Setup: the occ command differs for Codespaces (audit the whole path)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
The "Common commands" section gives a single universal occ command that only works for local docker-dev:
./scripts/occ.sh nextcloud --
Codespaces users need:
docker exec master-nextcloud-1 sudo -u www-data php occ
So anyone following the Codespaces path hits a failing command in a section presented as universal.
Scope
Split the occ guidance by environment in content/shared/setup.md. The module already has per-OS paths (macOS / Ubuntu / Windows / Codespaces), so the structure to hang it on exists.
Worth auditing the whole Codespaces path while in there — this was flagged as a "Codespaces path audit" and this command is the known instance, not necessarily the only one.
Done when
Each environment shows the occ invocation that actually works for it, and the Codespaces path has been walked end to end.
Identified 2026-06-17.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read content/shared/setup.md and compare the existing macOS, Ubuntu, Windows, and Codespaces paths, starting with the Common commands section and its occ invocations. Walk the Codespaces path end to end, then update each environment's occ guidance and verify that the documented commands work for their intended path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php, shell
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100