Skip to content

Releases: bravetools/bravetools

2.10

12 Mar 14:21
b9508d8
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.00...2.10

2.00

24 Jan 16:15
bac62c8
Compare
Choose a tag to compare

What's Changed

Read more

1.56

29 Jun 16:11
Compare
Choose a tag to compare

What's Changed

  • Pretty print by @idroz in #31
  • test dependencies before installation by @deknos in #33
  • Resource check refactoring by @adrozdovbering in #34
  • Bump kramdown from 2.3.0 to 2.3.1 in /docs by @dependabot in #40
  • address #35 by @idroz in #37
  • Issue 39 by @idroz in #42
  • issue-44 by @idroz in #45
  • address #49 by @idroz in #50
  • Update docs by rerunning doc generation tool to match current CLI messages by @Szubie in #53
  • Fix docs to refer to "local" images rather than "private" images by @Szubie in #55
  • Multi user init by @idroz in #58
  • Rename function BuildUnit to BuildImage by @Szubie in #56
  • Spinner stdout redirect by @idroz in #52
  • Multi user fixes by @idroz in #59
  • Unit db to init by @idroz in #61
  • Clean init by @idroz in #62
  • fix confusion with delete alias vs fingerprint by @idroz in #64
  • Brave deploy cli priority by @idroz in #66
  • Empty sources support by @idroz in #69
  • fix for apt by @idroz in #70
  • Return image fingerprint when building from base local/github images by @Szubie in #73
  • Remove attempts to remove LXD image of same name when deleting a unit by @Szubie in #74
  • Fix doc typos by @Szubie in #78
  • Update README with the new names for the LXD profile and storage pool by @Szubie in #79
  • Return an error when an unrecognized package manager is encountered. by @Szubie in #80
  • consider the case during brave base where package manager is not prov… by @idroz in #81
  • Raise error if empty package manager and packages to be installed by @Szubie in #82
  • create unit testing framework by @idroz in #89
  • Username sanitization by @Szubie in #90
  • Prevent shadowing of original error in init code by @Szubie in #88
  • Enable privileged mounts on windows to allow mounting using multipass by @Szubie in #85
  • GetUnits first check if eth0 key is in the map by @Szubie in #84
  • Replace map used for host config with a struct by @Szubie in #86
  • Testing by @Szubie in #92
  • Cleanup build by @Szubie in #77
  • Unit test fixes by @idroz in #94
  • Address apk update pause by @Szubie in #93
  • Update DB tests with initialization and teardown by @Szubie in #97
  • bravetools clean up after failed init by @Szubie in #96
  • Account for multipass backend in lxdCheck and checkLXDVersion by @Szubie in #95
  • Multiplatform tests by @Szubie in #98
  • add xgo xcompiler by @idroz in #101

New Contributors

Full Changelog: 1.55...1.56

Bravetools release 1.55

19 Oct 18:23
7cda84e
Compare
Choose a tag to compare

Mounting enhancements come to Bravetools! This release makes it possible to:

  • Seamlessly share UID/GID information between host and running Unit, enabling transparent read/write of mounted directories from LXD containers (#17)
  • Support for multiple mounts to a single Unit (#20)
  • Support for multiple forwarded ports between a single Unit and Host (#28)

Bug fixes

  • Ensure database is initialised correctly (#24)
  • Improved port/volume/ip information output

Bravetools version 1.54

04 Oct 20:47
b1a0305
Compare
Choose a tag to compare

This release makes it possible for Bravetools to be deployed on any system that supports LXD.

  • Minimal LXD version is now 3.0.3.
  • Internals have been changed to make Bravetools agnostic to snap or non-snap LXD versions
  • brave init elegantly handles existing LXD installations, seamlessly integrating Bravetools on top of existing setups

Backend operations

  • Bravetools now creates a new LXD bridge, bravebr0 instead of relying on existence of a default bridge
  • brave mount and brave umount support arbitrary directory paths
  • Port-forwarding uses LXD proxy device instead of iptables, making it more stable
  • brave deploy intelligently assess whether forwarded ports are available on the host prior to deployment #10
  • brave base and brave build on Windows now hands off container image to properly complete the build process #8

release-1.53

31 Aug 16:27
d7fa9ff
Compare
Choose a tag to compare

Welcome to Bravetools!

Bravetools is an open source tool for creating and managing System Containers for multiple platforms using a single source configuration. Bravetools makes it easy to build, deploy, and scale machine images.

Features

Improved Stability. All software and configurations are installed into your images at build-time. Once your image is launched and tested, you can be confident that any environment launched from that image will function properly.

No overheads of a VM. Bravetools runs on LXD. LXD uses Linux containers to offer a user experience similar to virtual machines, but without the expensive overhead. You can run either single images on a local machines or scale to thousands of compute nodes.

Focus on code not infrastructure. Maintaining and configuring infrastructure is difficult! With any application built and deployed using Bravetools infrastructure and environment have to be configured just once. Developers can spend more time on creating and improving software and less time on managing production environments.

release-1.52

28 Aug 10:46
Compare
Choose a tag to compare

Welcome to Bravetools!

Bravetools is an open source tool for creating and managing System Containers for multiple platforms using a single source configuration. Bravetools makes it easy to build, deploy, and scale machine images.

Features

Improved Stability. All software and configurations are installed into your images at build-time. Once your image is launched and tested, you can be confident that any environment launched from that image will function properly.

No overheads of a VM. Bravetools runs on LXD. LXD uses Linux containers to offer a user experience similar to virtual machines, but without the expensive overhead. You can run either single images on a local machines or scale to thousands of compute nodes.

Focus on code not infrastructure. Maintaining and configuring infrastructure is difficult! With any application built and deployed using Bravetools infrastructure and environment have to be configured just once. Developers can spend more time on creating and improving software and less time on managing production environments.