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.

Start by spelling “finite”, then add the relevant prefixes and suffixes.

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.

DIdn’t Intel stop making NUCs?

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.)

What about designs that contain white?

I don’t know if there’s already a convention for naming Canvas-related communities, but it seems like it would make more sense for them to start with “Canvas” so they all sort together in peoples’ community lists.

Have some of the rules (like cooldown time and overdrawing penalty) vary spatially across the canvas. So there could be a “fast/dynamic” corner where it’s easy to interact and compete, and a “slow/static” corner where things stay put more (with intermediate values in between).

This could also be good feedback for future runs, because people could experience a variety of settings on the same canvas and see which they prefer.

36 pixels at once would be fine early on when there’s plenty of room and everyone’s doing their own thing, but once it starts to fill up and people start interacting more, other people need time to respond to each pixel.

Maybe have the number go down over time, or say every time you overwrite an existing pixel it reduces your total stack capacity.

Yeah, it was fun!

Canvas size, active participants, and total running time are all factors.

I liked the fact that there was enough room for everyone to get their initial designs down—once that’s out of their systems they can look around and have more spontaneous interaction. Maybe a bit more time would have allowed for more of that.

I wonder if the people who stopped at six didn’t realize you get more over time?

I did most of the labyrinth! My original idea was that it would be more of an interstitial background linking other artwork together.

If I remember right, r/place “scaled up” by adding more blank canvas. But it might be more interesting to actually scale up the previous pixels as well, so each iteration is overlaying the previous one with higher detail.

The end result wouldn’t look as empty, because it would be easier to fill large areas early on.

There are bound to be some “virgin” white pixels that end up incorporated into permanent designs.

I’ve been running two NC instances for over five years (linuxserver docker images)—one has been issue-free, and the other had sporadic issues like OP is describing… but not for the last year or so, so I assumed the issue had been fixed in an update. Or maybe the problem was the network configuration instead of NC.