From 18935e01a74e49921ef4fa1dbddff51274417d48 Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Tue, 6 Oct 2026 08:58:11 +0700 Subject: [PATCH] refactor: rename code-server-linuxserver to code-server-lsio and set naming rules for compose names --- CLAUDE.md | 20 ++++++++++++++++--- README.md | 2 +- .../.env.example | 2 +- .../Dockerfile | 0 .../README.md | 2 +- .../compose.yml | 0 6 files changed, 20 insertions(+), 6 deletions(-) rename {code-server-linuxserver => code-server-lsio}/.env.example (93%) rename {code-server-linuxserver => code-server-lsio}/Dockerfile (100%) rename {code-server-linuxserver => code-server-lsio}/README.md (99%) rename {code-server-linuxserver => code-server-lsio}/compose.yml (100%) diff --git a/CLAUDE.md b/CLAUDE.md index 7708db1..d7771fd 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -9,6 +9,20 @@ gitignored `.env`. Every service uses `compose.yml` — the current Compose spec name, and the shorter one. Not `docker-compose.yml`. +## Names + +A service directory is named after the software it runs. When two services +package the same software, the one that is not upstream's own image takes a +suffix naming its source — `code-server-lsio` for LinuxServer's code-server — +so both can coexist. The suffix is a directory name only, forced by the +conflict; it is not a name to copy anywhere else. + +Inside `compose.yml`, service, volume and network names follow the upstream +project's official Docker guide. Where the guide gives none, the main service +takes the image's own name (`code-server`, not `code-server-lsio`), and a +supporting container may be named for its role instead — `db`, `database`, +`cache` and the like. + ## Installing software in an image Follow the upstream project's own documented install method, or the one the @@ -91,7 +105,7 @@ directory, one mounted at `/workspace`. The home volume holds settings, credentials and CLI logins; `/workspace` holds the code. Point whatever variable selects the working directory at `/workspace`. -`code-server-linuxserver`, `paseo` and `webtop` all follow this. A service with no +`code-server-lsio`, `paseo` and `webtop` all follow this. A service with no human inside it does not — an agent such as `hermes` or `openclaw` keeps the volume layout of its official Docker guide. @@ -101,7 +115,7 @@ your extensions and logins. Check who owns `/workspace` on a fresh volume. Docker creates it `root:root` unless the image ships the directory, and an image that drops to a non-root -user will not be able to write there. `code-server-linuxserver` and `webtop` need an +user will not be able to write there. `code-server-lsio` and `webtop` need an explicit `chown` for this reason; `paseo` does not. ## Environment variable order @@ -187,7 +201,7 @@ Compose interpolation reads the deploying shell's environment before the `.env` file, so a variable must not share a name with anything the shell already exports. `HOSTNAME` is the trap: it is set inside every container, including the one Coolify itself runs in, and would silently win. Hence -`SERVICE_HOSTNAME` in `code-server-linuxserver` and `paseo`. +`SERVICE_HOSTNAME` in `code-server-lsio` and `paseo`. ## Upstream sources diff --git a/README.md b/README.md index 12a37d5..29ed64a 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ Each links to its own README for variables, ports, and storage. | Service | What it is | | --- | --- | | [alloy](alloy/README.md) | Grafana Alloy shipping host and Docker telemetry to Grafana Cloud | -| [code-server-linuxserver](code-server-linuxserver/README.md) | VS Code in the browser from the LinuxServer image, as a remote dev box | +| [code-server-lsio](code-server-lsio/README.md) | VS Code in the browser from the LinuxServer image, as a remote dev box | | [couchbase](couchbase/README.md) | Couchbase Server | | [diun](diun/README.md) | Image-update notifier, reading the Docker API through a read-only proxy | | [gitea](gitea/README.md) | Gitea backed by PostgreSQL | diff --git a/code-server-linuxserver/.env.example b/code-server-lsio/.env.example similarity index 93% rename from code-server-linuxserver/.env.example rename to code-server-lsio/.env.example index 89eb6c3..fd360c9 100644 --- a/code-server-linuxserver/.env.example +++ b/code-server-lsio/.env.example @@ -14,7 +14,7 @@ GIT_EMAIL= # Container hostname, also passed in as HOST -- the name zsh's prompt shows. # Not named HOSTNAME: the deploying shell's own HOSTNAME would override it. -SERVICE_HOSTNAME=code-server-linuxserver +SERVICE_HOSTNAME=code-server-lsio # Name of the installed web app. # PWA_APPNAME=code-server diff --git a/code-server-linuxserver/Dockerfile b/code-server-lsio/Dockerfile similarity index 100% rename from code-server-linuxserver/Dockerfile rename to code-server-lsio/Dockerfile diff --git a/code-server-linuxserver/README.md b/code-server-lsio/README.md similarity index 99% rename from code-server-linuxserver/README.md rename to code-server-lsio/README.md index 6261a1e..6ad4d34 100644 --- a/code-server-linuxserver/README.md +++ b/code-server-lsio/README.md @@ -1,4 +1,4 @@ -# code-server-linuxserver +# code-server-lsio [VS Code in the browser](https://github.com/linuxserver/docker-code-server), from the LinuxServer image, set up as a full remote dev box. diff --git a/code-server-linuxserver/compose.yml b/code-server-lsio/compose.yml similarity index 100% rename from code-server-linuxserver/compose.yml rename to code-server-lsio/compose.yml