-
Notifications
You must be signed in to change notification settings - Fork 5
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
Deploy dev veda backend with openveda.cloud #291
Comments
I created a certificate for the new domain |
For anyone following along the issue, the following links are available: I also will update the dev secret to contain the new values for the following variables, pending some confirmation that that's okay to do:
I'm currently working on migrating to Stadia maps for https://dev.openveda.cloud/api/stac/index.html to be functional |
I updated my comment and reverted the changes to the dev secret until I get confirmation from the team that it's okay to update it 😅 |
## Description - This PR migrates Stamen Map references to use Stadia Maps (full migration notes [here](https://docs.stadiamaps.com/guides/migrating-from-stamen-map-tiles/)) - The migration is setup with my DevSeed email and to work with `*.delta-backend.com` domain ## Related Issues #291 ## Changes Made - updates `stac-viewer.html` references from stamen maps to stadia maps ## Testing Done [- Page now shows map](https://dev.delta-backend.com/api/stac/index.html)
The PR attached to this issue has been merged 🎉 Thanks for the review, @smohiudd! Once we can successfully get dev deployed again, I will udpate the Stadia Maps account with the new domain (openveda.cloud) |
Writing here to note that I updated the Stadia Map account to use the new domain (openveda.cloud). I also opened a PR to address an issue I found in the STAC viewer #311. |
### Issue #291 ### What? - Updated the endpoint value for the STAC viewer in order to properly render the collections on the webpage. - Added a PR template so that all new PRs will have a template for reference ### Why? - The endpoint is https://dev.openveda.cloud/collections which is incorrect which causes the collections filter to fail in the STAC viewer. https://github.com/NASA-IMPACT/veda-backend/assets/12633533/b272fb4c-23a9-41c2-8ce8-925c6760231a ### Testing? - I didn't locally deploy or anything but here is [the working collections link](https://dev.openveda.cloud/api/stac/collections) ### Notes - I think we could technically also update https://github.com/NASA-IMPACT/veda-backend/blob/develop/stac_api/runtime/src/app.py#L79 to be: ```{"request": request, "endpoint": str(request.url).replace("/index.html", "/api/stac")},``` if that's preferred
What
Before taking on this Cloudfront ticket, should test out using the new openveda.cloud domain on a the
dev
instance. This will help formulate a pattern that can be used for the production deployment.As part of this ticket, explore (possibly implement) the option to have no subdomain in veda-backend routes construct. Currently this configuration is not supported. Ultimately this config option will support the production instance which may have a urls pattern like this:
AC
dev
instance is deployed with openveda.cloud domain (i.e. dev.openveda.cloud)The text was updated successfully, but these errors were encountered: