I'm sorry, but that's not a fence, it's just a vertically mounted array. Would OP really have built a regular fence there?
It'd probably be less labor and material intensive to just build a single structure holding the entire array using much longer rails instead of setting posts and rails every 6-7 feet. To keep costs lower you could also go with a string inverter instead of the ~$1500 you'd need for microinverters.
Pricing conveniently doesn't include the panels, so you just have a set of posts and some horizontal racking.
Holding that much cash is already insane, considering inflation. In coins? Huge liquidity problem. Good luck finding enough buyers to make 10-20 cents off a single coin.
It sounds more like poor choices. 6 staging environments sounds a bit overkill.
If you can fit them all on a 4 cpu / 32gb machine, you can easily forgo them and run the stack locally on a dev machine. IME staging environments are generally snowflakes that are hard to stand up (no automation).
> you can easily forgo them and run the stack locally
Not if you're running with external resources of specific type, or want to share the ongoing work with others. Or need to setup 6 different projects with 3 different databases at the same time. It really depends on your setup and way of working. Sometimes you can do local staging easily, sometimes it's going to be a lot of pain.
The word "host" is ambigious. Hosts can be virtual or physical.
Self-host to me is a verb, which mean you're running the service, regardless of what hardware it's on. On-prem is better descriptive word for physical hardware.
> You'll likely spend thousands less on maintenance on an EV.
I don't spend many thousands on maintaining an ICE to begin with.
I've kept track of all car expenses since 2008 for 3 different cars. My average per year is $445. This is repairs and maintenance.
I'm not a gearhead. I know little about cars. I do whatever repairs my mechanic suggests. Things just don't break down much with reliable ICE cars.
TCO calculators are, in my experience, off by an order of magnitude. Ignore them.
> The few oil changes on my recently out of warranty 2021 Toyota
Are you doing them at the dealer? You're likely paying too much. And are you doing them on the manufacturer schedule or have you fallen prey to the "Every 3 months or 3000 miles" propaganda?
Most cars need it every 6 months. And unless your car needs some high quality oil, it's typically about $40 to get a regular mechanic to change it. So $80-100/year.
I have a car over 20 years old. I don't spend much money on maintenance. I don't have a car payment, taxes are very low, and insurance is decently cheap. Had it for a few years, have replaced brakes and some minor things. Didn't spend much on the vehicle, either.
Having a car payment would automatically be more expensive than my current vehicle. More taxes, more money each month, and so on. For electric cars, I won't get the incentives here in Norway for much longer, as they are being (mostly) phased out in the next few years.
To be fair, though: I walk a lot. I have a 5-10 minute walk to work (depending on snow). Driving takes longer. The car is used a few times a month. Realistically, my car is a luxury item and I'm lucky to live in a place that makes it so.
This feels like a contradiction to what Flask (and) htmx are. There are way too many abstractions going on. Also I don't see any integration with htmx at all?
I was expecting something like what FastHTML does where htmx is essentially built in.
Self hosting is great and I'm thankful for all the many ways to run apps on your own infra.
The problem is backup and upgrades. I self host a lot of resources, but none I would depend on for critical data or for others to rely on. If I don't have an easy path to restore/upgrade the app, I'm not going to depend on it.
For most of the apps out there, backup/restore steps are minimal or non existent (compared to the one liner to get up and running).
FWIW, Tailscale and Pangolin are godsends to easily and safely self-host from your home.
Every selfhosted app runs in docker, where the backup solution is back up the folders you mounted and the docker-compose.yml. To restore, put the folders back and run docker compose up again. I don't need every app to implement its own thing, that would be a waste of developer time.
+1 for the above... all my apps are under /app/appname/(compose and data)... my backup is an rsync script that runs regularly... when I've migrated, I'll compose down, then rsync then rsync to the new server, then compose up... update dns, etc.
It's been a pretty smooth process. No, it's not a multi-region k8s cluster with auto everything.. but you can go a long way with docker-compose files that are well worth it.
I would rather use headscale than netbird. Headscale is well established and very stable. netbird has a lot of problems and the fact their issue list is hardly looked at by the devs is more concerning
I do give credit to Steve Jobs. I was saying that what Jony has done on his own is less impressive IMHO.
If they manage to pull this off (OpenAI/io) then I will, begrudgingly, have to give credit to Altman, despite not being a huge fan of him (then again, Jobs wasn't a "good guy" in many aspect of his life either).
My point being, Jony needs an editor, when he was unchecked at Apple (or his own design company "Love From") I found that much of his output came across as an exercise in smelling one’s own farts.
It'd probably be less labor and material intensive to just build a single structure holding the entire array using much longer rails instead of setting posts and rails every 6-7 feet. To keep costs lower you could also go with a string inverter instead of the ~$1500 you'd need for microinverters.
Pricing conveniently doesn't include the panels, so you just have a set of posts and some horizontal racking.
reply