nextcloud / nextcloud/richdocuments
Suggested richdocumentscode install command doesn't work in all situations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Describe the bug
richdocumentscode can in many cases not be installed via the web interface due to timeouts. As a result, richdocuments (rightly) suggests installing using occ if it doesn't work. See here:
However, that command assumes that one has installed Nextcloud manually instead of using e.g. the snap, where the comand doesn't work. It should be trivial to check the $SNAP and $SNAP_NAME environment variables and print the proper command in that situation (sudo nextcloud.occ app:install richdocumentscode specifically), but I'm afraid I don't quite have the vue chops to pull it off.
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
Start in src/components/AdminSettings.vue around line 91, where the suggested occ installation command is assembled. Check how the $SNAP and $SNAP_NAME environment variables can determine the displayed command. Done means Snap installations show sudo nextcloud.occ app:install richdocumentscode while other installations retain the existing command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100