Sebastian Fisahn
94f9b8969d
repo setup
|
1 anno fa | |
|---|---|---|
| .. | ||
| README.md | 1 anno fa | |
| docker-compose.yml | 1 anno fa | |
| nextcloud-claim0-persistentvolumeclaim.yaml | 1 anno fa | |
| nextcloud-claim1-persistentvolumeclaim.yaml | 1 anno fa | |
| nextcloud-claim2-persistentvolumeclaim.yaml | 1 anno fa | |
| nextcloud-claim3-persistentvolumeclaim.yaml | 1 anno fa | |
| nextcloud-claim4-persistentvolumeclaim.yaml | 1 anno fa | |
| nextcloud-db-claim0-persistentvolumeclaim.yaml | 1 anno fa | |
| nextcloud-db-deployment.yaml | 1 anno fa | |
| nextcloud-deployment.yaml | 1 anno fa | |
| nextcloud-service.yaml | 1 anno fa | |
| output.txt | 1 anno fa | |
| rancher-compose.yml | 1 anno fa | |
| redis-claim0-persistentvolumeclaim.yaml | 1 anno fa | |
| redis-deployment.yaml | 1 anno fa | |
README.md
Some Rancher v1.x organizational concepts have changed in racher v2.x:
- environments -> projects
- stacks -> namespaces
- services -> workloads
To maintain same organization boundaries on rancher v2.x, is recommended to:
- create a separated project for every rancher v1.x environment.
- create a separated namespace for every rancher v1.x stack.
Project: Sebastians Namespace: nextcloud