If you want to switch to the develop channel, you simply stop and delete the mastercontainer and create a new one with a changed tag to develop:
sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8080:8080 \
--publish 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:develop
And you are done :) It will now also select the developer channel for all other containers automatically.
Simply use #180 as template.
Simply use #6198 as template.
Go to https://github.com/nextcloud-releases/all-in-one/actions/workflows/repo-sync.yml and run the workflow that will first sync the repo and then build new container that automatically get published to develop
and develop-arm64
.
Before testing, make sure that at least the amd64 containers are built successfully by checking the last workflow here: https://github.com/nextcloud-releases/all-in-one/actions/workflows/build_images.yml.
There is a testing-VM available for the maintainer of AIO that allows for some final testing before releasing new version. See this for details.
Additionally, there are now E2E tests available that can be run via https://github.com/nextcloud/all-in-one/actions/workflows/playwright.yml
- Verify that no job is running here: https://github.com/nextcloud-releases/all-in-one/actions/workflows/build_images.yml
- Go to https://github.com/nextcloud-releases/all-in-one/actions/workflows/promote-to-beta.yml, click on
Run workflow
.
This is documented here: https://github.com/nextcloud-releases/all-in-one/tree/main/.build
- Verify that no job is running here: https://github.com/nextcloud-releases/all-in-one/actions/workflows/promote-to-beta.yml
- Go to https://github.com/nextcloud-releases/all-in-one/actions/workflows/promote-to-latest.yml, click on
Run workflow
.
Simply run sudo docker exec -it nextcloud-aio-database psql -U oc_nextcloud nextcloud_database
and you should be in.