this post was submitted on 06 Jul 2025
31 points (100.0% liked)

Selfhosted

46677 readers
1106 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I have quite a few self-hosted services, both on machines at home and on a VPS. And there are even more odds and ends I've written that do things on my home network. A one-person maintenance team runs into serious memory limitations, particularly for the services that just run fine for years at a time.

After running into the frustration of forgetting how to run Nextcloud upgrades on the command line for the nth time, I realized it was time to write a tool.

The system wayfinder is what came out of that frustration. It lets you leave notes and commands in place around your infrastructure. After dogfooding it a bit, I was delighted when it saved me a ton of trouble dealing with one of my docker containers.

I took some time to work on it proper, wrote it up, and put it on GitHub, even though it is still a pre-release. Would you use a tool like this? What else would you want in it?

Edit: adding link to GitHub https://github.com/robbieh/way

you are viewing a single comment's thread
view the rest of the comments
[–] sxan@midwest.social 5 points 9 hours ago (4 children)

Maybe! How is it better than keeping a README?

If it's just a command, I put it in a readme. If it's a series of commands, I put it in a shell script. What would your tool bring to the party, and if I'm going to turn to a third party solution, why shouldn't I use Salt or Puppet instead?

[–] Nundrum@yall.theatl.social 1 points 9 hours ago (3 children)

For just a couple of reasons. One is the shell integration to remind me that the notes are there. The other is making it a standard tool with standard formats and expectations. I find there's a little bit of magic in that.

As for Salt and such systems, this is way far away from anything like that. It is not intended to run your infrastructure for you.

[–] sxan@midwest.social 2 points 9 hours ago (2 children)

Publish that puppy. It can't hurt.

Don't do it in github, though. Sourcehut is better; or if you crave that cluttered, JS-heavy feel, Gitlab.

[–] WhyJiffie@sh.itjust.works 2 points 4 hours ago

why not codeberg? kind of lightweight on JS, but especially compared to gitlab.

@Nundrum@yall.theatl.social

load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)