[jcook818]

Several ways - arkOS already has a tool (https://github.com/jacook/logrunner) for buffering logs in RAM before they are written to disk, thus reducing probably the top cause for SD card wear on webserver Pis. Its RAM footprint is lightweight, and it makes a huge difference over time. Secondly, with a successful crowdfund campaign the project will be able to install both to SD card AND to a USB-connected drive. Meaning that boot gets written to SD and data is stored on an external device, something more hardy than a cheap SD card. :) Finally, backup services (plural because there will be a couple different options for people to choose from) will be made a part of the core framework, making regular backups easy and data loss less of a nightmare.

[zapt02]

Logrunner seems very useful, will try it out.

With a powered USB drive it would be a nice setup!

But I feel that Drydock and arkOS CONNECT do not fit your model. Setting up central backup and a VPN for your Pi is essentially just another service. The point of this was to get rid of the middleman, yet you conveniently introduce yourself as one?

[jcook818]

I totally understand the impression. But the goal with arkOS is to help people securely self-host with as much stability as possible. Since self-hosting is a complex and occasionally troublesome thing, some people may need help in getting properly connected. So the only reason we consider hosting those services is to help with these ends. If someone needs the services in order to self-host, I think it is better that they use them, rather than not being able to self-host at all. Any services will be 100% optional and up to the end user.

[zapt02]

I appreciate you taking the time to write informed answers!