-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Migrate to Cloud Run #20
Comments
I'm going to switch from Circle CI to GitHub Actions at the same time. Will base this on https://github.com/simonw/covid-19-datasette/blob/master/.github/workflows/scheduled.yml |
I added the |
Here's the Circle CI script I'm replacing: https://github.com/simonw/museums/blob/c0ac71b58b1c958233cfddada8ce6b01b2bfdcb2/.circleci/config.yml |
OK, site is deployed at https://niche-museums-j7hipcg4aq-uc.a.run.app/ - but it's showing a 500 error on the index page right now: The data is there: https://niche-museums-j7hipcg4aq-uc.a.run.app/browse And it looks like it has the correct list of plugins: https://niche-museums-j7hipcg4aq-uc.a.run.app/-/plugins |
I get the same error in my local development environment. Here's the traceback:
|
The problem occurs here on the index page: Lines 76 to 79 in 6422909
The Lines 34 to 43 in 7520afa
|
It looks like the bug originates here: Lines 7 to 10 in 7520afa
|
The working version at https://www.niche-museums.com/-/versions reports that the Datasette version is Line 36 in c0ac71b
Looks like I started deploying |
My last successful deploy of the old site was c0ac71b on 2nd Feb. At the time Datasette master would have been https://github.com/simonw/datasette/tree/286ed286b68793532c2a38436a08343b45cfbc91 |
Deploying today's master ( https://github.com/simonw/datasette/tree/e0e7a0facfc935a835cd73c720bc46661462f0b1 ) resulted in the same 500 error. I'm going to see if I'll test that locally first with this:
|
That fixes it! I'll use this as a temporary fix here, then investigate the underlying Datasette bug. |
Next step: map www.niche-museums.com domain to the new Cloud Run instance. |
For verification I'm following the same steps as here: simonw/datasette#705 (comment) DNS is hosted by Zeit so I need to run:
|
I'm going to try setting the CNAME on both Zeit DNS AND Google DNS, to hopefully workaround the potential 48 hour delay. |
Ran this:
|
I'm going to make a change that's only visible in the Cloud Run instance so I can tell in my browser if I am seeing the site hosted on Zeit Now or on Cloud Run. |
I made the same DNS change on Google Domains: https://domains.google.com/m/registrar/niche-museums.com/dns |
Looks like I've broken https://www.niche-museums.com/ - it's returning a TLS error at the moment. |
https://niche-museums-j7hipcg4aq-uc.a.run.app/-/metadata now shows the As soon as https://www.niche-museums.com/-/metadata shows the same thing I can close this ticket. |
So it's working! Just started working on my laptop too. |
https://niche-museums.com/ doesn't work. It should redirect to the correct site. I'm going to try to set that up using Google Domains, in 24 hours time once everything has settled a bit: https://domains.google.com/m/registrar/niche-museums.com/dns Instructions here: https://www.tachyonstemplates.com/2018/google-domains-forward-root/ |
Actually I'm going to try pointing https://niche-museums.com/ to the same Cloud Run app, then add some Datasette custom ASGI middleware to handle the no-www to www redirect. |
OK, DNS now looks like this: Already seeing them on my laptop using
|
Still not working, I'll give it a few minutes for certificates to settle down etc. |
OK https://niche-museums.com/? is working for me now but not redirecting to www. |
Moving that to a separate issue: #21 |
Zeit v1 is being turned off in August.
The text was updated successfully, but these errors were encountered: