Goofed Home

Using #Madblog as the easiest way to spin up an Indieweb/ActivityPub-compatible blog.

Zero db, zero JS, entirely hosted on text files.

it works so well that it federated into this community twice! /s

Looks similar to Plume, the “no DB required” is neat though!

I finally set up a VPN instead of exposing unnecessary ports to the wild!

A hopefully “success in progress”: I am building a new trueNAS server for storage. I have a k8s cluster and am currently using rancher for storage, but I decided at my scale central storage made more sense & would be easier to manage. I am also using that opportunity to upgrade from 2TB usable storage to 44TB usable storage. Fingers crossed everything will work 🤞

cross-posted from: https://lemmy.nocturnal.garden/post/552459

For a hobby of mine, there’s an outdated lore wiki on Fandom. I dislike Fandom and would like to host an alternative. It’s supposed to be accessible to all kinds of people.

I started with mediawiki as that’s what Fandom and Wikipedia are using, so people would be familiar with page structures at least and maybe the editor.

It turned out to be a bit of a pain though. It only has unofficial container images, the documentation is outdated and (what I consider as) core functionality like WYSIWYG editor or simple infoboxes has to be added by extensions or templates. I’m in the process of setting it all up and wondering if it’s worth it (and if I want to maintain it). There’s so many wiki projects it’s hard to keep track, what are y’all using for stuff that’s used by larger communities and simple to use with close-to-default settings?

Not at all! I did poke around some random pages after you helped me, sorry I didn’t come back to my. Thanks for sharing the update, I’m keen to see how you’re using DW.

Judging by how productive I’ve been just in the last 8 hours, I’d say going from Mediawiki to Dokuwiki was a good choice. I’m not even sure why. DW still uses markup instead of a WYSIWYG editor, which I’m fine with. I think it’s the namespaces. MW does have them, but you have to set them up with a config file on the server, and adding and removing them cannot be done lightly. With DW it’s as easy as searching for new_namespace:some_new_article, and the namespace is created along with the article. So I have a scratchpad namespace where I can work on drafts, a stories namespace to put my attempts at creative writing, a lore namespace for, well, canonized lore tidbits, and so on. And I don’t need to worry about names colliding like I did with MW where lore articles and story titles often conflicted.

DW lets you use hierarchy when it works, and loose categories (tags) when it doesn’t (with the tags plugin that is). With MW you just have categories but no hierarchy. Bookstack is the opposite. It forces you to use its shelf>book>chapter>page organization system. It does have tags, too, but you can’t have pages outside of books, and the pages have an explicit order. You can fairly easily change that order, but it’s always there.

Back to DokuWiki, the blog plugin has proven invaluable over the last few days. I can jot down ideas as blog entries and push them to the main lore namespace if I think they’re worth keeping.

The title says basically everything but let me elaborate.

Given the recent news about the sold out of harddrives for the current year and possibly also the next years (tomshardware article) I try to buy the HDDs I want to use for the next few years earlier than expected.

I am on a really tight budget so I really don’t want to overspend. I have an old tower PC laying around which I would like to turn into a DIY NAS probably with TrueNAS Scale.

I don’t expect high loads, it will only be 1-2 users with medium writing and reading.

In this article from howtogeek the author talks about the differences and I get it, but a lot of the people commenting seem to be in a similar position as I am. Not really a lot of read-write load, only a few users, and many argue computing HDDs are fine for this use case.

Possibilites I came up with until now: 1. Buy two pricey Seagate Ironwolf or WD Red HDDs and put them in RAID1 2. Buy three cheaper Seagate Barracuda or WD Blue and put two in RAID1 and keep one as a backup if (or should I say when?) one of the used drives fails.

I am thankful for every comment or experience you might have with this topic!

It is a gamble, fuck the my butt bozos for speculating us into economic uncertainty

F in the chat for your savings, least you’ve got the peak of home NASes. Pretty fuckin cool and I hold out hope when the drop comes in a… 6 months to 3 years…? that I’ll be able to afford full SSD NAS life. The power savings, the speed, the no worries of shock or vibrations, the silence - jealous

Tangled is also a new Git forge built on ATProto, the protocol used by Bluesky

Me neither, I only stumbled across this a couple of days ago. I don’t use Bluesky but I heard that it’s not really defederated because of the large amount of resources it requires. Not sure if it applies to ATProto in general. For now I’m sticking with Codeberg because what’s a federated network worth if there’s not much to federate with

Yeah Codeberg is cool. I’m on my own forgejo but it’s currently local only and that won’t change until federation works.

This is not directly selfhosting but related. I have 2 Proxmox hosts which both support Intel AMT which is a remote control tool similar to supermicro IPMI, supporting KVM, power cycles and more. I wanted it to be able to repair stuff in case I can’t reach the servers via ui/ssh.

I set it up and it worked fine for months. I could access both on ip.address:16992.

Lately, one of them started disappearing after days or weeks. Rebooting brings it back, but it’s a running server and I don’t want to reboot it so often. The server is working fine otherwise.

Does anyone know that problem? It’s hard to pin down since it can’t be seen on the host linux (port not shown in netstat for example).

Apologies. I misread apparently. I thought your Proxmox boxes were disappearing.

They’re right here in the shelf :-)