5c1a1baf08
The previous tar support lacked the ability to track changes between tarball deploys. Critically, it also failed to be handled correctly when there was _also_ a git deployment done on the app, resulting in odd deployment states depending on the angles of the moon and the sun in the sky. Rather than try to "fix" this through some hokey mechanism, importing the tar file contents into the git repository is preferred, as then the user can refer to the repository for commit history. Additionally, we add support for non-tar files (tar.gz and zip), enabling deployments from systems that do not create tar files, such as Github (their tarball url is a tar.gz file). Finally, this deprecates the tar plugin, and sets it to be removed in the next minor release (in addition to the tags plugin). Closes #3458 Closes #4207
1.3 KiB
1.3 KiB
0.23.0 Migration Guide
Changes
- The commands
proxy:enable,proxy:disableandproxy:build-confignow support the--allflag in addition to general parallelism. - The
builder-cnbplugin has been renamedbuilder-pack, and all related plugin triggers have had the suffix-cnbchanged to-pack.
Deprecations
- The 1.0.0 release of Dokku will no longer select buildpack builders over dockerfile builders if both builders match. Instead, Dokku will choose the first builder that responds to the
builder-detecttrigger. Users that wish to use a specific builder may set a builder using thebuilder:setcommand, which will force Dokku to use the specified builder regardless of what might be auto-detected. - The
tagsplugin is deprecated in favor of thegit:from-imagecommand. It will be removed in the next minor release, and is considered unmaintained. Users are highly encouraged to switch their workflows togit:from-image. - The
tarplugin is deprecated in favor of thegit:from-archivecommand. It will be removed in the next minor release, and is considered unmaintained. Users are highly encouraged to switch their workflows togit:from-archive.