Note these are not any official notes - just random scribbles
Running bootstrap wont give you the latest dev versions, only whats been released on the bootstrap server by the ynput team.
Updating it from time to time is a good way to see what progress has been made in terms of addons etc. It shouldnt remove old addon version, only add the new ones. That way you can still use older addons should you need. You would need to create a new bundle to accommodate that.
If you want to run the latest addons, you would need to grab that from the openpype github repository (as that is the current location of the ayon addons) then manually build those (instructions should be on the repository in the Server Addon README) then manually upload those newer addons to the ayon server. You can do this via the ayon web interface or command line should you need.
Set e.g. this in the server section of docker-compose.yml
:
environment:
- "AYON_SESSION_TTL=604800"
Update ayon-docker
, also see AYON Docs: Server Deployment - updates and comment: AYON Updating docker + picking the right tag
Latest:
docker pull ynput/ayon:latest
docker compose up -d --build
Dev:
docker pull ynput/ayon:dev
docker compose up -d --build
Before someone helps to debug, it would be good to make sure you are on the latest build. Run make update
./.poetry/bin/poetry run python ./server_addon/create_ayon_addons.py
Generally its along the lines of docker buildx prune
. Where buildx
is the container, image, etc.
Just be sure not to blow your volumes away!
Run docker system prune -a
' on development machine as part of digital hygiene procedure.
It tells you what it is going to delete (unused things). Make sure to keep stuff you want to keep running.
docker compose exec postgres pg_dump -U ayon > backup.sql
Source: https://discord.com/channels/517362899170230292/611571347058982927/1187432211067183174
- run
docker compose exec postgres pg_dump -U ayon > backup.sql
to create database dump - copy
storage/
docker-compose.yml
andbackup.sql
to the new machine - run
docker compose up postgres
on the new machine to start only the database (if you run the entire stack, it will be populated with defaults, we want to keep it empty for now) - run
docker compose exec -T postgres psql -U ayon ayon < backup.sql
to restore the backup - start everything using
docker compose up
By the way, this method also allows upgrading the database server. If you dump the db
storage and restore it on the target machine, you need to use the same postgres version, while using pg_dump
converts everything in the database to a huge list of sql queries, which you can run on a newer postgres database.
Note: The exact commands may differ on Windows see here for a Powershell example:
If you are struggling with redirections like
docker compose exec postgres pg_dump -U ayon > backup.sql
.In Powershell on windows it is
docker compose exec postgres pg_dump -U ayon | Out-File backup.sql
.And the other way around like
docker compose exec -T postgres psql -U ayon ayon < backup.sql
.In Powershell on windows is
powershell cat backup.sql | docker compose exec -T postgres psql -U ayon ayon
.
And bonus points - you may want to use best practice naming conventions for your backup files
AYON getting started / onboarding discussions: