mastodon-documentation VS test_feedback

Visit your instance, make yourself an account, and set yourself as admin by running this function in the Cloudron > Mastodon Terminal: https://github.com/McKael/mastodon-documentation/blob/master/Running-Mastodon/Administration-guide.md

For those wondering about how to sign up to mastodon and what server to pick:

It's like picking an email server. They all have their differences, but generally they are interoperable. You can read users from anywhere, and follow from anywhere. Better yet, it's fairly easy to move your account from one server to another if you don't like it.

Your best bet is some of the bigger second-tier servers (ones that have thousands but not hundreds of thousands of users) because they aren't as heavily loaded.

https://github.com/McKael/mastodon-documentation/blob/master...

An internet search showed https://instances.social/ and https://github.com/McKael/mastodon-documentation/blob/master/Using-Mastodon/List-of-Mastodon-instances.md. There is no website that lists all of them. While this might feel a bit annoying, think about it this way: Imagine looking for a new email-service, there is not the one website that lists all of them. Same here. Since it’s a decentralized service, that’s just not possible.

Found some basic requirements in GitHub: https://github.com/McKael/mastodon-documentation/blob/master/Running-Mastodon/Resources-needed.md

you can find a break down of what cpu and ram needs are expected here, for this tutorial you will be running without docker.

But basically, docker-compose build will get you most of the way there. These instructions are old but mostly still relevant: https://github.com/McKael/mastodon-documentation/blob/master/Running-Mastodon/Docker-Guide.md

There is currently an incompatible ubuntu update, that may or may not be resolved by the time you do this, if you experience a warning about a failed grub installation tell it not to retry, and to continue without installing grub and the issue will not return in further updates. this is documented here, this issue is resolved by not skipping the step of running update & upgrade and handling the warning at the beginning of each deployment. it will break the install scripts in the tutorials if you do not update and upgrade first.