Page MenuHomePhabricator

Investigate: Ensure there's a production-ready init process
Closed, DuplicatePublic8 Estimated Story Points

Description

afaik security-api has only been built for development environments. Its init.sh script kicks off nodemon, which should only ever be used in development. Please investigate if another init script is needed or what needs to be done to still start up server.js without nodemon. If your investigation turns up additional information about what needs to be done to make the application production start-upable, please also document that (eg. I believe someone mentioned to me once that the docker-compose.yml was also only for development purposes. If so, where does configuration need to live?).

Event Timeline

Niharika set the point value for this task to 8.Dec 20 2022, 5:21 PM
Niharika subscribed.

Linked service request: T325147: New Service Request 'iPoid'

For production, I believe we want npm run start, which invokes service-runner.

For production, I believe we want npm run start, which invokes service-runner.

I'm not sure what the best practice is for services using GitLab CI (cc @Jelto) but I believe we'd want to add an entrypoint: entry (docs) and specify that the entrypoint for the production image is npm run start instead of the default init.sh file.