Cloud-run Dockerfile installs Django 3, errors about django-collaborative

[brandonrobertz]

Ah, thank you. That's was an oversight. I moved the cloud run link to clone with master branch, as intended.

[chriszs]

Great!

The key changes in the Dockerfile were pegging the Dockerfile base to 3.7, the aforementioned branch switch and modifying the relative paths for copying the start scripts. Not sure whether that last one is required in cloud-run, but we needed it in our build.

[brandonrobertz]

The cloud-run branch has gone stale (I forgot it was there). This problem is fixed in the master branch of Collaborate a while ago, along with a bunch of other issues.

I'm going to look at merging cloud-run and master, but don't want to break people so I'm going to do some testing first.

[brandonrobertz]

Can I ask if there's a reason you're using the cloud-run branch and not master? The deploy/google-cloud/Dockerfile exists in master so I'm curious what happened there.

[chriszs]

I’m using master. The Dockerfile in master clones the cloud-run branch.

[brandonrobertz]

Just so you know, I found a few issues with the cloud run environment/Dockerfile combination and I'm working through them in my spare time. If you're trying to get something running ASAP, I'd recommend using Heroku in the meantime.

[chriszs]

Hey there, we worked around those issues in a fork, as well adding a build file for our CI and a Helm deployment for Kubernetes. It's currently running on our cluster. Would offer to PR, but some of our changes may be specific to us.

[chriszs]

(We did use Heroku briefly for test purposes. It worked fine there!)

[brandonrobertz]

Awesome! I'm going to dedicate some time to this later this week and will go through your fork, seeing what the best path to unifying them may be. Thanks for your patience with this.