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.
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.
Do you have a server, connection and domain available?
If yes, a simple Joomla setup with a single static page should work well.
Kommt stark drauf an wie du das dann betreiben willst. Soll das über WLAN erreichbar sein, oder direkt per Kabel? Sollen da auch andere drauf Zugriff haben?
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.
What are you using as a database? Also, from which Gitea version to which Forgejo version did you attempt the migration?
Na toll, den Ohrwurm hab ich jetzt wieder bis morgen…
Those are two big points though, especially the latter. At least for people concerned with selfhosting their services.
It’s the way I do all of my service backups. One separate DB container per docker stack so nothing else is in there, all the data in one folder, and off we go at 1AM.
You’re building a machine from parts. Different Mainboard, PSU, CPU and drive combinations. No real way for a system manufacturer to optimize for a specific use case and power target.
The full ATX PSU alone has a widely variable efficiency, and often not down in the low double digit power areas.
You’re not going to see similar power levels to those ARM devices. A massive part will be the drives, 3.5" drives take between 6 and 10W per drive while running.
Use Filezilla and SFTP.
Any special requirement for Alpine, or just “because I want to”?