ocelot-Social-Community/Ocelot-Social
1
0
Fork 0
mirror of https://github.com/Ocelot-Social-Community/Ocelot-Social.git synced 2025-12-13 07:46:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fine tuning documentation

Browse Source
This commit is contained in:
Robert Schäfer 2019-04-24 23:55:49 +02:00
parent 86c0307ddb
commit c350fb37a9
2 changed files with 17 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
deployment/human-connection/README.md
View File

@ -18,7 +18,7 @@ environment variables in your deployed kubernetes pods.
If you want to edit secrets, you have to `base64` encode them. See [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-manually). If you want to edit secrets, you have to `base64` encode them. See [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-manually).
```text ```bash
# example how to base64 a string: # example how to base64 a string:
$ echo -n 'admin' | base64 --wrap 0 $ echo -n 'admin' | base64 --wrap 0
YWRtaW4= YWRtaW4=
@ -29,7 +29,7 @@ your deployed kubernetes pods.
## Create a namespace ## Create a namespace
```text ```bash
$ kubectl apply -f namespace-human-connection.yaml $ kubectl apply -f namespace-human-connection.yaml
``` ```
@ -47,7 +47,7 @@ persistent volumes once before you apply the configuration.
## Apply the configuration ## Apply the configuration
```text ```bash
# in folder deployment/ # in folder deployment/
$ kubectl apply -f human-connection/ $ kubectl apply -f human-connection/
``` ```

17
deployment/legacy-migration/README.md
View File

@ -39,6 +39,7 @@ Bring the application into maintenance mode.
Then temporarily delete backend and database deployments Then temporarily delete backend and database deployments
```bash ```bash
$ kubectl --namespace=human-connection get deployments $ kubectl --namespace=human-connection get deployments
NAME READY UP-TO-DATE AVAILABLE AGE NAME READY UP-TO-DATE AVAILABLE AGE
@ -52,7 +53,8 @@ deployment.extensions "nitro-backend" deleted
``` ```
Deploy one-time maintenance-worker pod: Deploy one-time maintenance-worker pod:
```
```bash
# in deployment/legacy-migration/ # in deployment/legacy-migration/
$ kubectl apply -f db-migration-worker.yaml $ kubectl apply -f db-migration-worker.yaml
pod/nitro-maintenance-worker created pod/nitro-maintenance-worker created
@ -60,7 +62,7 @@ pod/nitro-maintenance-worker created
Import legacy database and uploads: Import legacy database and uploads:
```text ```bash
$ kubectl --namespace=human-connection exec -it nitro-maintenance-worker bash $ kubectl --namespace=human-connection exec -it nitro-maintenance-worker bash
$ import_legacy_db $ import_legacy_db
$ import_uploads $ import_uploads
@ -68,7 +70,16 @@ $ exit
``` ```
Delete the pod when you're done: Delete the pod when you're done:
```
```bash
$ kubectl --namespace=human-connection delete pod nitro-maintenance-worker $ kubectl --namespace=human-connection delete pod nitro-maintenance-worker
``` ```
Oh, and of course you have to get those deleted deployments back. One way of
doing it would be:
```bash
# in folder deployment/
$ kubectl apply -f human-connection/deployment-backend.yaml -f human-connection/deployment-neo4j.yaml
```