Skip to content

docs: Improves README and documentation#227

Merged
frgfm merged 5 commits into
masterfrom
api-documentation
Oct 17, 2022
Merged

docs: Improves README and documentation#227
frgfm merged 5 commits into
masterfrom
api-documentation

Conversation

@frgfm

@frgfm frgfm commented Oct 16, 2022

Copy link
Copy Markdown
Member

This PR introduces the following modifications:

  • adds details in CONTRIBUTING
  • revamped README (adds table description, full workflow description, usage description and configuration steps)
  • passes the Sentry creds in docker compose
  • added column description for all schemas
  • renames SERVER_NAME into SENTRY_SERVER_NAME

Any feedback is welcome!

@frgfm frgfm added topic: docs Improvements or additions to documentation type: improvement New feature or request type: breaking change topic: docker labels Oct 16, 2022
@frgfm frgfm added this to the 0.2.0 milestone Oct 16, 2022
@frgfm
frgfm requested a review from a team October 16, 2022 22:12
@frgfm frgfm self-assigned this Oct 16, 2022
@codecov

codecov Bot commented Oct 16, 2022

Copy link
Copy Markdown

Codecov Report

Merging #227 (9fc50a0) into master (5df89ed) will increase coverage by 0.00%.
The diff coverage is 98.75%.

@@           Coverage Diff           @@
##           master     #227   +/-   ##
=======================================
  Coverage   94.08%   94.09%           
=======================================
  Files          47       47           
  Lines        1285     1286    +1     
=======================================
+ Hits         1209     1210    +1     
  Misses         76       76           
Flag Coverage Δ
unittests 94.09% <98.75%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/app/main.py 76.00% <0.00%> (ø)
src/app/api/schemas/accesses.py 100.00% <100.00%> (ø)
src/app/api/schemas/alerts.py 100.00% <100.00%> (ø)
src/app/api/schemas/base.py 100.00% <100.00%> (ø)
src/app/api/schemas/devices.py 100.00% <100.00%> (ø)
src/app/api/schemas/events.py 100.00% <100.00%> (ø)
src/app/api/schemas/groups.py 100.00% <100.00%> (ø)
src/app/api/schemas/installations.py 100.00% <100.00%> (ø)
src/app/api/schemas/login.py 100.00% <100.00%> (ø)
src/app/api/schemas/media.py 100.00% <100.00%> (ø)
... and 5 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@fe51 fe51 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi FG !

Thanks a lot for the PR, it makes this repo usage clearer ! few questions but not blocking :)

Comment thread CONTRIBUTING.md
make test
```

This will run the full suite of core API unittests. However, if you're trying to run some specific unittests, you can do as follows:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should specify that these tests only concern the api and not the client. The current wording suggests that the command will test everything, whereas there is a specific command for the client. Maybe specify the client test command (while specifying that the current test coverage is not complete yet) ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought "core API" was specific enough 😅

Comment thread README.md
With the previously described tables, here are all the steps to send a wildfire alert:
- Prerequisites (ask the instance administrator): register user
- Register a device: declare your device on the API, using your new user credentials.
- Create a media object & upload content: using the device credentials, save the picture metadata and upload the image content.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think it would be needed to explain that there is service to store images (s3 alike) and other tables are in an postgres table ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is explained in CONTRIBUTING (I think we should scare people only coming for usage / light development rather than "hardcore" developers)

Comment thread README.md
```

## Usage
### How is the database organized

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think an ER diagram would be needed ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not, but I would argue not in the README 😅 That will scare people haha

@frgfm
frgfm merged commit 7994513 into master Oct 17, 2022
@frgfm
frgfm deleted the api-documentation branch October 17, 2022 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: docker topic: docs Improvements or additions to documentation type: breaking change type: improvement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants