I also have the prompt set to the host name. I’ve never understood why people included their usernames; I don’t log in to more than one account on each machine.

As long as it isn’t github.

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.

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?

If you do, use the -k option - it locks access to the rook service to only the user session. Rook works without it, but is more secure with it.

Have you ever used OwnCloud, before the fork?

I hated administrating OwnCloud, and that’s kept me away from NextCloud. OwnCloud was a big, resource hogging, hot mess; did NextCloud do a huge refactor and clean it up?

Shamelessly shilling my OSS project, rook. It provides a secret-server-ish headless tool backed by a KeePass DB.

• Headless server
• Optional and convenient integration with the kernel keyring (on Linux), for locking the server to only provide secrets to the user’s session
• Provides a range of search, list, and get commands
• Minimal dependencies and small code base make rook reasonably auditable

You might be interested in rook if you’re a KeePassXC user. Why might you want this instead of:

• Gnome secret-server, KDEs wallet, or pass? rook uses your (a) KeePass DB, while most other projects store secrets in their own DBs and require (usually manual) sync’ing when passwords change.
• One of the browser secret storage? Those also keep a bespoke DB which needs to be synced, and they’re limited to browser use. Rook supports using secrets in cron jobs or on the command line (e.g. mbsync, vdirsyncer, msmtp, etc, etc).
• KeePassXC? KeePassXC does provide a secret service that mocks Gnome secret-service, but you have to keep KeePassXC (a GUI app) running even if you only rarely use the UI. Rook can also be used on a headless machine.
• The KeePassXC command line tool? That requires entering the password for every request, making it tedious to use and impractical for automated, periodic jobs.

Rook is read-only, and intended to be complementary to KeePassXC. The KeePassXC command line tools are just fine for editing, where providing a password for every action is acceptable, and of course the GUI is quite nice for CRUD.

Agree. Set my wife up on EndeavorOS on her laptop, and every time I go in to do something I’m impressed.

I’m a tiling, terminal, minimal mouse guy, so it isn’t for me, but what I’ve seen of KDE it’s leaps and bounds better than Gnome. Some of the minimal DEs are good if you want lightweight; Cinnamon (or whatever Gnome-on-GTK3 is called) is good, and better than current Gnome, but not in the same league as KDE.

Did you look at Pelican?

I have not, but I will. I may also look at Zola, although it, too, appears at the surface level to be tightly coupled with markdown.

the template language is buggy and inscrutable

It’s just Go templates, which are pretty solid; I’d be surprised by any bugs, unless they’re in the Hugo short codes. The syntax is challenging, even if you’re a Go developer and use it all the time. It’s a bespoke DSL, and a pretty awful one: it’s verbose, obtuse, and makes some common things hard.

Go is my language of choice, but my faith gets shaky whenever I have to use templates.

I’m not a huge fan of Python; despite its popularity, it’s got a lot of problems, not least of which is the whole Python 2/3 fiasco; which, years later, is still plaguing us. However, if I can containerized it so it isn’t constantly breaking in the background when I do a system update, I’m not opposed to using a project written in it. At least it isn’t Node; I won’t let that crap onto any server I admin.

Edit: Zola has the same problem as Hugo.

Ah, Ok.

I do as (or a similar workflow): I rsync the content directory and let Hugo on the server render. My sites are public, but perhaps they’re just much smaller or not as popular; Hugo renders even my largest site in about a second, but for a large, slow, heavy-use production situation I could see a push-and-swap process for a more atomic site update.

I don’t see the degradation you do, but there are so many possible variables.

My biggest gripe about Hugo is how limited it is in supporting source document formats. There’s no mechanism for hooking in different formats, and the team is reluctant to merge PRs for other formats. When I started with Hugo, I had a large repository of essays spanning a decade and written in a variety of markup, from asciidoc (which I used for years), to reST, to markdown; and markdown is by far the worst. I was faced with converting everything to markdown, which was usually a lossy process because markdown is so limited, or not publishing all of that history. And now we have djot, which is almost the perfect plain text markup language, but I again have to first do a lossy conversion to markdown to get Hugo to consume it. It low-key sucks, and I’m actively looking for an alternative that has a more flexible AST-based model for which new formats can be added; something that consumes a format like pandoc’s AST.

Hugo has a watch mode, right? It should rebuild if it detects changes.

Ah. I was wondering where the “Hugo, but Rust” was.

I love these rewrites in other languages. They often learn from, and improve on, their predecessors in a way that having to maintain backwards compatability doesn’t allow.

Good choice. I’ve been running Radicale for years, reverse proxied behind Caddy, and it’s been solid.

Very probable! When replying, my client only lets me see the comment I’m replying to, so losing track of who said what is a common problem for me. I assumed you were OP because I didn’t think anyone else was advocating for Plebbit.

Naw, there are several good use cases for blockchain. Ask a blockchain hater how to implement an auditable change log, and they’ll re-invent blockchain and claim it’s not.

I’m only saying: you specifically mentioned Bitcoin, and then later said design goals included cryptocurrency integration. I’m not opposed to crypto, conceptually - I’m just giving a possible reason why you may be garnering downvotes.

Sure; I’m saying that there are trigger words that are guaranteed to generate negative comments: blockchain, crypto, crypto currency, and Bitcoin.

You said that you can’t understand the negative feedback. I’m giving you one reason why you might be seeing it. Lemmy and Mastodon (the AP FediVerse in general) is not cryptocurrency-friendly. If you mention “Bitcoin” in the post, you’re going to get brigaded. If someone sniffs around on the repo documentation and sees the crypto link, they’ll mention it in the comments and you’ll get brigaded.

I think there’s such a knee-jerk reaction to any mention of crypto currency, even in comparison, that even a whiff of a relationship generates negative reactions. As you say, much of it is based on no actual knowledge about the topic. It doesn’t help that there are some truly deplorable people associated with cryptocurrency, a great many bad actors, and proof-of-work was in retrospect a terrible design decision by Satoshi.

Blockchain isn’t cryptocurrency, and vice-versa, but most people can’t distinguish between the two. If there’s any mention of blockchain on the site, or especially if you mention bitcoin (as you did) you’re going to get crusaders.

Thank you, I’ll check them out.

I never considered that Alaska might be less serviced than other states, given how removed it is. It’s no Hawaii, but still.

My problem has always been finding a SIP company I wanted to give my money to, for providing a land line #. For a glorious, brief, period, I was able to do this through Google Voice. But then they got rid of that feature, and I haven’t found another provider who I like the looks of.