shnizmuffin

This (along with basically all instances with communick news behind them) is a classic example of scaling up prematurely.

When this community is brimming with so much content that users start to “miss” posts about [thing x] because there are so many posts about [thing y], then you make offshoot communities, not before.

lol yeah, that’ll do it.

Using the template syntax you can start by copy/pasting the site to be migrated, and then inject sections that render using markdown syntax.

What templating languages do you know already, and are you running 11ty v3? There are some gotchas around images because (I think) the eleventy-image plugin is enabled by default.

I’ve found success running with .webc which is effectively HTML until you need it to be more.

Shout out to my fellow “None Backup Strategies” chaos goblins.

Repokémon is an amazing name.

Direct link to the PDF.

Donphan is legit, too.

This person couldn’t be bothered to search “Phanpy Mastodon” to learn more, literally everything is non-trivial to them. They probably have to remember to breathe.

Let me Google that for you.

Amazon SES is dirt cheap, billed per-send, you just need to bring the Everything Else with something like Mailcoach or Sendy.

Use containers. Start with one device. Check your utilization after you’re sure you’ve hit min and max for each of your services, then figure out if your single device can handle all your services gunning at once. If not, take your biggest service and migrate it to its own device.

Eventually, you might find yourself googling “Kubernetes vs Docker Swarm.” When you do that, take a deep breath and decide if upgrading one device is easier than trying to horizontally scale many.

Edit: Words bad. Verbs hard.

There are tons.