Simplify local development setup#10
Conversation
- Collapse to a single .env (cp .env.example .env); remove make dev-env - Ship working local defaults in .env.example: admin login, unverified email login, certificates disabled, so a fresh copy boots with no SMTP/OAuth/CA setup - Remove the dev Docker image and atom-dev service; keep one release image and fold the dev-only env knobs into the atom service - Unify the Cargo and Compose flows on one Postgres volume and port 8080 - Add `make db` (Postgres only) and `make dev` (Postgres + cargo run + UI) - Rename ATOM_DEV_ALLOW_UNVERIFIED_EMAIL_LOGIN to ATOM_ALLOW_UNVERIFIED_EMAIL_LOGIN - Fix the admin login identifier in docs (admin, not atom-admin) - Document the local run flows in README and quickstart
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
atom-docs | 1a01865 | Commit Preview URL Branch Preview URL |
Jun 15 2026, 12:47 PM |
Signed-off-by: dusan <borovcanindusan1@gmail.com>
|
@codex Review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 02d8b67ddc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| true, | ||
| ), | ||
| dev_allow_unverified_email_login: env_bool("ATOM_DEV_ALLOW_UNVERIFIED_EMAIL_LOGIN"), | ||
| dev_allow_unverified_email_login: env_bool("ATOM_ALLOW_UNVERIFIED_EMAIL_LOGIN"), |
There was a problem hiding this comment.
For deployments or local env files that already set the previously documented ATOM_DEV_ALLOW_UNVERIFIED_EMAIL_LOGIN=true, this rename silently falls back to false, so no-SMTP dev signup/login flows start requiring email verification after upgrade. Since the surrounding config already keeps legacy aliases for renamed flags, this should read the old variable as a fallback when ATOM_ALLOW_UNVERIFIED_EMAIL_LOGIN is unset.
Useful? React with 👍 / 👎.
Signed-off-by: dusan <borovcanindusan1@gmail.com>
Signed-off-by: dusan <borovcanindusan1@gmail.com>
2 participants
make db(Postgres only) andmake dev(Postgres + cargo run + UI)What type of PR is this?
This is an enhancement.
What does this do?
This simplifies running Atom locally.
Which issue(s) does this PR fix/relate to?
There is no such issue.
Have you included tests for your changes?
N/A
But I did test locally.
Did you document any new/modified features?
Yes.
Notes
N/A