mirror of
https://github.com/Ocelot-Social-Community/Ocelot-Social.git
synced 2025-12-12 23:35:58 +00:00
Change docker repository to develop-maintenance
- maintenance —> develop-maintenance
This commit is contained in:
parent
558ef75471
commit
da91be2136
@ -9,7 +9,7 @@ dbMigrations: "yarn prod:migrate up"
|
||||
# bakendImage is the docker image for the backend deployment
|
||||
backendImage: ocelotsocialnetwork/develop-backend
|
||||
# maintenanceImage is the docker image for the maintenance deployment
|
||||
maintenanceImage: ocelotsocialnetwork/maintenance
|
||||
maintenanceImage: ocelotsocialnetwork/develop-maintenance
|
||||
# neo4jImage is the docker image for the neo4j deployment
|
||||
neo4jImage: ocelotsocialnetwork/develop-neo4j
|
||||
# webappImage is the docker image for the webapp deployment
|
||||
|
||||
@ -10,9 +10,10 @@ bring the database into maintenance mode for manual database migrations.
|
||||
## Deploy the service
|
||||
|
||||
We prepared sample configuration, so you can simply run:
|
||||
|
||||
```sh
|
||||
# in folder deployment/
|
||||
kubectl apply -f human-connection/maintenance
|
||||
$ kubectl apply -f human-connection/maintenance
|
||||
```
|
||||
|
||||
This will fire up a maintenance service.
|
||||
@ -23,6 +24,7 @@ Now if you want to have a controlled downtime and you want to bring your
|
||||
application into maintenance mode, you can edit your global ingress server.
|
||||
|
||||
E.g. in file `deployment/digital-ocean/https/ingress.yaml` change the following:
|
||||
|
||||
```yaml
|
||||
...
|
||||
|
||||
@ -32,12 +34,12 @@ E.g. in file `deployment/digital-ocean/https/ingress.yaml` change the following:
|
||||
- path: /
|
||||
backend:
|
||||
# serviceName: develop-webapp
|
||||
serviceName: maintenance
|
||||
serviceName: develop-maintenance
|
||||
# servicePort: 3000
|
||||
servicePort: 80
|
||||
```
|
||||
|
||||
Then run ` kubectl apply -f deployment/digital-ocean/https/ingress.yaml`. If you
|
||||
Then run `$ kubectl apply -f deployment/digital-ocean/https/ingress.yaml`. If you
|
||||
want to deactivate the maintenance server, just undo the edit and apply the
|
||||
configuration again.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ spec:
|
||||
env:
|
||||
- name: HOST
|
||||
value: 0.0.0.0
|
||||
image: ocelotsocialnetwork/maintenance:latest
|
||||
image: ocelotsocialnetwork/develop-maintenance:latest
|
||||
ports:
|
||||
- containerPort: 80
|
||||
imagePullPolicy: Always
|
||||
|
||||
@ -31,7 +31,7 @@ services:
|
||||
- "DEBUG=${DEBUG}"
|
||||
- PUBLIC_REGISTRATION=false
|
||||
maintenance:
|
||||
image: ocelotsocialnetwork/maintenance:latest
|
||||
image: ocelotsocialnetwork/develop-maintenance:latest
|
||||
build:
|
||||
context: webapp
|
||||
dockerfile: Dockerfile.maintenance
|
||||
|
||||
@ -11,7 +11,7 @@ tags=($major $major.$minor $major.$minor.$patch)
|
||||
# docker build --build-arg BUILD_COMMIT=$BUILD_COMMIT --target production -t ocelotsocialnetwork/develop-backend:latest $ROOT_DIR/backend
|
||||
# docker build --build-arg BUILD_COMMIT=$BUILD_COMMIT --target production -t ocelotsocialnetwork/develop-webapp:latest $ROOT_DIR/webapp
|
||||
# docker build --build-arg BUILD_COMMIT=$BUILD_COMMIT -t ocelotsocialnetwork/develop-neo4j:latest $ROOT_DIR/neo4j
|
||||
docker build -t ocelotsocialnetwork/maintenance:latest $ROOT_DIR/webapp/ -f $ROOT_DIR/webapp/Dockerfile.maintenance
|
||||
docker build -t ocelotsocialnetwork/develop-maintenance:latest $ROOT_DIR/webapp/ -f $ROOT_DIR/webapp/Dockerfile.maintenance
|
||||
|
||||
echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user