Releases: linuxserver/docker-fleet
Releases · linuxserver/docker-fleet
2.0.1-ls38
LinuxServer Changes:
Updated to keep in line with v2.0.0 branch of Fleet
fleet Changes:
Re-added legacy API
- In my infinite wisdom I forgot to implement the old API for public consumption which returns all shown repositories.
2.0.0-ls38
LinuxServer Changes:
Updated to keep in line with v2.0.0 branch of Fleet
fleet Changes:
v2.0.0 Rewrite
This is the first major release update which is effectively a rewrite of the original Fleet code.
(Some of the) Changes
- An asynchronous queuing system is in place which accepts different kinds of jobs. Currently the only implemented job is to synchronise known images.
- A scheduling system has been implemented which runs specific update tasks periodically to ensure the images are correct in relation to DockerHub.
- DockerHub authentication has been entirely removed. You can now add whatever repositories you want.
- Much more granular management of repositories and images.
- Huge increase in metadata stored per image, including: logo, URLs, Docker properties.
- Multiple named branches (not just
master
) can be tracked per image. - User management has been added.
- The entire UI has been overhauled using a new CSS framework: Bulma.
- Container information and run command snippets are now included per image.
1.4.4-ls36
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls35
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls34
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls33
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls32
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls31
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls30
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.
1.4.4-ls29
LinuxServer Changes:
Rebasing to alpine 3.11.
fleet Changes:
- Protect against potential empty API responses from DockerHub causing an enmasse deletion of repositories. This seems to occur sporadically but causes Fleet to delete everything it has stored.