-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't find public directory. #2
Comments
Short answer: no. Long answer: I had a terrible time trying to get all the pathnames to come Unfortunately I don't have time to dive back into this now. On Fri, Nov 16, 2012 at 12:16 PM, Quinn Jarrell [email protected]:
|
Alright, I'll take a deeper look this week and see if I can fix it. Thanks for your response. |
Why the error happens is obvious: the application tries to access directory the "./public/" - the one present in the git repository. But the buildpack doesn't copy the source code to BUILD_DIR. It only places CCL binary and the application image file there. So the "./public/" directory is absent at run-time. |
Found the fix. Changed the "./public/" to "/app/public". Found this solution in this application: https://github.com/jsmpereira/heroku-cl-example. |
Discuessed on #heroku at freenode.net with @jsmpereira and @yfeldblum. We think that referring the /app/ directly is not 100% reliable, as heroku may change it in the future. Expecting the git repository content to be available in the current directory is more reliable, according to @yfeldblum. But I've added logging to the initialization of the lips application. |
The public directory for loading images/assets seems not to be working and is crashing the app when deployed on heroku.
The error reported in the logs is: Error: File "./public/" does not exist. Any ideas on how to solve this? For now I don't need images so I've commented out the publish-directory call in initialize-application.
The text was updated successfully, but these errors were encountered: