Update luanti-server/ReadMe.md

.deprecated/jelu/ReadMe.md

@@ -1,2 +1,4 @@
 # Jelu
+A book tracker.
+
 Modified from [official instructions](https://github.com/bayang/jelu?tab=readme-ov-file#docker).

.deprecated/lemmy/ReadMe.md

@@ -1,4 +1,6 @@
 # Lemmy
+A federated reddit-style board.
+
 This is like my 3rd attempt to make Lemmy do anything, but it is fundamentally
 unable to run alongside other apps for no reason? I don't know.
 

.deprecated/yamtrack/ReadMe.md

@@ -1,4 +1,6 @@
 # Yamtrack
+A multimedia tracker.
+
 Modified from [readme](https://github.com/FuzzyGrim/Yamtrack) instructions which tell ya to use the [dev docker-compose.yml](https://github.com/FuzzyGrim/Yamtrack/blob/dev/docker-compose.yml).
 
 **WARNING**: Yamtrack, despite having a nicer aesthetic, the ability to add custom items, and being more updated, is inferior to MediaTrack in speed, usability, and presentation & availability of information.

ReadMe.md

@@ -40,3 +40,10 @@ I place these at the top of compose files for different changes that need to be
 1. Note where I got the original compose file or documentation.
 2. Add instructions.
 3. End with notes about complications or issues I ran into.
+
+## Tasks
+- [ ] figure out requirements to config a cosmos database so that its config
+      can have one specified here instead of being stuck on the host machine
+- [ ] Update EtherPad, use it, make sure it works, update table
+- [ ] Move `calibre-web-nextgen` to deprecated..
+  - [ ] Rename `.deprecated` to `+deprecated`

audiobookshelf/ReadMe.md

@@ -5,11 +5,15 @@ continuous 502 Bad Gateway errors until it resolves.
 
 Modified from official instructions: https://www.audiobookshelf.org/docs/#docker-compose-install
 
-During initial setup, you will be asked to create a library. I just call it
-"Books", use `/audiobooks` for the path, and leave everything else at default.
-
 **WARNING**: If you ever accidentally leave an old version of an Audiobookshelf
 database where a new version can see it, a restart may cause it to load the old
 database, and **its default behavior when this occurs is to delete every file it
 doesn't recognize**. Thankfully, I had backups, but I have to set up all of the
 metadata around this all over again now.
+
+**WARNING**: Audiobookshelf doesn't clean up after itself, so when you modify
+or remove items, it will bloat over time. I should replace it.
+
+## Setup
+During initial setup, you will be asked to create a library. I just call it
+"Books", use `/audiobooks` for the path, and leave everything else at default.

calibre-web-automated/ReadMe.md

@@ -1,2 +1,7 @@
 # Calibre Web Automated (CWA)
+Ebook manager.
+
+**WARNING**: Should be assumed insecure and kept behind a secure proxy.  
+Pinned to a specific version due to fears over changes and instability in future versions. Abandonware possibly.
+
 Modified from [official instructions](https://github.com/crocodilestick/Calibre-Web-Automated?tab=readme-ov-file#using-docker-compose-recommended).

calibre-web-automated/docker-compose.yml

@@ -30,7 +30,7 @@ volumes:
 
 services:
   calibre-web-automated:
-    image: crocodilestick/calibre-web-automated:latest
+    image: crocodilestick/calibre-web-automated:v4.0.6
     container_name: calibre-web-automated
     environment:
       # Only change these if you know what you're doing

calibre-web-nextgen/ReadMe.md

@@ -1,3 +1,5 @@
 # Calibre-Web-NextGen
-Community maintained version of CWA with many fixes and improvements.  
+~~Community maintained version of CWA with many fixes and improvements.~~  
+AI-slop version of CWA maintained entirely by bots as far as I can tell.  
+More features and fixes, but also highly unstable and power-hungry.  
 https://github.com/new-usemame/Calibre-Web-NextGen

calibre-web-nextgen/docker-compose.yml

@@ -30,7 +30,7 @@ volumes:
 
 services:
   calibre-web-automated:
-    image: ghcr.io/new-usemame/calibre-web-nextgen:latest
+    image: ghcr.io/new-usemame/calibre-web-nextgen:v4.1.37
     container_name: calibre-web-nextgen
     environment:
       # Only change these if you know what you're doing

cosmos-server/ReadMe.md

@@ -2,7 +2,8 @@
 **WARNING**: A database is set up by the UI using a volume instead of a bind
 mount, so this setup is ***not*** self-contained.
 
-Host mode networking needs to be explicitly enabled in Docker Desktop on macOS.
-
 Newer docker compose versions will complain about the `version` directive, but
 it is kept for backwards compatibility.
+
+## Setup
+Host mode networking needs to be explicitly enabled in Docker Desktop on macOS before attempting to run this.

etherpad/ReadMe.md

@@ -1,2 +1,4 @@
 # Etherpad
+**WARNING**: Etherpad cannot handle power interruptions gracefully.
+
 https://docs.etherpad.org/docker.html#ready-to-use-docker-compose

immich/ReadMe.md

@@ -1,7 +1,7 @@
 # Immich
 This was created following the [Docker Compose installation guide](https://docs.immich.app/install/docker-compose/).
 
-WARNING: Does not work with docker-compose.
+**WARNING**: must use `docker compose`. Does not work with older `docker-compose` script.
 
 1. Edit `docker-compose.yml` to set directories and a database password.
 2. Create directories needed: library, database, model-cache

luanti-server/ReadMe.md

@@ -7,10 +7,13 @@ may need some changes after it is generated to better support starting your serv
 
 ```
 name = admin                   # Sign up as this user name to have admin rights.
+enable_tnt = true              # only if you want TNT (some mods require this)
 secure.http_mods = digistuff   # optional feature
-enable_tnt = true
 ```
 
+Don't forget to actually install a game before trying to run.
+The provided config assumes you are playing `minetest`.
+
 Note that admin rights are not the same as in-game permissions,
 you still need to use `/grantme all` to get all permissions,
 and `/revokeme creative` if you don't want creative mode.

luanti-server/docker-compose.yml

@@ -1,6 +1,7 @@
 # TODO set volume directories
 # TODO change ALL_CAPS environment variables in all locations
-#       (this is just WORLD_NAME here - it CANNOT have special characters or spaces, and must not start with a number)
+#       WORLD_NAME cannot have special characters or spaces, and must not start with a number
+
 # Normally, I use external management to open up ports, but the definitions here are necessary.
 
 volumes:
@@ -11,12 +12,10 @@ volumes:
       o: bind
       device: /Volumes/Treat/Containers/luanti-server/server
 
-name: luanti-server
-
 services:
-  luanti-server:
+  luanti_server:
     container_name: luanti_server
-    image: lscr.io/linuxserver/luanti:5.15.2
+    image: lscr.io/linuxserver/luanti:5.16.1
     restart: always
     # networks:
     #   - default
@@ -24,6 +23,8 @@ services:
       - TZ=America/Denver
       # do not use --terminal or --server or --worldname
       - "CLI_ARGS=--gameid minetest --world /config/.minetest/worlds/WORLD_NAME"
+      - PUID=1000
+      - PGID=1000
     volumes:
       - LUANTI_SERVER:/config/.minetest
     ports:

miniflux/ReadMe.md

@@ -1,4 +1,6 @@
 # Miniflux
+**WARNING**: Cannot handle power failure.
+
 Modified from [official instructions](https://miniflux.app/docs/docker.html).
 
 ~~I commented out the stuff to create the initial user because I'm running this

vikunja/ReadMe.md

@@ -1,7 +1,10 @@
 # Vikunja
-**WARNING**: After a power failure, permissions were reset on the volume this
+**WARNING**: Inconsistent around power failures. Sometimes it comes right back,
-app was using, causing it to fail. I have no idea how that occurred. Permissions
+sometimes it breaks until restarted several times.
-must be user/group 1000 for this to function.
 
 1. [What to backup](https://vikunja.io/docs/what-to-backup/)
 2. [Configuration options](https://vikunja.io/docs/config-options/)
+
+**WARNING**: After a power failure, permissions were reset on the volume this
+app was using, causing it to fail. I have no idea how that occurred. Permissions
+must be user/group 1000 for this to function.

wordpress/ReadMe.md

@@ -1,4 +1,7 @@
 # Wordpress
+**NOTE**: This instance will be replaced with custom blog hosting software, as I'm sick
+of all the terrible decisions and bad security of Wordpress.
+
 This instance has a long history, as I've migrated my blog several times. As a
 result of previously not keeping records, I've lost some of the history of how
 it got here.