NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #2476 by repository stars
Last release 6 years ago
no release in 18 months
Ships unpredictably
gaps range from 9 days to 1.8 years
Nearly every release is documented
notes for 5 of 5 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
13 releases · first in 2018
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
Mostly a bugfix release. Short summary:
Mostly a bugfix release. Short summary:
--offline flag to a bunch of sub commands.See the CHANGELOG for a lot more details.
A smaller release with some bug fixes and a few new features. Also one bigger stability and speed improvement. Thanks to everyone that gave feedback!
cat, tar,
mount and fstab add. These flags will only output files that are
locally cached and will not cause timeouts therefore. Trying other files will
result in an error.brig from the
develop branch. Thanks @vasket!brig remote ls command no longer does active I/O between nodes to check
if a node is authenticated. Instead it relies on info from the peer server
which can apply better caching. The peer server is also able to use information
from dials and requests to/from other peers to update the ping information.blake2s-256 from sha3-256.
This change was made for speed reasons and leads to a slightly different looking
checksum format in the command line output. This change MIGHT lead to incompatibilities.scrypt with argon2 for key derivation and lower the hashing settings
until acceptable performance was achieved.Nothing published for this version
New feature release with the following main features:
New feature release with the following main features:
See the CHANGELOG for a lot more details.
It's only been a few months since the last release (December 2018), but there are a ton of new features / general changes that total in about 15k added lines of code. The biggest changes are definitely refactoring IPFS into its own process and providing a nice UI written in Elm. But those are just two of the biggest ones, see the full list below.
As always, brig is always looking for contributors. Anything from
feedback to pull requests is greatly appreciated.
The IPFS daemon does not live in the brig process itself anymore.
It can now use any existing / running IPFS daemon. If ipfs is not installed,
it will download a local copy and setup a repository in the default place.
Notice that this is a completely backwards-incompatible change.
New UI: The Gateway feature was greatly extended and an UI was developed that
exposes many features in an easily usable way to people that are used to a
Dropbox like interface. See
here for some
screenshots of the UI and documentation on how to set it up. The gateway
supports users with different roles (admin, editor, collaborator,
viewer, link-only) and also supports logging as anonymous user (not by
default!). You can also limit what users can see which folders.
New event subsystems. This enables users to receive updates in "realtime"
from other remotes. This is built on top of the experimental pubsub feature
of IPFS and thus needs a daemon that was started with
--enable-pubsub-experiment. Users can decide to receive updates from
a remote by issuing brig remote auto-update enable <remote name>. More
details in the documentation.
Change the way pinning works. brig will not unpin old versions anymore,
but leave that to the repinning settings.
This is an automatic process that will make sure to keep at least x
versions, unpin all versions greater than y and make sure that only a
certain filesystem quota is used.
New trash subcommand that makes it easy to show deleted files (brig trash ls) and undelete them again (brig trash undelete <path>).
New brig push command to ask a remote to sync with us. For this to work
the remote needs to allow this to us via brig remote auto-push enable <remote name>. See also the
documentation.
New way to handle conflicts: embrace will always pick the version of the remote you are syncing with.
This is especially useful if you are building an archival node where you can push changes to.
See also the documentation.
You can configure the conflict strategy now either globally, per remote or for a specific folder.
Read only folders. Those are folders that can be shared with others, but when we synchronize with them, the folder is exempted from any modifications.
Implement automated invocation of the garbage collector of IPFS. By default
it is called once per hour and will clean up files that were unpinned. Note
that this will also unpin files that are not owned by brig! If you don't want this,
you should use a separate IPFS instance for brig.
It's now possible to create .tar files that are filtered by certain patterns.
This functionality is currently only exposed in the gateway, not in the command line.
Easier debugging by having a pprof server open by default (until we
consider the daemon to be stable enough to disable it by default). You can get
a performance graph of the last 30s by issuing go tool pprof -web "http://localhost:$(brig d p)/debug/pprof/profile?seconds=30"
One way install script to easily get a brig binary in seconds on your computer:
bash <(curl -s https://raw.githubusercontent.com/sahib/brig/master/scripts/install.sh)
make lint)init will now set some IPFS config values that improve connectivity and performance
of brig. You can disable this via --no-ipfs-optimization.go mod since we do not need to deal with gx packages anymore.make install target anymore. Simply do make and
sudo cp brig /usr/local/bin or wherever you want to put it.brig is now much snappier.This releases the newly written Gateway feature. See the CHANGELOG for more details.
This is the first release of brig to a slightly larger audience. It is released under the motto " it's 80% finished! " It still has a few rough edges,
This is the first release of brig to a slightly larger audience.
It is released under the motto "it's 80% finished!"
It still has a few rough edges, but unless you trust it as primary data source (don't do that!) it
should be safe to play around with. After all, it needs YOU (yes, you!) to make it past the beta phase.
You can find more details about brig in the documentation as always.
The development of brig has reached a point where it does not make any sense
anymore to develop it without any help from the community. I hope to find some
users (read: crash dummies) that help me see issues with the current design of
brig, its ongoing development and my possible tunnel vision. I'm of course also
happy with any help regarding development, be it pull requests or discussions.
There are currently many areas that deserve to be worked on:
Performance is currently really a constraint to make it smooth. A lot of
brig was developed while commuting in the train, therefore I spend more
time on offline operations than on fiddling with network setups (try that while
sitting in a train 😏). I'm sure you guys will find quite a lot for improvement,
especially regarding transfer speed.
All features mentioned in the documentation should work now.
Many new features, including password management, partial diffs and partial syncing.
Many internal things. Too many to list in this early stage.
Nothing substantial.
Nothing.
v.0.1.0 improved release
v.0.1.0 improved release
Initial release on the Linux Info Day 2018 in Augsburg.
Nothing published for this version
This release marks the very first milestone towards a production ready version of brig .
This release marks the very first milestone towards a production ready version of brig.
🍾 😁 🎉
All documented features are implemented, but still are buggy. Bug requests and bug fixes are welcome!
Please view the documentation to get started:
http://brig.readthedocs.io/en/latest
DISCLAIMER: THIS IS UNSTABLE SOFTWARE. DO NOT USE IT FOR PRODUCTION DATA.
IT WILL EAT YOUR FILES IN CREATIVES WAYS.
This release was presented on the Linux Presentation Day in Augsburg 2018.
Your coding agent can read these notes before it upgrades. Set up the MCP server →