-
Notifications
You must be signed in to change notification settings - Fork 152
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
Only copy from app import path to app path when building #467
Only copy from app import path to app path when building #467
Conversation
Assigning to @michaelshobbs for review :) |
@josegonzalez this should be tested with dokku before upgrading the default version |
@josegonzalez is there anything I can do to help with the dokku testing? |
@mlandauer thanks for PRing this – I'd love to see this pushed through! |
Testing in dokku would require building the herokuish image and pushing a few apps with it. |
I am pretty sure this will work based on a single test of a python app, but will try and get this more stress-tested soon. |
Any chance of this to be released in the near future? I encountered the same problem and it would be great to have this merged. This change will certainly come in handy when I want to chain multiple herokuish commands. |
febc15e
to
7a1c10f
Compare
This worked locally with Dokku like so:
|
- #1093 @dependabot: chore(deps): bump actions/download-artifact from 3 to 4 - #1173 @josegonzalez: Use find to identify only files not already owned by user - #1174 @josegonzalez: Add linting to CI - #1175 @josegonzalez: Ensure all file permissions are set to specified unprivileged user - #467 @mlandauer: Only copy from app import path to app path when building
Apologies for getting to this so late, just didn't have the bandwidth/mental energy to work on it. |
This PR fixes #402 (slug generate gzips from /tmp/app, when it should gzip from /app) and #321 (Cannot execute any Procfile commands) and fixed the issue mentioned in the blog post "Running Herokuish apps in Docker".
Currently every time herokuish is run the app import path (e.g. /tmp/app) is copied over to the app path (e.g. /app) if the import path exists and has files in it.
This PR changes this so that the copy from the import path to the app path is only done on running
herokuish buildpack build
orherokuish buildpack test
as suggested by @matthewmueller in #402.This means that you can now run
buildpack build
immediately followed byprocfile start
within the same container and things will work.I can see at least two different ways that people were working around this issue before:
buildpack build
and then running a container from that image which doesn't have a volume mounted at /tmp/app and so the contents of /app is not overwritten.This PR should not break those workarounds.