updated readme

main
alex 2023-11-05 19:49:15 +01:00
parent afd3bb8e8b
commit 475676aa83
2 changed files with 14 additions and 29 deletions

View File

@ -1,46 +1,38 @@
# Publishing new version
```
./delete-docker.sh
```
```
./build-docker.sh
```
```
./build-and-push.sh
./build-all-dockers.sh
```
# On the client side - fetch latest images
## remote-docker-compose.yml
Is the docker-compose.yml file that is used to deploy the application on a remote server.
Copy remote-docker-compose.yml as **docker-compose.yml** to the remote server.
Then run:
```
docker compose up
```
### Remove the old images
```
docker image rm dockreg.ex.umbach.dev/jnx-admin-dashboard-server dockreg.ex.umbach.dev/jnx-admin-dashboard-proxy dockreg.ex.umbach.dev/jnx-log-manager-server
```
### Pull the new images
```
docker compose up
docker image rm dockreg.ex.umbach.dev/jnx-admin-dashboard-server dockreg.ex.umbach.dev/jnx-admin-dashboard-proxy dockreg.ex.umbach.dev/jnx-log-manager-server jnx-robot-control-manager jnx-telegram-bot-manager
```
## Script used last time
delete.sh
```
docker compose down
docker image rm dockreg.ex.umbach.dev/jnx-admin-dashboard-server dockreg.ex.umbach.dev/jnx-admin-dashboard-proxy dockreg.ex.umbach.dev/jnx-log-manager-server
docker volume rm tet2_admin_dashboard_server_data tet2_log_manager_data
docker image rm dockreg.ex.umbach.dev/jnx-admin-dashboard-server dockreg.ex.umbach.dev/jnx-admin-dashboard-proxy dockreg.ex.umbach.dev/jnx-log-manager-server jnx-robot-control-manager jnx-telegram-bot-manager
docker volume rm <volumes>
```
build.sh
```
./build-all-dockers.sh
```
```
docker compose up

View File

@ -1,7 +0,0 @@
#docker compose down
# rm images
docker image rm jnx-admin-dashboard-server dockreg.ex.umbach.dev/jnx-admin-dashboard-server jnx-admin-dashboard-proxy dockreg.ex.umbach.dev/jnx-admin-dashboard-proxy
#docker volume rm admin-dashboard_server_data
#docker volume rm admin-dashboard_server_data