![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
This could be as ubiquitous as location and be widely popular.
Could be, but I don’t really see the value compared to location.
This could be as ubiquitous as location and be widely popular.
Could be, but I don’t really see the value compared to location.
Any special requirement for Alpine, or just “because I want to”?
I’d be a bit concerned with having the git repo also be hosted on the machine itself.
Please tell me you have a tested backup solution/procedure in place.
Yeaaah… No.
I’ve had good experiences with most modern Dell Laptops. Also Thinkpads. What’s “budget range” to you?
Are you refering to this comment?
https://mastodon.social/@popey/112591863166141029
@bytebro Yeah, their butchered Ubuntu install, and anti-snap stance is anti-consumer.
Do you have a server, connection and domain available?
If yes, a simple Joomla setup with a single static page should work well.
Reporting is done by users who voluntarily upload their system specs via
# hw-probe -all -upload
So not skewed at all…
Nice haul! I hope you also managed to get the small power plant for the drives. That’s not going to be pretty.
That’s most likely the syslog. Check the settings, you can choose the volume to use for it.
Which is one of the occasions that a Dev sticks to the original feature list instead of trying to shoehorn in some features which wouldn’t really fit.
While I do love Syncthing, it solves a different set of requirements.
Grafana + Prometheus + data gathering will at least give you the resource and usage stats.
Subtitles being “burned into” the frames instead of being a separate track, also known as hard-coded sometimes. This enables one to use subtitles on devices which cannot traditionally use them or screw up the display. But this means the server needs to re-encode each and every frame, which is a massive load on the server.
Considering it’s basically just a script “frontend”: wireguard and its documentation.
That setting also takes host names. As long as both containers share at least one network, put in the service name (not the container_name!), e.g. “npm” or whatever yours is called and you should be fine.
As you need an installation medium anyway, get those packages while you’re at it, then install them on the VM.
What are you using as a database? Also, from which Gitea version to which Forgejo version did you attempt the migration?
I’ve traveled quite a lot with my camera, and never thought afterwards “Ah, if only I knew which temperature they were shot at…”
Considering there’s been basically zero implementation at the moment, neither open source nor commercial, there probably is no demand for a feature like this.