Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Portainer #40

Open
samihenrique opened this issue Oct 14, 2019 · 4 comments
Open

Implement Portainer #40

samihenrique opened this issue Oct 14, 2019 · 4 comments

Comments

@samihenrique
Copy link

No description provided.

@beeblebrox3
Copy link
Member

I don't think the framework should be responsible for this.

@samihenrique
Copy link
Author

I see attiv being used most by small and medium, and maybe they don't have a good management of applications and servers, the idea of putting the portainer would be to empower the developer, and ensure greater visibility of what is happening underneath of the cloths in the docker.

@beeblebrox3
Copy link
Member

I understand, but why this has to be part of the framework? If one build five apps with the framework, each one needs to have it's own portainer? Or the developer needs to know how to handle this? how to approach this on docs?
I think it will only complicate things. Maybe we can add a section about it on docs, but just that.

@taciomedeiros
Copy link
Member

I agree with @beeblebrox3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants