Skip to content

docs: fix spliced sentence in changelog known gaps #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nahuel007ng wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: fix spliced sentence in changelog known gaps #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ Why: a scrape used to tie up one of only two gunicorn workers for up to two minu

### Deploy checklist

1. Deploy the backend. new indexes by itself.
1. Deploy the backend. On startup it creates `scrape_jobs` and the new indexes by itself.
2. Optional, once: `alembic stamp 003_scrape_jobs` against prod so Alembic history matches.
3. Deploy the web app and publish the new APK straight after.
4. For Play Store builds, create `mobile/android/key.properties` first.
Expand All @@ -72,5 +72,5 @@ Why: a scrape used to tie up one of only two gunicorn workers for up to two minu
### Known gaps

- The Supabase SDK still loads at web boot (could be lazy).
- The lab-report "drop it here" box loOn startup it creates `scrape_jobs` and theoks like a drop target but only supports clicking to pick a file.
- The lab-report "drop it here" box looks like a drop target but only supports clicking to pick a file.
- CI builds the APK with only `API_BASE_URL` and `MEDSCAN_API_KEY`. That's fine, because the app fetches Supabase config from the backend.