docs: Update release notes

ref: #371 closes #363
This commit is contained in:
2024-10-31 15:50:57 +09:30
parent ea8a054005
commit 9f826d7142
3 changed files with 19 additions and 1 deletions

View File

@ -1,3 +1,19 @@
# Version 1.3.0
!!! danger "Security"
As is currently the recommended method of deployment, the Centurion Container must be deployed behind a reverse proxy the conducts the SSL termination.
This release updates the docker container to be a production setup for deployment of Centurion. Prior to this version Centurion ERP was using a development setup for the webserver.
- Docker now uses SupervisorD for container
- Gunicorn WSGI setup for Centurion with NginX as the webserver.
- Container now has a health check.
- To setup container as "Worker", set `IS_WORKER='True'` environmental variable within container. _**Note:** You can still use command `celery -A app worker -l INFO`, although **not** recommended as the container health check will not be functioning_
# Version 1.0.0
Initial Release of Centurion ERP.

View File

@ -147,7 +147,7 @@ RUN pip --disable-pip-version-check list --outdated --format=json | \
WORKDIR /app
# In future, adjust port to 80 as nginX is now used (Will be breaking change)
EXPOSE 8000
VOLUME [ "/data", "/etc/itsm" ]

View File

@ -8,6 +8,8 @@ about: https://gitlab.com/nofusscomputing/infrastructure/configuration-managemen
Centurion ERP is a simple application to deploy with the only additional requirements being that you have already deployed a database server and a RabbitMQ server. Centurion ERP is container based and is deployable via Docker or upon Kubernetes. Our images are available on [Docker Hub](https://hub.docker.com/r/nofusscomputing/centurion-erp).
Deployment of Centurion ERP is recommended to be behind a reverse proxy. This is required as the method used to setup the containers does not include any SSL setup. Due to this the reverse proxy will be required to conduct the SSL termination.
!!! note "TL;DR"
`docker pull nofusscomputing/centurion-erp:latest`.