#django-storages

/

      • maikhoepfel joined the channel
      • maikhoepfel
        Hi richleland
      • richleland
        heya
      • did my reply make sense?
      • maikhoepfel
        Yes, it does make sense. The problem is that Heroku's buildpack only runs collectstatic; afaik there's no easy way to change that command
      • Hence I suggest to call the command the same, but introduce a setting (which defaults to False) to enable the modified behaviour
      • I would add documentation for that in my pull requests
      • richleland
        oh you can disable collectstatic w/heroku and call another command I believe
      • one sec...
      • and then you could run a command manually
      • heorku run "command"
      • not sure if you can automate that "command"... hmm
      • maikhoepfel
        I don't think you can, without using a custom buildpack
      • If I'd introduce a setting and have it default to False, people can't really confuse it. I think it's fair enough for django-storages to override the collectstatic command. South does the same with e.g. syncdb
      • Or django-nose with the test command.
      • richleland
        that's true
      • good call - so basically like COLLECTSTATIC_HASH = True or somehting along those lines
      • maikhoepfel
        Exactly.
      • richleland
        and if not hash, just use vanilla collectstatic
      • ok cool - sounds sane
      • maikhoepfel
        Cool. I'll prep a pull request today or sometime next week then for you to have a look
      • Will run it by my boss to see if I can do it on company time ;)
      • richleland
        thanks a ton
      • I'm sure lots of folks will find this helpful
      • maikhoepfel
        No worries, thanks for a great project. I ran into this myself, and at work
      • Cheers. You'll hear from me
      • I just wrote to Olof, the author of fasts3collectstatic. I'll leave him time to reply and will prep the PR next week
      • maikhoepfel has quit