Enhancements to render the base image more suitable for production environments
- Dominant language
- Shell
- Stars
- 35
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The current Docker Compose environment serves well for both a _simple setup_ and a more _development specific_ purpose. However it lacks certain configurations and optimisations needed for a proper **production-grade deployment**.
We need to introduce changes and configurations to our Docker Compose environment to align it with production standards. This includes optimising resource allocation, securing sensitive information, ensuring high availability if possible, and incorporating best practices for monitoring and logging.
Here is the list of things to think about
1. Use a non-root user to install all software where root is **not** a requirement for installation
2. Should we have separate ckan users for installation _vs_ running the processes?
3. What about using a non-root user for volume mounts
4. Can we somehow simplify by combining both the non-dev and dev configurations so only one command is needed ie: `docker compose build | up`
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.