SHA256
Deploy configuration
- Added tasks for publishing as container image. - Improvements for deployment: Db migrations on startup, reverse-proxy forward headers, and DataProtect management. - Added deploy example using docker-compose.
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# Somnia.GuestLog Deployment
|
||||
|
||||
## Deploy using docker-compose
|
||||
|
||||
Use [docker-compose file](docker-compose.yaml) as example. Configure required enviroment variables.
|
||||
|
||||
Notes:
|
||||
- By default, HTTP-only is deploy. Uncomment required sections to enable HTTPS (and mount required certs).
|
||||
- Reverse-proxies should work?
|
||||
|
||||
[To-Be-Improved]
|
||||
|
||||
## Manually update registry
|
||||
|
||||
Container images are built by CI/CD pipelines and uploaded to the registry (**not yet!**).
|
||||
|
||||
If required, a image can be manually built and uploaded to the registry (for testing or development purposes):
|
||||
```sh
|
||||
podman push [IMAGE_ID] [REGISTRY]/somnia/somnia-guestlog:[TAG]
|
||||
|
||||
# Example:
|
||||
podman push localhost/somnia-guestlog:latest gitea.uberelectronnetwork.cc/somnia/somnia-guestlog:devbuild
|
||||
```
|
||||
Reference in New Issue
Block a user