This code:
> class Variables(View):
> def get(self, request):
> data = {}
> try:
> data["cloudsql"] = os.listdir('/cloudsql')
> except Exception as e:
> data["cloudsql"] = str(e)
> return JsonResponse(data)
>
>
Leads to the following output:
{"cloudsql": []}
>
>
I haven't tested the sample app, yet. But how can the application itself
affect the existence of the socket? Shouldn't it be always there?
On Tuesday, 16 October 2018 15:51:42 UTC+2, Attila-Mihaly Balazs wrote:
>
> Yes, I can confirm that I can deploy the app from the linked GitHub repo
> and it can establish a database connection fine (this is the view I'm
> testing with:
> https://github.com/cdman/google-appengine-django-postgres-test/blob/master/mysite/urls.py#L29
>
> - which does a "User.objects.count()").
>
> Also, I don't think the region (europe-west) has anything to do with it
> since I deployed / tested it myself in the europe-west region.
>
> Perhaps you could try printing out (ie. logging or returning it in a view)
> the values from os.listdir('/cloudsql') *in production* to see if your
> postgres instance shows up there.
>
> Attila
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/fc3e84bc-cf9f-4980-aaf7-5da70596e187%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
