I enjoyed using Asciidoctor to write a book. It necessitates using a text editor instead of a word processor so it doesn't fit DJ's use case, but it really is quite nice.
I'm also fascinated by the build for Ada & Zangemann, a FOSS illustrated full-color children's book. It looks rather complex, but it handles translations, beautiful typesetting, and was remarkably fast when I tried running the build locally.
Many other tools/platforms provide decent source control and issue tracking. Nothing else has the FOSS project market share of github, and this matters especially when you're looking for the canonical home of a project and trying to judge how popular/active/viable it is (stars/commits/issues/PRs).
If you want exposure and participation for your FOSS project, it's harder to not use github.
FWIW, Forgejo does the source control stuff well. I love it for self-hosted local mirrors.
Hard pass. Another Linux laptop with another sus distro won't teach anyone how to focus. Save a hand-me-down laptop from the landfill, install a known good distro, and do the hard work of culling distractions.
You're right to start with your requirements. Try to get detailed, like the list @WA wrote out, then match it up with appropriate tech.
I wrote a technical book and I also wanted multiple decent-looking outputs. In my case: HTML, EPUB/mobi, screen and print PDFs. I was struggling with Markdown+pandoc+custom scripts/styles, so I switched to Asciidoc. I wrote about that process here: https://adammonsen.com/post/2122/
Here are two examples where the author used Markdown and the result was beautiful and successful (although layout for printed editions were done with extra/other tooling): http://gameprogrammingpatterns.com , http://www.craftinginterpreters.com . I'm curious if Bob would/will use Markdown for his next book. My process is different than Bob's... I didn't need literate code and I didn't want to do _any_ layout/pre/post-processing, even for print. Asciidoctor worked for this, although there were some compromises (see my links above). Print-ready layout is a lot of work, however you do it.
Is this your first book? Do you have a publisher? Will it be printed on paper? Do you have a developmental editor / proofreader / etc? Do you have a plan for what you'll do after you publish e.g. talks/promos/tour?
Contact me if you want to chat. I'm happy to share my war stories. And good luck!
In the space of local-first finance apps, I've really enjoyed Actual Budget (as have many, based on what I'm seeing in other comments). I'll check out Wealthfolio but like @dw_arthur I'm concerned about looking at investments too much / too often. I try to invest based on personal experience / value and always go long. I use off-budget accounts in Actual to track investments/illiquid value changes and update them every 6mo-1yr. I'm sure a spreadsheet would work fine for this as well. But for someone who moves investments more frequently, Wealthfolio looks awesome.
For managing my life's data, this golden combination is always going to win: app that works well | full/local control of data | sane FOSS project governance | software license mitigates enshittification (e.g. AGPLv3)
Skimming that I'm thinking yes, sure, why not, but this repo is missing useful context. Who are you, authors? Why should I bother learning this protocol? Is anyone using or going to use this? If it's new, has it been shopped around at conferences? Any related research?
So much depends on your use case. Can you say more about that? And what have you already tried? I'm skeptical their server-side tuning suggestions will improve your "initial loading delay" depending on what that means exactly. If you mean you see a slow cold cache page load of the Files app web UI (or any Nextcloud app, really) then I'd say that's common with many complex JS-heavy web apps, including Nextcloud.
FWIW, my Nextcloud web UI seems as fast as I'd expect. Roughly 5sec to load the Files app completely in Firefox (logged-in & warm cache) and this is roughly the same time Google Drive takes to do the same thing! Navigating folders actually feels faster in Nextcloud Files.
I'm not using the web UI except when I have to. I do as much as possible locally (e.g. editing docs, contacts/calendars/tasks). I mostly use Nextcloud for mobile and desktop file/calendar/contacts/photo/notes/tasks sync & share and it seems to do quite well at this. Server-side I did spend a lot of time tuning at first, but it has been stable for years once I got it to a good place.
anacron is worth a mention here for sometimes-on computers like desktops, laptops, or personal servers. It's great for ensuring something runs at the set interval, or just whenever the machine comes back online. Minimum anacron interval is one day, so this can't simply replace cron. cron might even be the most sensible thing to use to kick off anacron on your system, and it might already be in use (see if your /etc/crontab fires off anacron).
anacron won't have the OP's 2am/3am issue because it locks jobs while they run, so multiple job spawns should be no-ops. Still seems like it would be good practice to, e.g. use UTC for the host system and do whatever else might help avoid the unnecessary re-spawns.
I noticed I was on 8 today. Running in Docker. In case this helps anyone else: Upgrade from 8 to 9 worked fine (just by switching the Docker label), then from 9 to 11 worked, and since 11 is LTS I'll stay on that for a while.
I'm also fascinated by the build for Ada & Zangemann, a FOSS illustrated full-color children's book. It looks rather complex, but it handles translations, beautiful typesetting, and was remarkably fast when I tried running the build locally.