Skip to content

Commit 2dd85fb

Browse files
authored
Merge bd1e9b3 into c0d62da
2 parents c0d62da + bd1e9b3 commit 2dd85fb

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/MAINTAINING.md

+15
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@
1212
- [Changelog](#changelog)
1313
- [Releases](#releases)
1414
- [Publishing a release](#publishing-a-release)
15+
- [Documentation](#documentation)
16+
- [Troubleshooting](#troubleshooting)
1517

1618
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
1719

@@ -156,3 +158,16 @@ If you're the current release manager, follow these steps:
156158
1. Update the AUR package. Instructions for updating the AUR package are at
157159
[cdr/code-server-aur](https://github.com/cdr/code-server-aur).
158160
1. Wait for the npm package to be published.
161+
162+
## Documentation
163+
164+
### Troubleshooting
165+
166+
Our docs are hosted on [Vercel](https://vercel.com/). Vercel only shows logs in realtime, which means you need to have the logs open in one tab and reproduce your error in another tab. Since our logs are private to Coder the organization, you can only follow these steps if you're a Coder employee. Ask a maintainer for help if you need it.
167+
168+
Taking a real scenario, let's say you wanted to troubleshoot [this docs change](https://github.com/cdr/code-server/pull/4042). Here is how you would do it:
169+
170+
1. Go to https://vercel.com/codercom/codercom
171+
2. Click "View Function Logs"
172+
3. In a separate tab, open the preview link from github-actions-bot
173+
4. Now look at the function logs and see if there are errors in the logs

0 commit comments

Comments
 (0)