fbartels

joined 1 year ago
[–] [email protected] 1 points 1 year ago (1 children)

What are other products in this kind of space? Something where you could get some stats from the host and docker and have the ability to control containers through a web interface (like pulling new containers, restarting, changing env variables)?

[–] [email protected] 1 points 1 year ago

No, cpu wise there should not really be an overhead, as it just uses docker or podman to run the application in question. the only bottleneck i see could be host filesystems that are not supported by docker/podman and therefore could lead to slow file access in the container.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (3 children)

In the end you could use any distro which desktop you like (which could be Debian stable, or something immutable) and then get your applications from the latest and greatest with Distrobox

[–] [email protected] 8 points 1 year ago (4 children)

If you like web tools maybe https://github.com/Frooodle/Stirling-PDF could be something for you.

[–] [email protected] 2 points 1 year ago

The article says:

The Nokia G22 will cost from £149.99 shipping on 8 March with replacement parts costing £18.99 for a charging port, £22.99 for a battery and £44.99 for a screen.

 
[–] [email protected] 1 points 1 year ago

I do remember my joy, when finding out that instead of feeding it with batteries, I could even use the power adapter of the master system to play with the Gamegear. 😄

[–] [email protected] 2 points 1 year ago

Congrats on the impressive 0.0.1 version. The one thing that I was missing in Mlem, that is also not part of this app is ipados support.

[–] [email protected] 5 points 1 year ago

Another +1 for restic. To simplify the backup I am however using https://autorestic.vercel.app/, which is triggered from systemd timers for automated backups.

[–] [email protected] 2 points 1 year ago (3 children)

You’ll have to use http://192etc:port. So no httpS for internal access

This is not really correct. When you use http this implies that you want to connect to port 80 without encryption, while using https implies that you want to use an ssl connection to port 443.

You can still use https on a different port, Proxmox by default exposes itself on https://proxmox-ip:8006 for example.

Its still better to use (sub)domains as then you don't have to remember strings of numbers.