The 2023 forum post is essentially a pointer to an external BigBearCasaOS tutorial, not a complete installation record. The good news is that the underlying package is still maintained: BigBearCasaOS continues to list code-server using the LinuxServer.io image.
A current deployment should focus on persistent configuration/workspace, the correct user/group identity for mounted project folders, and authentication. code-server gives a browser shell/editor access to your files, so exposing it casually to the public Internet is much higher risk than exposing a read-only media dashboard.
BigBearCasaOS Still Maintains code-server
The current BigBear package maps persistent configuration and project folders and exposes the LinuxServer code-server WebUI through a host port.
See the current BigBear code-server package.
Persist /config
LinuxServer's current code-server image stores relevant configuration under /config. Keep that directory on CasaOS AppData or another persistent storage location so user settings, SSH configuration, extensions, and workspace state survive container recreation.
Map the Real Project Folder Deliberately
BigBear also exposes a project volume. If the source code already lives on a NAS share or storage disk, map only the folder tree code-server actually needs rather than giving it broad write access to the whole NAS.
Use the Real PUID and PGID
The current LinuxServer image supports PUID and PGID so files created through the browser editor can match the host ownership model.
Run id username on a normal CasaOS Linux host to identify the user/group rather than assuming 1000 is always correct.
Set Authentication Before Normal Use
LinuxServer supports PASSWORD or HASHED_PASSWORD. If neither is set, the WebUI can run without authentication.
Use the current code-server container guidance.
Treat SUDO_PASSWORD as a Powerful Optional Feature
The image can expose sudo inside the container when configured. Do not enable it merely because an old tutorial shows a field. A browser-accessible development container with sudo is more sensitive than a normal unprivileged editor.
Prefer LAN, VPN, or a Hardened Reverse Proxy
If code-server must be reached remotely, use an authenticated VPN/overlay or a carefully configured HTTPS reverse proxy. Protect SSH keys, Git credentials, terminals, and source code stored under the workspace.
Update by Recreating the Container, Not by Modifying the Image Internally
LinuxServer recommends pulling the newer image and recreating the container with the same persistent /config mapping. That keeps the container disposable while user state remains outside it.
code-server on CasaOS FAQ
Is the 2023 forum post itself a complete current installation guide?
No. It points to an external BigBear tutorial.
Is BigBearCasaOS still maintaining code-server?
Yes. The current BigBear catalog still includes the LinuxServer code-server package.
What is the most important persistent path?
/config, plus any separate project/workspace folder you intentionally map into the container.
