@james said in Mastodon migration: Or did I understood your question wrong? No that was part of my question. Thank you! The other part is, the masto.host backup has a folder structure with things like media/accounts/avatars or media/custom_emojis and I want to make sure that those things are in a similar location on the Cloudron install so I know where to copy everything over. I'm going to do a trial run on a test Cloudron app anyway before I attempt to do it for real.

Hello @aksaks From the documentation: Apps are run with an AppArmor profile that disables many system calls and restricts access to proc and sys filesystems. Apps run with a read-only rootfs preventing attacks where the application code can be tampered with. @aksaks said in How to modify mastodon files: if we can't modify files then how else we are going to work with read only apps? The core application is read-only. Everything that is needed to be read-write e.g. files in Nextcloud, pictures in Mastodon, everything that is user-data is read-write. This also greatly reduced the backup footprint, backup times and restore times. Also, a tamper protection. As an example, most WordPress instances get hijacked at some point and then the WordPress core PHP files are edited to insert malware or worse. The application-core read-only approach protects from that.

Hello @sponch There are currently no plans to include this in the Cloudron Package for Mastodon.

If you continue to read the aws-cli docs, you can specify where to install them, ie /app/data It's alsways useful to set the HOME dir variable whenever working with the CLI with export HOME=/app/data

@robi Good idea, thanks. Continuing in https://forum.cloudron.io/post/105874

@scooke @jdaviescoates Ok, I will look into the storage factor before I applied any fakerelay. Thank for the advice.

@joseph Thank you for your feedback. So far, my setup has been working well for a month. But I will follow your advice and use the hosts file to avoid updates breaking my setup.

But it will force me to maintain the old instance. OK. Thank you for your help

Hey all, thanks for recent notes. Still a good idea, probably need to find a developer who can do the packaging first.

I seem to recall that there may be tools out there to help this, but your googling will turn up whatever that was just as quick as mine. I would say that I tried doing this myself, twice, and by the second time I decided to handle it manually. That is, I downloaded and saved (I know, I should have done better saving the originals) the various graphics my site used, as well as my list of contacts, etc., and then re-uploaded them to the new location, then relinked them from within Mastodon. The first time the migration didn't work, there was no one who could help, and it was just quicker to do it manually. All the graphics connected to other users were eventually repopulated anyway, and anything I had wanted previously I had downloaded and saved. So, in a way, there wasn't a need to migrate anything. Good luck.

@jayonrails the avatar link is set in the OIDC responses. that's the only situation where cloudron's profile pics are used in apps.

the second link (everything on the second link)

right I meant more like the app was maybe installed from a package, where the OTP_SECRET was not yet set properly. This was then a packaging bug not a user error.

Thank you for the explanation, I didn't know that.

@johannesjom me too

here we go Using a private bucket on Hetzner. S3_ENABLED=true S3_BUCKET=NameOfYourBucket AWS_ACCESS_KEY_ID=xxxxxxxx AWS_SECRET_ACCESS_KEY=xxxxxxxxxxxxxxxx S3_REGION=eu-central-1 S3_PROTOCOL=https S3_HOSTNAME=NameOfYourBucket.fsn1.your-objectstorage.com S3_ENDPOINT=https://NameOfYourBucket.fsn1.your-objectstorage.com

While typing this here, I had the idea to check the create command for a flag and indeed there is --approve: /app/code/bin/tootctl accounts modify testusername --approve

@archos Thank you. That command helped. Now I have some broken images next to some profile pictures like using verified status pic (or something). I think, I check that next. But this was a huge help!

Package update is out.