Hrmm due to filling up my database allocation I have had to increase my Masto
-
-
-
I am self-hosted, on an N100 Intel NUC.
I am not using docker.
I do not do anything fancy to keep it going (and it gets a fair workout :)).
It is not the most trivial installation, but not is it too bad.
-
-
I am more than happy to go through it with you remotely at some point, should you wish!
-
fair. Easiest way to think of it is a small prebuilt vm image but without a kernel and (usually) designed to run a single app.
Running a docker container is generally easy, but troubleshooting docker issues can be a pain (though rarely needed IME), so I guess a native install might end up being less burden if you're not already doing that anyway
-
-
fair. Easiest way to think of it is a small prebuilt vm image but without a kernel and (usually) designed to run a single app.
Running a docker container is generally easy, but troubleshooting docker issues can be a pain (though rarely needed IME), so I guess a native install might end up being less burden if you're not already doing that anyway
-
Sure!
Personally, I am not using a VM, although there may be some value to that. I dedicated the whole machine to Mastodon, but then I, erm, use it rather a lot!
So just a normal Debian installation for me.
-
@bloor @wishy @dtl The answer to that depends a bit on exact needs, but
Scalability - I can run far more containers than I can VMs because containers don't usually bring userspace and kernel overhead
Ease of deployment: containers ship with all their deps in there, so there's no screwing about with dep hell (or incompatible deps being required by different apps). That also makes support easier if you're shipping
upgrades are also much easier - you just change the tag and pull the new image.
-
-
-
-
-
@neil @dtl @bloor @wishy Similar here, it's in its own segment - my firewall has multiple NICs so hangs off one of those.
I gave that segment its own IPv6 subnet, so if there ever was an issue, I'll be able to see at a glance whether it was our LAN or the masto box (less so for ipv4 though because NAT)
-
-
@steve @wishy @bloor @dtl Yeah that's fair
I remember nearly going to war with engineering because they wanted to start shipping software to us (ops) as docker images solely because it made deployment easier for them.
I get on very well with containers nowadays (didnt have much choice when I started owning a SaaS product running on k8s), but (if I was still there) I think I'd still make the same arguments against them driving the CDN
-
@bloor @ben @wishy @dtl sadly docker is probably the worst implementation of the container concept, but it useful in the modern world, even if it shouldn't be. podman is saner in many respects. It's also worth playing with "full system" containers via e.g. systemd-nspawn - they might make more sense if you're used to VMs, and it uses the same kernel features as application containers, so it's a good way of getting experience with those.
-
@bloor@bloor.tw
Have you looked at snac2? https://codeberg.org/grunfink/snac2
In C, no dependencies, uses small files instead of a DB. make; make install works for everything I need from a single user instance.
The old UNIX spirit is still alive there
-
@bloor@bloor.tw
Have you looked at snac2? https://codeberg.org/grunfink/snac2
In C, no dependencies, uses small files instead of a DB. make; make install works for everything I need from a single user instance.
The old UNIX spirit is still alive there@david Ignorant question: is activtypub another word for mastodon? If not, I'm not sure what this is!
