Closed AubreyHewes closed 5 years ago
ah ok, soz forget about it.. the plugin install always clones.. so there is no support for commitish.. so I will have to locally clone and then checkout the required tag
followup; the current version seems to work in the old dokku env ;-)
It unfortunately did do the following:
Status: Downloaded newer image for dokku/ambassador:0.2.0
Status: Downloaded newer image for dokku/wait:0.3.0
Status: Downloaded newer image for dokku/s3backup:0.9.4
Status: Downloaded newer image for busybox:1.30.1-uclibc
So as no way back will have to see if that has any impact.. a way to force the global update ;-)
We have an older dokku
0.8.2
in production and need to add this plugin..and we can not (yet) update the dokku...Is it safe to just install the latest? as per docs (even though the current minimum dokku, 12, is above our current)?
I tried installing a compatible release (a la package mgmt) but it fails as the
plugin:install
fails ...this seems to be a plugin installer problem that the plugin installer does not support release tags (Cloning into 'mongo.git#1.4.10'...fatal: https://github.com/dokku/dokku-mongo.git#1.4.10/info/refs not valid)? This is probably not an issue for this plugin but installing specific plugin releases in general?
@josegonzalez ?
Is the work around to just clone the release directly to the dooku installed plugins ?