You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, we've tried to update to version 1.17, but the docker-compose file has changed a lot since then. More specifically, we've seen that the penpot_asset volume was renamed in the newer version of the file, and are a bit worried that this could cause the loss of our assets if we just C/P the newest file. Is there a safe way for us to do the upgrade without loosing any data ? Or is a c/p of the newest version of the docker-compose file enough ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello !
Last november, a friend of mine deployed on a shared server version 1.16 of penpot, based on the october 2022 docker-compose file (https://github.com/penpot/penpot/blob/c534a40923dd9396153b2a23f5493c9873f82706/docker/images/docker-compose.yaml).
Recently, we've tried to update to version 1.17, but the docker-compose file has changed a lot since then. More specifically, we've seen that the penpot_asset volume was renamed in the newer version of the file, and are a bit worried that this could cause the loss of our assets if we just C/P the newest file. Is there a safe way for us to do the upgrade without loosing any data ? Or is a c/p of the newest version of the docker-compose file enough ?
Thank you in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions