Add a "troubleshooting" section
Open
documentation
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
For example, use ssh to go into the VM and use the internal docker commands to find out what's wrong
- [ ] Cover debug with preevy ssh
- [ ] Cover authorization scenarios for frontend apps (domain origin in such)
Contributor guide
Research direction
Locate the documentation entry point covering preevy ssh and the existing guidance for frontend authorization scenarios. Verify the troubleshooting steps using the VM's internal Docker commands, then consider the work complete when both checklist topics are documented with actionable guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- authorization, devops, documentation, frontend
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100