I frequently amaze new colleagues when I show them that deploying an update for our backend application is a sub-second affair. Our pipeline keeps track of what git tag was deployed last, diffs between that tag and the new release, and uploads the files to each of the deployment targets. It takes longer for the pipeline agent to spin up from Cold on a Monday morning, than it does to actually deploy.

The core of the application is just php scripts, and those are either immediately up to date whenever the next call is, or swapped out the next time that component finishes a processing cycle.

Docker containers are nice, but nothing beats the cause of a stack trace being fixed, tested and deployed to the acceptance environment within minutes of it arriving.

I mean, for 10 bucks anything is a decent deal. Those specs are pretty decent for a simple home server. I’m not familiar with HP thin clients, but I assume you can install a Disdro of your choice on it? My big reason to avoid HP is their crap software and warranties, both of which are moot here.

I would say relatively light software like tailscale, pihole and such would be fine. Docker containers might be pushing it, but that depends largely on what containers you want to run, same goes for nginx; by itself the requirements are fairly low, it depends on what you want to run on it.

Jellyfin might be a stretch, and as you alluded to, real-time transcoding is probably out. It strongly depends on the decoding capabilities of that chip and wether it does hardware decoding or if it all happens in software. The latter might be too much for it. If it can handle it though, it might be interesting as a media player hooked up to a TV, rather than acting as a transcoding or DLNA-esque server.

Thanks! I will pass it along and hopefully we can push for a change. I can’t guarantee that anything will happen in the short term, but at the very least we can create some bad publicity for them.

Hey Op, since you appear to be somewhere in the EU based on your mention of Euro pricing, would you be willing to name and shame the wheelchair manufacturer and/or model?

Without giving too much of my own personal information away, I might be in a position to cause a bit of ruckus for this particular company in terms of bad PR, possibly legislatively. I work for a company that profiles itself on doing this stuff “the right way” (secure practises, not screwing users this way, etc) and we are working on building a list of practises we are hoping to root out EU-Wide with some examples that are clearly exploitative.

I need nothing personally identifiable, just the brand and model, and I can pass it along to the team that can investigate further.

Everyone else is just telling you to do things in a way that is different, and while they are correct (you should use a unit.d/systems script for this depending on your distro), I’m going to actually answer your question since I know sometimes you just need a quick and simple way.

Depending on your version of cron, it may support special statements instead of the * * * * * notation for time.

The one you want is @reboot. Replace all entries of the schedule syntax with that, including the @, and the command will be executed only once when the system boots up.

Use that to start a script that checks for network connectivity on a loop with a sleep statement. Break the loop when you have connectivity, then execute your command, and exit the script.

Don’t ignore the correct way though. You’re better off executing this as a systemd (or equivalent) script. It’s barely more effort, and has the benefit of some nice built in logging and integrations.

I have some bad news…