8000 docs: add backend contributing guide by mtojek · Pull Request #18077 · coder/coder · GitHub
[go: up one dir, main page]

Skip to content

docs: add backend contributing guide #18077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 32 commits into from
May 30, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix lint
  • Loading branch information
mtojek committed May 28, 2025
commit a4ce2c335f43a009524a7aac94eb72d8ee179691
6 changes: 3 additions & 3 deletions docs/contributing/backend.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ git clone https://github.com/coder/coder.git
cd coder
```

2. Run the development script to spin up the local environment:
1. Run the development script to spin up the local environment:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could add a quick explainer what the develop script does to deepen the understanding? (I.e. spins up coderd with embedded postgresql, creates an admin and a member user, prepares an initial template, etc.)

Also, are all of these intentionally 1.?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In theory, Markdown should auto-number, but I think this might only work if the content beneath is indented correctly.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Markdown linter enforces 1.-numbering, so I hope this will work. Once we've finished the technical review, I'll politely ask Edward to verify.


```sh
./scripts/develop.sh
Expand All @@ -35,7 +35,7 @@ This will start two processes:
* http://localhost:3000 — the backend API server, used primarily for backend development.
* http://localhost:8080 — the Node.js frontend dev server, useful if you're also touching frontend code.

3. Verify Your Session
1. Verify Your Session

Confirm that you're logged in by running:

Expand All @@ -45,7 +45,7 @@ Confirm that you're logged in by running:

This should return an empty list of workspaces. If you encounter an error, review the output from the [develop.sh](https://github.com/coder/coder/blob/main/scripts/develop.sh) script for issues.

4. Create a Quick Workspace
1. Create a Quick Workspace

A template named docker-amd64 (or docker-arm64 on ARM systems) is created automatically. To spin up a workspace quickly, use:

Expand Down
Loading
0