Sebastian.Fisahn 28cfa3323d Initial commit 2 lat temu
..
README.md 28cfa3323d Initial commit 2 lat temu
docker-compose.yml 28cfa3323d Initial commit 2 lat temu
gogs-claim0-persistentvolumeclaim.yaml 28cfa3323d Initial commit 2 lat temu
gogs-deployment.yaml 28cfa3323d Initial commit 2 lat temu
gogs-service.yaml 28cfa3323d Initial commit 2 lat temu
output.txt 28cfa3323d Initial commit 2 lat temu
postgres-claim0-persistentvolumeclaim.yaml 28cfa3323d Initial commit 2 lat temu
postgres-deployment.yaml 28cfa3323d Initial commit 2 lat temu
rancher-compose.yml 28cfa3323d Initial commit 2 lat temu

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: gogs