search

azavea / temperate

Climate app developed in partnership with ICLEI
Apache License 2.0
0 stars 0 forks source link

Add Django static assets to deployment #84

Closed CloudNiner closed 7 years ago

CloudNiner commented 7 years ago

Missing on staging:

screen shot 2017-10-04 at 10 26 25

We can probably deploy them in the same way as the API, to an S3 bucket, unless there's a more streamlined way used more recently elsewhere:

https://github.com/azavea/climate-change-api/blob/develop/scripts/cipublish#L48

https://github.com/azavea/climate-change-api/blob/develop/django/climate_change_api/climate_change_api/settings.py#L252

hectcastro commented 7 years ago

If this is all collectstatic stuff, then I think I'd want to trap this in the container image somehow vs. pushing things to S3. I think that the S3 publishing workflow makes certain deployment related processes harder than they need to be.

Part of an approach with dj-static exists in this PR for C4C.

CloudNiner commented 7 years ago

Nice. That seems like a sensible approach. 👍