Hrmm due to filling up my database allocation I have had to increase my Masto

[bloor@bloor.tw]

@dtl I'd probably put it on a a separate "hosting block" tbh.

[dtl@8bitorbust.info]

@bloor I could probably magic up a VLAN, but I don't know if that's enough.

[ben@bluetoot.hardill.me.uk]

@bloor @eigen does that also include the cached media?

[bloor@bloor.tw]

@ben @eigen media is separate unfortunately

[ben@mastodon.bentasker.co.uk]

@bloor @dtl

FWIW, I quite happily run it at home on a NUC.

Although I've got gigabit internet, it turns out it'd probably have been fine on ADSL too

I have moved media to object storage though, which helps a lot

[bloor@bloor.tw]

@ben @dtl I have a NUC-like machine (N100 type thing) which I was running HA on before I moved. I guess I could run a separate VM on there for hosting a Masto instance.

[wishy@tooter.wishy.co.uk]

@bloor @ben @dtl masto doesn't need a huge amount of power. My instance has been hanging off one of your lines for a good few years now.

The protocol is pretty tolerant to a bit of downtime now and then

[bloor@bloor.tw]

@wishy @ben @dtl my main mental obstacle is the “getting it working” and then the “keeping it working”

[ben@mastodon.bentasker.co.uk]

@bloor @wishy @dtl Admittedly I run it in docker so don't have to worry about deps, But I've found it far lower maintenance than I was expecting.

The getting it going bit was a bit more effort though

[bloor@bloor.tw]

@ben @wishy @dtl see .. I have never used docker and have no idea how to use it or even really what it’s for…

[wishy@tooter.wishy.co.uk]

@bloor @ben @dtl you'd need to learn about 5 commands to manage the service through docker. It's been remarkably pain free tbh

[neil@mastodon.neilzone.co.uk]

@bloor @ben @wishy @dtl

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.

[steve@mastodon.nexusuk.org]

@bloor @ben @wishy @dtl I believe Docker is for a similar purpose to AutoTools. I.e. to make simple stuff go wrong in complex un-debuggable ways.

[neil@mastodon.neilzone.co.uk]

@bloor @ben @wishy @dtl

I am more than happy to go through it with you remotely at some point, should you wish!

[ben@mastodon.bentasker.co.uk]

@bloor @wishy @dtl

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

[bloor@bloor.tw]

@neil @ben @wishy @dtl thank you, I may very well take you up on that, I think I need to try and get my “basic requirements” in order first though, perhaps a machine or a virtual machine, nice and clean and ready

[bloor@bloor.tw]

@ben @wishy @dtl why not just use a VM?

[neil@mastodon.neilzone.co.uk]

@bloor @ben @wishy @dtl

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.

[ben@mastodon.bentasker.co.uk]

@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.

[wishy@tooter.wishy.co.uk]

@steve @bloor @ben @dtl in the case of masto, I would say the ruby setup is a bit of a pain. Docker just gives you a pre built image which largely just works