As part of a much larger project that was all-in on Java to begin with, I’ve used Tomcat to serve pages and PDFs/office doc formats rendered based on a postgres backend and FreeMarker templates.
For these purposes, you don’t want that level of complexity (or Java) but the general premise and template libs should be available in nearly any sane web programming language.
There’s an SOL on rape in most scenarios.
But no statute of limitations on copyright violations? WTF?
Have made numerous mockups for devs, as a PM, that way.
When you have one style sheet for users and admins, you get creative.
At the time, building it wasn’t my problem. Explaining what needed to be built was, and the devs in question were not native speakers of same language I was.
Show, not tell, works quite well IFF you recognize immediately when it’s needed.
Copy the thing you want from where it is, paste it where it needs to be, and tweak the (easily recognisable by any human, cmon) verbiage.
I’m not a particularly visual person, so dev tools was quite useful for that. “${foreach} state, ${foreach} county, ${foreach} postal code,” here is the expected UI both expanded and not, beats hell out of trying to spec out what amounts to the better part of an RFC, especially when I am not the one actually writing the code and also not the one who came up with the straight up crazy schema.
Schema created years ago, and there’s only money to add this UI to replace an UPDATE WHERE that the boss decided he didn’t like because he didn’t “get it” and couldn’t personally do it if ever needed (literally no world where it would be needed, and boss didn’t understand the geo that made the whole thing necessary, but…. That’s life.)
(Edit: created, not ‘creates’, and FreeMarker is brutal. Things that binary work/do not work belong in code, not templates. Templates should be as tolerant as is sane given a use case. Boss wouldn’t know HTML or a variable if I whacked him over the head with a variable (length walking staff))
Not aware of a FOSS 1:1, but that sounds like Ghost or your blogging platform of choice.
Except WP, if self hosting, IMHO. Wordpress == PHP == trouble and risk. I don’t mean to malign WP specifically, but if you’re a noob, you want to avoid exposing PHP to the public internet - especially if there’s any possibility you’ll eventually forget about maintaining and upgrading.
Just too damn easy for some threat actor to come along and exploit a vuln you missed, in the software or the web server or WP.
That said, years of WP taught me that, roughly, you want “pages” linking to “posts” ( == chapters). In theory, the former is a permanent reference and the latter is dynamic to some degree.
In reality, the existence of search engines before enshittification means the two have been conflated frequently.
Pages would often get links in a sidebar or menu. Posts might get buried much farther down, but can also be linked to. They’re often, but not always, time—specific.
“2023 NY [financial product] Guide” (page) might well link to a years-old post about subrogation regarding an attempted BBQ of a random wild animal that went wrong and caused a fire, because it’s a positively classic example of the same that makes a great deal of sense to most people, even if they don’t understand terms like subrogation.
Post/page are distinctions that WP makes, but are abstractly relevant to setting up abs any CMS (which is what you want, Content Management System) so that you (ideally) never have to figure out how or where to link something, its just native. Changing the structure means changing the URLs which is annoying at best, and fraught with peril at worst.
Above 2023 xxxx Guide page, would be https://example.org/NY-Xxxx-Guide and that way you DGAF about the sidebar links, for instance. Link it once, and then you only have to update 50 posts with the year and/or some change in the data, which can be done programmatically in the db as a trivial exercise. “UPDATE page SET title = (SELECT title FROM… WHERE ‘2022’ in title TO ‘2023’;”
Disclaimer: do not run that query as copypasta, it’s meant to illustrate a point and not to exhibit valid SQL on any db (Not least because I intentionally left out at least one closing paren and simplified a bit. I’m a PG guy, and I am 100% certain it would fail as written, but fully expect anything approaching the standard to reject it. But you get the idea, update 50 states at once with a fairly simple query, once a year.
Lots going on here, but go for a modern CMS and repeatable updates, not a legacy product with a bunch of tech debt accumulated. Build it clean, plan it out first, and know whatever DB is backing it fairly well.
Migadu has been amazing. It “”just works,”and there’s no reason to deal with any of the crap that comes with hosting email.
They are affordable, and provide exactly what they claim to provide.
Email is not - IMHO - worth the trouble to self host. There are too many hard stops where email is required as login, etc to bother.
I enjoy hosting and using a variety of services. But I’ve no desire to bother with something I can ship out to folks who live and breathe that particular service.
Open source wheelchairs; and a community of variously abled makers who can come together and build assemblies that are “not medical devices” but come together easily into something that could be used as such.
Speaking strictly for the US, and as a non-lawyer - I’m inclined to think that an open source wheelchair would probably sail right through the 510k process, but… Still doesn’t make that process cheap by any means.
I’ve had similar thoughts re: CPAP/APAP machines, neither the SW nor the HW is brutally complex / poorly understood. Pretty straightforward stuff mostly. But trying to distribute a thing like that even as plans is just asking for a C&D from the FDA, I’d expect.
Try it all. Keep good notes.
Some service names are marginally misleading, but understanding what it does and how it bills does two thing: Helps you avoid overbilling; and also ensures you “get” it.
Properly secured and understood, S3 + immutable saves my ass more than o once because could prove that as of x bi-hourly backup, PG reflected some given status.
In other words, “I did not fuck that specific thing up, and as of the last time I was in good faith awake, it looked like x. Let’s look at logs/code, bc last I saw it, it mapped perfectly to reality.”
The bit about “keep good notes,” above, is for future you.
“Oh yeah I played with that random AWS service a few years back, wish I could recall the outcome,” vs “Mind giving g me a sec to have a look at my notes, I’ve seen this before!”
That translates to execs as “Yep, I follow, and u have ref material from the last n times I solved this problem, so I’m your guy, I just need a sec to locate the details of the last round before I straight up commit to an answer.”
Boxes that physically live in my home are mostly Manjaro. They’re also not externally accessible from the internet.
Anything in the cloud I standardize on Debian. Two distros and consistency makes maintenance much easier.
Anything in a container runs whatever it was built on because porting a docker compose file from, say, Alpine to anything else is just not worth the time and energy.
From where I sit, not a lot of reason to do it. It’s a bigger pain to deal with your own CA than to just use LE.
Haven’t seen RTFM casually dropped in conversation online in… um… a while…
You’ve been hanging out on the intartoobz at least as long as I have. Circa the paleolithic era, or so…