search

statusengine / interface

AngularJS based Web Interface for Statusengine
https://statusengine.org/ui/#overview
GNU General Public License v3.0
18 stars 7 forks source link

Use docker-compose #19

Closed mrala closed 5 years ago

mrala commented 6 years ago

Resolves #18

nook24 commented 6 years ago

Many thanks @mrala for your contribution. This gave us the opportunity to evaluate how well Statusengine and it's components will fit into a Docker environment.

Unfortunately we noticed, that not all components (especially the module which depends on legacy C code) will fit into Docker super well.

Maybe it is better for us, to use some configuration management like Ansible, to get the most flexibility (different databases, templates for config files, etc.) or a mixed method where Ansible and Docker are used to get the best out of both.

I will close the issue #18 for now, and keep your pull request for later references.

We are thankful that we could test Docker, and will do some further evaluations and tests. Happy Hacktoberfest!

mrala commented 6 years ago

Not a problem, @nook24! You may find it useful to use Docker for the interface-ui bit, even if the other components may not be a good fit for containerization.

Also, if you think it's worth pursuing, I wouldn't mind taking a look at how the other components could be containerized. As far as allowing for flexibility, I agree that Ansible would likely be a better fit. However, there are a few options to have flexibility using Docker: using environment variables in docker-compose, using multiple docker-compose files for different configurations, etc. I was working off the assumption that using MySQL and some of the other configuration options would be an simple choice for quick development debugging.

Thanks for taking a look!

mrala commented 5 years ago

Closing old PRs.