nextcloud / nextcloud/documentation

Document scaling best practice to app developers

Open
#13,550 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop pending documentation
Dominant language
JavaScript
Stars
628
Forks
2.5k
Avg merge
2d 11h
Merged PRs (30d)
135

Description

  • Database:
    • Use storageId when using the fileId
    • Use generator when manipulating users and files
    • How to use snowflake IDs

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No target file, test, or entry point is named. Start by locating the database documentation section and reviewing how it currently covers storageId/fileId, generators for users and files, and snowflake IDs. Done means each checklist item has clear guidance for app developers.

Written by the indexing model from the issue text.

Assessment

Domain
databases, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.