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

latest.datasette.io is no longer updating #705

Closed
simonw opened this issue Mar 22, 2020 · 15 comments
Closed

latest.datasette.io is no longer updating #705

simonw opened this issue Mar 22, 2020 · 15 comments
Labels

Comments

@simonw
Copy link
Owner

@simonw simonw commented Mar 22, 2020

@simonw simonw added bug ci labels Mar 22, 2020
@simonw simonw added this to the Datasette 0.39 milestone Mar 24, 2020
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 24, 2020

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.

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 24, 2020

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 latest.datasette.io working again, using Cloud Run.

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

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:

datasette publish cloudrun fixtures.db \
    -m fixtures.json \
    --branch=7656fd64d8b6a32ebc34d89c1b8711cc5ea240f7 \
    --version-note=7656fd64d8b6a32ebc34d89c1b8711cc5ea240f7 \
    --extra-options="--config template_debug:1" \
    --service=datasette-latest
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

I need to verify datasette.io with Google. These instructions look good: https://cloud.google.com/endpoints/docs/openapi/verify-domain-name

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

Webmaster_Central

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

I tried running this:

$ now dns add datasette.io '@' TXT google-site-verification=wHw15S1fkNOMzk42PEVK6XLnSG9qEfyq6paO8_G4IVU
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

That worked:
Webmaster_Central

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

... and set up the CNAME record:

$ now dns add datasette.io latest CNAME ghs.googlehosted.com.

Got an error:

> Error!  A conflicting record exists "rec_e4c36ae94cf0a2b7b1781329".
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

Removed the conflicting record with:

 $ now dns rm rec_e4c36ae94cf0a2b7b1781329

Then:

$ now dns add datasette.io latest CNAME ghs.googlehosted.com.
> Success! DNS record for domain datasette.io (rec_5b8855344da0be1861c4d55b) created under simonw [10s]
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

Could take a while for the certificate to be issued:

Domain_mappings_–_Cloud_Run_–_datasette_–_Google_Cloud_Platform

simonw added a commit that referenced this issue Mar 25, 2020
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

Now following steps in https://simonwillison.net/2020/Jan/21/github-actions-cloud-run/ - I've added the GCP_SA_EMAIL and GCP_SA_KEY secrets to this repository: https://github.com/simonw/datasette/settings/secrets

@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

https://latest.datasette.io/-/versions is now serving from Cloud Run.

simonw added a commit that referenced this issue Mar 25, 2020
@simonw

This comment has been minimized.

Copy link
Owner Author

@simonw simonw commented Mar 25, 2020

It worked! After that push https://latest.datasette.io/-/versions updated to show 90015b26895fd2bd29676bc375f096102b0587ed as the version note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.