I assume it’s because it reduces the possibility of other processes outside of the linked containers accessing the files (so security and stability).

CasaOS is not an operating system and more like a GUI for Docker

So it’s more like Portainer?

Internal server (Home Assistant etc.): domus
External server (Nextcloud etc.): nimbus
Router/firewall: murus

I believe so—see Wake-on-LAN.

If anyone’s interested in adding similar functionality to their own MediaWiki installation, you can use the ModernTimeline and SemanticMW extensions without the need for an AI to parse the pages for dates.

deleted by creator

One under-appreciated aspect of Docker is that it forces you to document all your setup steps in your dockerfile and docker-config files.

I haven’t tried it because I’ve read a lot of negative discussions of it—and because (by my understanding) the only reasonable use case would be if there were a large number of users and each user is likely to have copies of the same files but don’t want to expose their files to each other (so you can’t just manually de-dupe).

the tech community keeps waiting for everyday people to take the baton of self-hosting. They never will—because the effort and cost of maintaining self-hosted services far exceeds the skill and interest of the audience.

The same argument could have been used a century ago to claim that everyday people would never switch from trains to private cars, because the effort and cost of maintaining a car exceeds the skill and interest of most travelers. That may have been true at one point, and may be true again in the future—but it’s contingent on changing circumstances, not a categorical truth.

You can install and run Stable Diffusion locally (Pinokio is a versatile installer that can run SD and many other open-source AI tools as well). With SD you can build your own upscalers that are better than Upscayl, and do things like background removal too (in addition to prompt-based generation and such).

A typical use case is to forward a single port to the proxy, then set the proxy to map different subdomains to different machines/ports on your internal network. Anything not explicitly mapped by the reverse proxy isn’t visible externally.

Does it need to be accessible via API (e.g. SQL) or just a spreadsheet-style web interface?

You can use any port for SSH—or you can use something like Cockpit with a browser-based terminal instead of SSH.

If you didn’t map a local config file into the container, it’s using the default version inside the container at /app/public/conf.yml (and any changes will get overwritten when you rebuild the container). If you want to make changes to the configuration for the widget, you’ll want to use the -v option with a local config file so the changes you make will persist.

It’s similar to how Adobe Illustrator works—if you leave the default compatibility options checked, saving in PDF or native AI format results in an identical file with the only difference being the filename extension.

If the other services are exposed on local ports, you can have NPM forward to those.

For anyone confused by “Nextcloud” in the title, it’s just the blog attribution—Nextcloud isn’t involved in the acquisition.

As a casual self-hoster for twenty years, I ran into a consistent pattern: I would install things to try them out and they’d work great at first; but after installing/uninstalling other services, updating libraries, etc, the conflicts would accumulate until I’d eventually give up and re-install the whole system from scratch. And by then I’d have lost track of how I installed things the first time, and have to reconfigure everything by trial and error.

Docker has eliminated that cycle—and once you learn the basics of Docker, most software is easier to install as a container than it is on a bare system. And Docker makes it more consistent to keep track of which ports, local directories, and other local resources each service is using, and of what steps are needed to install or reinstall.

Was it RAID 0 (striped), or RAID 1 (mirrored)?

In general, a mirrored RAID is best for minimizing data loss and downtime due to drive failure, while separate volumes and periodic backups is best for recovering from accidental file deletion or malware. (I.e., if a RAID gets told to write bad data, it’ll overwrite the good data on both drives at once.)

If you want the best of both worlds with just two drives, try zfs—you can mirror the drives to protect against drive failure, and make snapshots to protect against accidental data loss. (This still won’t protect against everything—for that you should have some kind of off-site backup as well.)

Only if you’re deliberately trying to trivialize the atrocities of slavery.