Skip to content
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.

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

Documentation: use consistent Astarte URL notation #738

Open
Annopaolo opened this issue Nov 10, 2022 · 0 comments · May be fixed by #836
Open

Documentation: use consistent Astarte URL notation #738

Annopaolo opened this issue Nov 10, 2022 · 0 comments · May be fixed by #836
Assignees
Labels
documentation This issue or pull request is about documentation good first issue Good for newcomers minor This issue causes only minor annoyance to the user
Milestone

Comments

@Annopaolo
Copy link
Collaborator

The Astarte documentation currently uses two notations for the base Astarte API URL:

  • <astarte base API URL> (e.g.here)
  • api.<your astarte domain>(e.g. here)

Commit to a single, consistent notation across all documentation.

@Annopaolo Annopaolo added good first issue Good for newcomers documentation This issue or pull request is about documentation minor This issue causes only minor annoyance to the user labels Nov 10, 2022
@rbino rbino added this to the v1.2 milestone Jan 17, 2023
@bettio bettio modified the milestones: v1.2, v1.3 Jun 19, 2023
rifasofic added a commit to rifasofic/astarte that referenced this issue Aug 15, 2023
Change notation for the base Astarte API URL instead api.<your astarte domain> in <astarte base AP
I URL>

Closes astarte-platform#738

Signed-off-by: rifa sofic <rifa.sofic@secomind.com>
@rifasofic rifasofic linked a pull request Aug 15, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This issue or pull request is about documentation good first issue Good for newcomers minor This issue causes only minor annoyance to the user
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

5 participants