-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Support scripts.dokku. in app.json #1836
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should really be cleaned up imo. port and then ip? ew.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wut?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pre-deploy hook is:
plugn trigger pre-deploy $APP $IMAGE_TAGMaybe we should follow that and instead do:
plugn trigger post-deploy $APP $IMAGE_TAG $ipaddr $portOr similar? What uses the port/ipaddr from here that cannot retrieve it from some other helper?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see. This would break any post-deploy plugins that used those arguments. While I agree with you that this should probably happen at some point, I don't think it should go in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant post-deploy in my second example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I meant that too :)
|
What happens for |
|
Yeah the current implementation only supports buildpack apps anyway since we don't EDIT: if this is to only be supported in |
|
Tests are failing because CircleCi did not include their |
|
Yeah lets drop the dockerfile reference. |
|
Noooooo! 😜 This really doesn't need to wait for |
|
I'd like to leave features up for 0.5.0 to push people to upgrade :) |
|
Bah! Ok 😿 |
|
Is there a good reason why we shouldn't incentivize updates? |
|
Meh? |
c7a201e to
3596e42
Compare
|
Note, I don't mind doing it in 0.4.x if that's your wish. |
|
no. |
29182d9 to
bfa26fe
Compare
|
I've split out the commits that don't belong here into other PRs. Once those tests pass, I'll update this one. |
bfa26fe to
75e2272
Compare
|
I'm wondering if If an app.json postdeploy script makes changes to the app image, the app will never see those changes because our container is already running with the previous image layer. As far as I can tell, we have 2 options.
I'm leaning towards option 2. Thoughts? |
|
Option 2 |
75e2272 to
2a7e2f4
Compare
|
Assuming tests pass, I think this is good to go. |
|
This looks good to me for the 0.5.0 release. |
|
🎉 Awesome! @michaelshobbs Thanks for working on this ❤️ |
2a7e2f4 to
91a8a54
Compare
|
Don't know why help generation is failing very weird, as master passes... |
91a8a54 to
48f2dc0
Compare
|
Must have been something weird with your rebase. I rebased and forced-push. Tests pass now |
|
Merge when ready :) |
support scripts.dokku. in app.json
IMAGE_TAGpost-deployplugn trigger callcloses #1824