I don't know if it's feasible but supporting dokku would definitely be a nice thing!
Can't we fork the 'Heroku' provider; change the default deploy strategy to git+ssh and remove the generic & API strategy?
I don't think so. The Heroku provider uses netrc for auth. Dokku OOTB needs an SSH key. https://github.com/travis-ci/dpl/blob/master/lib/dpl/provider/heroku/git.rb#L20-L24
Yeah, this is something I'm vested in - I'm torn about adding keys into a repo - a public one at that.
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
Thanks to this bot, I got curious and looked into this. A Dokku integration is definitely doable. It'd require the addition of a SSH key to one's project that Travis CI could use to push.
A plugin for Dokku https://github.com/cedricziel/dokku-deployment-keys makes that easy. I might look into this, if I get time.
Could you come up with something usable in the meantime @jalcine ?
Here is what I do currently (suppose the private key is base64 encoded in$SSH_PRIVATE_KEY_BASE64)
which ssh-agent || ( apt-get update -qy && apt-get install -y openssh-client )
eval $(ssh-agent -s)
ssh-add <(echo "$SSH_PRIVATE_KEY_BASE64" | base64 -d)
echo "Using key $(ssh-add -l)"
mkdir -p ~/.ssh
[[ -f /.dockerenv ]] && echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config # if running in docker we cannot check the hostkey
git push ssh://[email protected]:22/applicationname master
we're working on this, but still stuck on just getting an auto-deploy to dokku: https://github.com/travis-ci/travis-ci/issues/10174
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
Any update on this?
I want to push commits to GitHub's repo and if this was in master branch - please trigger deploy on dokku (like Heroku does with its GitHub integration). Couldn't find any nice solution without crutches
@ohld I don't think we received PR from the work @tansaku and @mattwr18 indicated in https://github.com/travis-ci/travis-ci/issues/10174. You can try copying what https://github.com/travis-ci/travis-ci/issues/10174#issuecomment-573733583 says, or work out a PR from it.
Most helpful comment
Thanks to this bot, I got curious and looked into this. A Dokku integration is definitely doable. It'd require the addition of a SSH key to one's project that Travis CI could use to push.
A plugin for Dokku https://github.com/cedricziel/dokku-deployment-keys makes that easy. I might look into this, if I get time.