Cloudron Forum

@LoudLemur about the broken link I have fixed it in the sample file, and you can fix in <1. minute in your deployed application, if it's still running. go to File Manager open content folder open index.gmi scroll down to the links section remove the "$0" after the '.gmi' on the last 2 links No idea how they got there, copy paste error by me probably. Just to get you up and running with testing

Ok the docker issue is on their end. I'll wait until tomorrow to clean all the images on my repo up. I've posted about this app on the Wishlist section to see if there is any interest in putting in on the App Store.

Thanks! I'm going to play around by modifying an existing app and see how far I get.

I think I may have found the solution. I can drop everything in the old database by logging in to the psql database and doing: DROP OWNED BY userXXXXXX CASCADE; (obviously replacing the XXXX by the random number generated for the peertube app) and then recreating an empty schema ready form import: CREATE SCHEMA public; CREATE EXTENSION unaccent; CREATE EXTENSION pg_trgm; (unaccent and pg_trgm are needed for restoring the peer tube db dump). Then the restore works without error or warnings: PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} pg_restore -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} --format=custom --schema=public --no-owner --role=${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} peertube_prod-dump.db and my app seems to come back up correctly as my old peertube server. I'll keep an eye on it in the next couple of days to see if I notice anything odd.

It looks like the migration went smoothly. I'll put together a blog post to details the steps I took. Thank you again for all the help!