feedback: Tarantool Cartridge developer’s guide
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
<…>ocumentation.
Implementing authorization in the web interface
|To implement authorization in the web interface of every instance in| a Tarantool
cluster:Implement a new, say, auth module with a <…>
https://www.tarantool.io/en/doc/2.3/book/cartridge/cartridge_dev/
Cartridge provides default auth callbaks, but they are not described in the docs
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 with the Tarantool Cartridge developer’s guide at the linked URL, especially the “Implementing authorization in the web interface” section. Review how Cartridge’s default auth callbacks are used, then document those callbacks in the developer’s guide. Done means the default callbacks are described where users look for web-interface authorization guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100