-
-
Notifications
You must be signed in to change notification settings - Fork 694
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
latest.datasette.io is no longer updating #705
Comments
I can switch over to deploying that using Cloud Run. Unfortunately if I move away from Zeit Now v1 (since it's no longer supported and might stop working) I don't think I'll be able to deploy a permanent URL for every commit hash that I push any more, which is a real shame. |
I'd like to still provide https://v0-35.datasette.io/ URLs for every named release, but I'm not sure how to best automate the provisioning of those subdomains. For the moment I'm going to focus on getting |
I'm going to do this using GitHub Actions and the recipe from https://simonwillison.net/2020/Jan/21/github-actions-cloud-run/ First step: deploying manually using this:
|
That's live at https://datasette-latest-j7hipcg4aq-uc.a.run.app/ |
I need to verify |
I tried running this:
|
Now add the service mapping in Cloud Run: https://console.cloud.google.com/run/domains?project=datasette-222320 |
... and set up the CNAME record:
Got an error:
|
Removed the conflicting record with:
Then:
|
Now following steps in https://simonwillison.net/2020/Jan/21/github-actions-cloud-run/ - I've added the |
https://latest.datasette.io/-/versions is now serving from Cloud Run. |
It worked! After that push https://latest.datasette.io/-/versions updated to show |
https://latest.datasette.io/-/versions is stuck on 0.35.
The text was updated successfully, but these errors were encountered: