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

switching default in template.env back to localhost:8080 #53

Open
4 tasks
surchs opened this issue May 7, 2024 · 1 comment
Open
4 tasks

switching default in template.env back to localhost:8080 #53

surchs opened this issue May 7, 2024 · 1 comment
Labels
documentation Changes only affect the documentation someday Not a priority right now, but we want to keep this around to think or discuss more.

Comments

@surchs
Copy link
Contributor

surchs commented May 7, 2024

to make first test deploy quick

Note that the docs will also need to be updated

TODO

  • change default to localhost:8080
  • add in the getting started docs that changing the value is optional for local trial deployment but required for prod deployment
  • add a big red warning box to restate the same in the getting started section (repetition of the above, implementer decides)
  • in the "configure a node" section, have a very prominent explanation on how to change the NB_API_QUERY_URL for common prod deployment
@surchs surchs changed the title switching default in template.env back to localhost:800 switching default in template.env back to localhost:8080 May 8, 2024
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jul 23, 2024
@alyssadai alyssadai added the flag:schedule Flag issue that should go on the roadmap or backlog. label Aug 15, 2024
@github-actions github-actions bot removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Aug 15, 2024
@surchs surchs added documentation Changes only affect the documentation and removed flag:schedule Flag issue that should go on the roadmap or backlog. labels Aug 16, 2024
@surchs surchs added the someday Not a priority right now, but we want to keep this around to think or discuss more. label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Changes only affect the documentation someday Not a priority right now, but we want to keep this around to think or discuss more.
Projects
Status: No status
Development

No branches or pull requests

2 participants