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

setup development and production environement #3

Open
lesly-houndole opened this issue Nov 8, 2017 · 1 comment
Open

setup development and production environement #3

lesly-houndole opened this issue Nov 8, 2017 · 1 comment
Assignees

Comments

@lesly-houndole
Copy link
Contributor

lesly-houndole commented Nov 8, 2017

Today, the development and production environments are the same hence it's not possible to guaranty that the code is correct at an instant T. I remind you that the production server must contain essentially what has been validated by the quality service of Hotmaps. We recently had the case of Thierry (quality department) who had validated that the calculations were good in production and a week later, it was no longer, this is not viable, we must control our development and apply rigorously the GIT guidelines define in the project. In a development process, there must be at least two environments, development and production, for more security, there should also be a staging environment.

@29axe
Copy link
Contributor

29axe commented Nov 9, 2017

As we discussed, I might add a dev container (in parallel of the toolbox-service) to isolate the development from the demo platform. Keep in mind that the advantage of using docker is that you can run the whole platform localy while developing.
So we will duplicate all the services/modules accordingly, except the database that won't see any risky changes.

@29axe 29axe removed the bug label Nov 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants