@scully @sophia @ramsey
So, the best option is to start a new server and migrate all accounts on the old server, read here the instructions on how to migrate your account: docs.joinmastodon.org/user/mov and once that is done you can stop the old server. Notice that has it says on that page content is not migrated, just followers, following and settings.

@scully @sophia @ramsey Mastodon doesn't support domain name changes as it depends on the domain name to make federation work. I can do it on my end but this will partially break the remote federation/communication between Mastodon servers.

@ton Yes, like it says on the post "want Masto.host to continue to be what, hopefully, is a positive force helping the community thrive" and as the network grows it should be less and less decentralised. Let's hope that happens.
Thank you so much for your continued support and for sharing your thoughts. Really appreciate it :)

@arjen Well, I don't think there is a right way. One could do it per user, or per active user or per volume of traffic like you suggested but in the end the number of instances works for my goal that is to just have enough return that is viable for me to continue to invest the time I currently do on the service, plus introducing some improvements that I have in mind for the future.

All of the ways to count have their issues, see an example here: mastodon.social/web/@mastohost

@raphael Sure, no problem. Anything else you need feel free to reach out.

@raphael extremely rare on my end but I have a somewhat strict TOS: masto.host/tos/

Happened half a doze on time in five years. A couple of cases the admin was easy to deal with and took down the content/blocked any trouble account. On the others, I cancelled the subscription, refunded the payment, suspended the instance and sent them the backup so they could host elsewhere.

@raphael IMO no point in building something large when you don't have the need.

But the infrastructure is not the hard part. Like, I just said here mastodon.social/@mastohost/108 the people can give you much more work than the machines :)

@raphael Yep, I also never liked the idea of one VM per instance. Also, harder to maintain in my opinion.

Well, I started with a single VPS. Initially without Docker but separating user per linux user account and it worked fine. As I didn't/don't provide SSH access, that worked fine.

If you can get a couple of instances working instances running on the same VPS then you have all the basics you need and then you see what your needs are in terms of scaling.

@maolfunction Thank you so much. Hopefully that will happen :) appreciate it.

@raphael For monitoring and alerting I use nixstats.com/

Not sure what you mean by "receive abuse notices".

@raphael About backups, is just a cron that runs daily and does pg_dump and another that moves them to an external object storage. Plus, I have another cron 24/7 doing a sync of media files to the same external object storage but keeping media deletes per day. Finally another cron that deletes old database backups and old media deletes.

Like I said, a bunch of crons :)

@raphael I don't use VMs, I use Docker for the actual Mastodon code that communicates with the other 2 layers.

If I need more resources I add more servers to each of the layers. I can move instances in the app servers between servers as needed and database and web servers are usually pretty predictable and stable in terms of resource needs. No big deal there.

@raphael Here you have the infrastructure: masto.host/infrastructure/

I have 3 layers, the web servers (NGINX), the app servers (Docker) and the database servers (PostgreSQL and Redis). Each layer is independent and can only communicate with the next one, meaning if someone could get access to the web servers they would have a harder time reaching the actual data (databases) that way.

@josias Sure, just email me any specific questions you have.

But if you have tested fully install 2 Mastodon instances on the same server/VPS and you got that running, then you have the basics of what is needed.

Also, maintaining servers is pretty simple if you don't overscale/abuse resources and have the right setup+monitoring. I can be weeks without touching a server but I can't go out for dinner for a couple of hours without receiving an email with a support request :)

@koyuchan Yep the vast majority of my installations are of instances with a small number of users. All I want is to reach a place where I can pay for my time and offer a service with the price/quality that I would like someone else to provide for me. If I get there, then I don't mind to keep running Masto.host for 5 more years :)

Thanks for the support, for all you have done on Mastodon and always being so great to work with.

Show older

The original server operated by the Mastodon gGmbH non-profit