Is it fairly cheap to host your own personal, single-user Lemmy instance?
Is it fairly cheap to host your own personal, single-user Lemmy instance?
Let's say I decided that instead of blogging, I wanted to host my own Lemmy instance that contained a maximum of one (1) user– me, but allowing other users to subscribe.
To show what I'm talking about, look at how kaidomac uses Reddit as his own personal microblog, which people subscribe to.
What is the cheapest way to do this?
My mental model of Lemmy is that if I were to do this, the instance would still be caching information from other instances. This would– at least in my mine– add up in costs.
I'm a software engineer, so feel free to use technical jargon.
Selfhosting is basically free. You already have an unmetered Internet connection, and sourcing some hardware to run Lemmy would also be super easy.
The “problem” is that setting Lemmy up is quite annoying and complex and involves multiple docker containers and volumes and networks. There are various installation scripts but it is still a complete mess.
It would also result in a metric shit-ton of traffic and data storage.
I'm not sure how much you're willing to write off as "basically free", but electricity does add up for running your own server.
http://www.wolframalpha.com/input/?i=200w*1 year *%240.14%2FkWh
$245/year assuming constant 200W load which is pretty reasonable for a small web server.
The trick is to have the server do other things like print, Plex, Piwigo, Samba, Shinobi, Frigate, Matrix, etc
It depends on how powerful of a machine you need. My server only costs about $9.25/mo to run and it is way overpowered for the services I run on it.
The problem for me is I believe you need to open your network firewall for Lemmy and other federated services to work right?
Not really a fan of opening up more attack surface on my home network
The problem for me is I believe you need to open your network firewall for Lemmy and other federated services to work right?
Yes, of course. Or search for an external reverse proxy. Cloudflare offers something like this. (You set a Cloudflare server IP as target for your domain and then tell Cloudflare your IP and all traffic is routed over the Cloudflare ecosystem so your actual IP is not publicly used.)
I just opened port 443 and forwarded it to my Docker host and have NPM running there, handling all the forwarding to the individual containers, based on the request, but due to my day job I know what I’m doing :)
It would also result in a metric shit-ton of traffic and data storage.
Really depends how many instances they want to federate with. I run a single user instance for all of my personal Lemmy use. Looks like it is using 20Gb of bandwidth per week, and the VM it runs on only has 32Gb of storage (and it runs other services, too)
Lemmy is definitely the most pain in the ass service that I self host. Most annoyingly when something goes wrong I can't just go on Lemmy until I feel like fixing it.
It's very cheap. Hostinger's cheapest tier ($17/mo) can easily handle a single-user Lemmy instance. You'll have to once in a blue moon worry about the image storage growing without limit, but it's a solvable problem.
Thanks, that's pretty good. Would Lemmy work with the base-tier (512mb RAM $4 USD) droplet?
For that kind of money you get so much much more at a budget host like contabo.
I think you would need more RAM than that. Between Rust and Node, I probably wouldn't try to make do with less than 2 GB at a bare minimum, and 4 might be better.
I run mine on digital ocean and it's great. Mine is slightly more powerful, but you can always start small and upgrade. It's much harder to downgrade
I already had a server running docker, so throwing a few more containers in was trivial. There's a docker-compose.yml published in the lemmy repo.
Since my server was already running and had free space, it was literally free, but if you're starting from scratch there's more to consider.
I've been self-hosting for over a year now, and the storage does add up. The postgres DB is 11GB, and pictrs service is getting bigger at 29GB. Between all the different services, it can eat up a decent bit of CPU. My (admittedly 10 year old CPU) sits at a load average of 1.9, so you'll probably want 3 or 4 cores minimum. And based on my stats, 4GB of ram should be just enough to keep everything loaded.
I run https://no.lastname.nz on equivalent to oracle's free service (I do have a subscription so I can run a backup etc) and before that it was on a vps at quantomcore https://secure.quantumcore.com.au
Alternative question– I use Zola and Github Pages to host my website. Does ActivityPub have support for blogging? Like let's say people on Lemmy or Mastodon could subscribe to my blog through ActivityPub?
From what I can tell Zola does not have anything like this (tried searching GH issues), but I just want to know if it's technically feasible. I can write Rust, so I could have a crack at it myself if it's not too cost/effort prohibitive.
Lemmy claims to be able to support any Bootstrap 5 theme as a drop-in Lemmy theme, and it's surprisingly close to being true. If you go to ponder.cat right now, you'll see one, based on Sandstone, that I've been fooling around with, because the provided Lemmy themes are mostly awful to me.
You could run one backend instance, have a main frontend to it on lemmy.whatever.com, and have a second frontend on whatever.com, with the theme set to a minimally modified version of Clean Blog or something, stripping out all the UI stuff and leaving only a blog. That would give you an RSS feed, a blog, a community that Lemmy people could follow, and a Fediverse actor that Mastodon people could follow, all in one place with all the comments unified. If you want to set the theme up that way, I can give you pointers, since I've just now been working on this for my instance.
Does ActivityPub have support for blogging?
From what I researched some time ago: There are/were some federated blogging systems out there but they’re all stuck in the pre-Docker era installation-wise and technology-wise (i.e. just outdated).
But in the end it makes no sense in my opinion. Blogs nowadays are just publishing and less networking/interaction.
A simple file loader and markdown parser could be enough. I set up my page based on Apache directory listing, a custom Action to parse markdown files, and some fancy CSS. There is figuratively nothing that runs my page, except a web server and a markdown parser.