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

Determine how the pre-release deployment steps and methods #49

Open
jhujasonw opened this issue Mar 19, 2020 · 1 comment
Open

Determine how the pre-release deployment steps and methods #49

jhujasonw opened this issue Mar 19, 2020 · 1 comment
Assignees

Comments

@jhujasonw
Copy link

Need to figure out the best way to deploy the pre-release (and subsequently the production) site from an OPS perspective. This may inform some decisions that the developers make in their implementation strategy.

@jhujasonw jhujasonw self-assigned this Mar 19, 2020
@jhujasonw
Copy link
Author

My initial thoughts on this are:

  • there are 3 containers needed to run the site:
    -- Tomcat (the war resides here)
    -- Mysql (the database is here)
    -- nginx (this is the SSL reverse proxy)

If these three can be configured into docker images ready for production, the ops deployment does not need the 'lutece-init' container. This is the most cloud-friendly way of doing this. I see a few possible issues:

  • Passing in db information to tomcat could get a little hairy, but I think that may be able to be done via env vars.
  • the database is going to need to have non-ephemeral storage linked into the container. Some amount of db init may still be required.
  • passing in the host information for each container to talk to each other may be tricky. Need to look into the best way to make this happen.

These are points to discuss or ponder as we consider the best way to deploy. Further discussion is likely needed and things may need to change one way or another.

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

1 participant