Toot

Written by Marc Trius on 2025-01-05 at 23:22

Hi so this is kind of an opinion question. I am setting up some apps on a VPS provider and trying to figure out what is the best way to architect it. My specialization is in dev not ops, so I'm stuck on how to set it up.

Here's my use case:

1. For now it'll be at least 3 #Ghost blogs, I might add other things later, like a Fedi instance or #forgejo, or maybe some other kinds of applications.

2. I am not expecting huge amounts of traffic, but it's good to know one's services are resilient. I think that there's a greater risk of becoming a target of ddos or some other attack from people who hate me, than very popular with readers and users...

3. I'm using a VPS host that charges by fine grained use of resources, so there is basically no cost per server, only the overhead that server generates from running the OS and so on. I've done this in shared hosting with https://nearlyfreespeech.net but https://slicie.com offers VPS. I'm on a 60-day trial so I get to see how that works out.

4. I want to build something resilient, learn cool and useful things, get into aelf-hosting, and mitigate my tendency to over-engineer things...

So, what should I do? I'd appreciate comments and explanations.

Please boost

[#]network #architecture

=> More informations about this toot | View the thread | More toots from alter_kaker@hachyderm.io

Mentions

Tags

=> View ghost tag | View forgejo tag | View network tag | View architecture tag