Search
4 results for “drybjed”
-
RE: https://fosstodon.org/@debops/117292864548178245
And to add a bit of context - this was possible from the start of the project in 2013. During development I had to reinstall a Debian VM many times to test various things, so a proper netboot setup was an early priority. But the problem with previous iteration was that I had to manually update the tarball checksums on each Debian point release.
Finally I've found some time to redesign the Debian Installer side of the setup, and created a whole new role for it, so that users can configure it separately if they want to, or incorporate it in their own solutions.
I also backported the new role to the stable branches of DebOps (which I usually don't do). That way, older releases can benefit from the automated updates without the need to switch to a newer version.
With this change, I plan to release DebOps v3.4.x stable release in a few days, after merging a couple more bugfixes from the pull requests.
-
RE: https://fosstodon.org/@debops/117292864548178245
And to add a bit of context - this was possible from the start of the project in 2013. During development I had to reinstall a Debian VM many times to test various things, so a proper netboot setup was an early priority. But the problem with previous iteration was that I had to manually update the tarball checksums on each Debian point release.
Finally I've found some time to redesign the Debian Installer side of the setup, and created a whole new role for it, so that users can configure it separately if they want to, or incorporate it in their own solutions.
I also backported the new role to the stable branches of DebOps (which I usually don't do). That way, older releases can benefit from the automated updates without the need to switch to a newer version.
With this change, I plan to release DebOps v3.4.x stable release in a few days, after merging a couple more bugfixes from the pull requests.
-
RE: https://fosstodon.org/@debops/117292864548178245
And to add a bit of context - this was possible from the start of the project in 2013. During development I had to reinstall a Debian VM many times to test various things, so a proper netboot setup was an early priority. But the problem with previous iteration was that I had to manually update the tarball checksums on each Debian point release.
Finally I've found some time to redesign the Debian Installer side of the setup, and created a whole new role for it, so that users can configure it separately if they want to, or incorporate it in their own solutions.
I also backported the new role to the stable branches of DebOps (which I usually don't do). That way, older releases can benefit from the automated updates without the need to switch to a newer version.
With this change, I plan to release DebOps v3.4.x stable release in a few days, after merging a couple more bugfixes from the pull requests.
-
RE: https://fosstodon.org/@debops/117292864548178245
And to add a bit of context - this was possible from the start of the project in 2013. During development I had to reinstall a Debian VM many times to test various things, so a proper netboot setup was an early priority. But the problem with previous iteration was that I had to manually update the tarball checksums on each Debian point release.
Finally I've found some time to redesign the Debian Installer side of the setup, and created a whole new role for it, so that users can configure it separately if they want to, or incorporate it in their own solutions.
I also backported the new role to the stable branches of DebOps (which I usually don't do). That way, older releases can benefit from the automated updates without the need to switch to a newer version.
With this change, I plan to release DebOps v3.4.x stable release in a few days, after merging a couple more bugfixes from the pull requests.