-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Cloudrun not loading SpatiaLite module? #21
Comments
D'oh! This can be fixed by adding the Hey @simonw I'm closing this but think this is probably a documentation issue -- probably the flag should be added to cloudrun publication invocation here: https://github.com/simonw/datasette-cluster-map#installation ? I'd add a PR but am a lil iffy if I'm right. |
This is covered in the publish Cloud Run docs in the main Datasette documentation - since |
Ahhhhh! I think I was acting under the impression that spatialite was required for cluster mapping to work. So I installed it and stuff was breaking because I hadn't enabled it. But now that I look more carefully it doesn't seem to be required, I just wanted spatial queries to work. |
I've been unable to publish a cluster map to google cloudrun even though essentially the same command runs locally. Specifically, I'm getting "Error: It looks like you're trying to load a SpatiaLite database without first loading the SpatiaLite module."
Am trying to follow the cloudrun publish example here.
That example does not use a "--load-extension" argument, but maybe it is needed? The one thing I can think of is that somehow the location isn't being set correctly on cloudrun? A different example noted that it was running in a docker container locally--is it possible that using --install=datasette-cluster-map gets misconfigured if you're not in docker? I'm running on mac os x locally, I'm a bit unclear on how packaging works...
This is the publish command I'm using:
datasette publish cloudrun --install=datasette-cluster-map --metadata=metadata.json --template-dir=custom_templates nursing_home_compare/Nursing_Homes.db --service=nh
From the google cloud logs
This is the local log traceback:
The text was updated successfully, but these errors were encountered: