Skip to content
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

Don't hard-code runtime application path #62

Merged

Conversation

benlangfeld
Copy link
Contributor

It is not guaranteed that the app is installed to /app. Users of buildpacks other than Heroku require applications to be stored at other paths, such as pkgr which uses /opt/${APP_NAME}. Furthermore, the source may not be located at /app at compile time, since not every buildpack executor uses a layered filesystem, and so must resort to using a sandbox build directory (some call this the good old days).

This seems to have been broken by f651aac.

See crohr/pkgr#93 for the source of this.

@benlangfeld benlangfeld changed the title Don't hard-code runtime application path [WIP] Don't hard-code runtime application path Jan 18, 2016
@benlangfeld benlangfeld force-pushed the feature/flexible-directory-structure branch 5 times, most recently from 939a2b0 to e8d80fe Compare January 18, 2016 21:13
It is not guaranteed that the app is installed to /app. Users of buildpacks other than Heroku require applications to be stored at other paths, such as [pkgr](http://github.com/crohr/pkgr) which uses /opt/${APP_NAME}. Furthermore, the source may not be located at /app at compile time, since not every buildpack executor uses a layered filesystem, and so must resort to using a sandbox build directory (some call this the good old days).

See crohr/pkgr#93 for the source of this.
benlangfeld added a commit to benlangfeld/QueueFlex that referenced this pull request Jan 18, 2016
@benlangfeld benlangfeld changed the title [WIP] Don't hard-code runtime application path Don't hard-code runtime application path Jan 18, 2016
@HashNuke
Copy link
Owner

@benlangfeld I'll try this out this weekend and merge it if alright.
\cc: @ericmj

@benlangfeld
Copy link
Contributor Author

@HashNuke Deployments to both Heroku and pkgr work just great with this change. Thanks for your attention on this. Note that I also have a relevant more general issue open.

@benlangfeld benlangfeld force-pushed the feature/flexible-directory-structure branch from 2986ed6 to e8d80fe Compare January 19, 2016 12:31
@ericmj
Copy link
Collaborator

ericmj commented Mar 18, 2016

:shipit:

@benlangfeld
Copy link
Contributor Author

@HashNuke Any chance of a merge here?

@HashNuke HashNuke merged commit ef21315 into HashNuke:master Apr 4, 2016
@HashNuke
Copy link
Owner

HashNuke commented Apr 4, 2016

@benlangfeld Sorry about the delay. Merged. Thank you very much ~!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants