Cannot make it work with DEBUG=False on Heroku

[filipeximenes]

I'm trying to serve statics on heroku with DEBUG=False. When DEBUG is True everything works perfectly so it is when I run my application locally with Heroku's Foreman. Collectstatic runs with no problems in both ambients.
Forman works with the following setting:

STATIC_ROOT = root('staticfiles')
STATIC_URL = '/static/'

But i've tried setting it with:

STATIC_ROOT = 'staticfiles'
STATIC_URL = '/static/'

with no success.

My app is structured in the following way:

Procfile
requirements.txt
projetc/
   manage.py
   project/
   staticfiles/

I'm setting --pythonpath to the project folder in the procfile.

[kennethreitz]

Are you using the latest release?

[filipeximenes]

I'm using the one available on pip:

dj-static==0.0.5
static==0.4

[syphar]

@filipeximenes
silly question, but have you tried DEBUG=False locally with foreman?

[filipeximenes]

Yes.
When I have
STATIC_ROOT = root('staticfiles')
Foreman works on debug True and False

[filipeximenes]

Not sure if i made some mistake or just got confused, but Forman is working perfectly with:

STATIC_ROOT = 'staticfiles'
DEBUG = False

I still can't get Heroku to serve my staticfiles.

[filipeximenes]

Also, when I run collectstatic, files are being saved at the root directory (not the "django project root")

Procfile
requirements.txt
staticfiles/
projetc/
   manage.py
   project/

(this is the configuration Foreman works)

[filipeximenes]

I changed the whole project to a more traditional structure:

Procfile
requirements.txt
staticfiles/
manage.py
project/
apps/
   app1/
   app2/

Still getting the same result. It works with forman but not in heroku. I destroyed my previous application in heroku and started another with no success.
One thing to notice is tha heroku is not automatically running collectstatic as it is supposet to (https://devcenter.heroku.com/articles/django-assets)
Also, every time a run collectstatic it copies all the files again.

[syphar]

This does not sound like a problem with dj-static (or static), it seems more this is your app not fully working on heroku :)

When Heroku does not run collectstatic on push, the static files are missing.
When you run it with heroku run the files aren't collected and compiled into your slug (what is what you need)

[filipeximenes]

Well, I really don't know where is the problem. I just made it work putting collectstatic inside Procfile:
web: python project/manage.py collectstatic --noinput; gunicorn --pythonpath project project.wsgi
this will do for now.
Still curious to know what's the problem and if it's my mistake or heroku's.

[patrick91]

I've the same problem. Maybe there's something wrong with --pythonpath project? (I'm just guessing).

I've even tried to run collect static after a push but nothing changed, the file were copied but when I try to access a static file I get a 404 error.

@filipeximenes solution partially worked for me I can see my assets but admin assets are missing.

I'm going to create a ticket on heroku support site.

[idan]

Also running into this issue. Strange.

[patrick91]

FYI this is the reply I received from Heroku support

Patrick,
I believe most of your issues is due to your repository layout. The custom PYTHONPATH you've provided shouldn't be necessary.
We recommend developers place the directory that contains manage.py as the root of their repository. This makes things much easier.

[filipeximenes]

I have tried the "traditional" project layout with no success (see previous messages).
@patrick91 can you try this on your project and tell us if it solves the problem?

Also, just yesterday a friend of mine came to me (after finding this discussion) and told me he had the same problem, I've checked and he had manage.py in the root of his repository.

[patrick91]

@filipeximenes I'll do as soon as possible :)

[cmoad]

+1 We're seeing this only work with "DEBUG = True" as well.