mirror of
https://github.com/tiennm99/composes.git
synced 2026-10-11 03:13:16 +00:00
refactor: rename the code-server service directory to code-server-linuxserver
This commit is contained in:
1 parent
85b8a5b1ef
commit
a7137fcdc4
4 files changed
+8
-8
No files matched your search
@@ -91,7 +91,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`, `paseo` and `webtop` all follow this. A service with no
|
||||
`code-server-linuxserver`, `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 +101,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` and `webtop` need an
|
||||
user will not be able to write there. `code-server-linuxserver` and `webtop` need an
|
||||
explicit `chown` for this reason; `paseo` does not.
|
||||
|
||||
## Environment variable order
|
||||
@@ -187,7 +187,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` and `paseo`.
|
||||
`SERVICE_HOSTNAME` in `code-server-linuxserver` and `paseo`.
|
||||
|
||||
## Upstream sources
|
||||
|
||||
|
||||
@@ -29,8 +29,8 @@ README.
|
||||
.env # real values, gitignored
|
||||
```
|
||||
|
||||
Compose names the project after its directory, so `code-server/` comes up as
|
||||
the `code-server` project with its own network and volumes.
|
||||
Compose names the project after its directory, so `gitea/` comes up as
|
||||
the `gitea` project with its own network and volumes.
|
||||
|
||||
Each service README covers only its own service. Shared conventions live here
|
||||
and are not repeated or linked from a service, so editing one service never
|
||||
@@ -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](code-server/README.md) | VS Code in the browser, as a remote dev box |
|
||||
| [code-server-linuxserver](code-server-linuxserver/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 |
|
||||
|
||||
@@ -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
|
||||
SERVICE_HOSTNAME=code-server-linuxserver
|
||||
|
||||
# Name of the installed web app.
|
||||
# PWA_APPNAME=code-server
|
||||
@@ -1,4 +1,4 @@
|
||||
# code-server
|
||||
# code-server-linuxserver
|
||||
|
||||
[VS Code in the browser](https://github.com/linuxserver/docker-code-server),
|
||||
from the LinuxServer image, set up as a full remote dev box.
|
||||
|
||||
Reference in new issue
Block a user