You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: