NOISSUE - Add getting started with Atom blog#159
Open
ianmuchyri wants to merge 10 commits into
Open
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
absmach-website | 0aee348 | Commit Preview URL Branch Preview URL |
Jun 17 2026, 02:53 PM |
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
ianmuchyri
force-pushed
the
atom-tutorial
branch
from
54d5d59 to
2bc5c6f
Compare
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
dborovcanin
requested changes
Jun 15, 2026
dborovcanin
left a comment
dborovcanin
left a comment
Contributor
There was a problem hiding this comment.
We are missing instruction on ADMIN_SECRET - so if I blindly follow commands, I get:
❯ docker compose up postgres -d
docker compose --profile atom-ui up -d --build
error while interpolating services.atom.environment.ADMIN_SECRET: required variable ADMIN_SECRET is missing a value: set ADMIN_SECRET
error while interpolating services.atom.environment.ADMIN_SECRET: required variable ADMIN_SECRET is missing a value: set ADMIN_SECRET
This architecture block should have a separate section or be a part of the intro.
Replace all dark-theme screenshots with light-theme versions and rename them by dropping the -light suffix. Remove old screenshots from the previous tutorial iteration. Replace em dashes throughout the prose with colons, semicolons, parentheses, or sentence breaks.
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
dborovcanin
requested changes
Jun 17, 2026
dborovcanin
left a comment
dborovcanin
left a comment
Contributor
There was a problem hiding this comment.
Screenshots are still too small in UI:
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
dborovcanin
reviewed
Jun 18, 2026
|
|
||
| 4. **Postgres connection refused on startup.** The database container needs a moment to fully initialize before accepting connections. If you see this, wait 15–20 seconds after starting and then check again. | ||
|
|
||
| 5. **Authorization check returns `"unknown action 'read'"`.** In Atom v0.1.0, the `read` action is only registered for built-in resource kinds (`channel`, `rule`, `report`, `alarm`). Use `kind: "channel"` for your test resource, or add the appropriate row to `action_applicability` if you're working with a custom kind. |
Contributor
There was a problem hiding this comment.
This look a lot like Magistrala-specific setup. Atom should not come with these out of box, but it should be provisioned on bootstrapping.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What does this do?
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Did you document any new/modified features?
Notes