Release 0.2 ("Portland")
2013-06-22
Hot on the heels of our first release (Grenoble), we're happy to be getting better at this release thing and announce 0.2, codename "Portland". Portland is my hometown and currently hosting IndieWebCamp.
Or browse at Github: github.com/bradfitz/camlistore/tree/0.2
What is Camlistore?
What works?
Everything that worked in 0.1.
New in 0.2
- Encryption support. It hasn't been audited yet, metadata compaction isn't quite done, and the simple-config-to-low-level-config translator isn't enabled yet, so consider it all beta. It's there to use if you know what you're doing, but the underlying format might yet change.
- Improved build system. Our build by default now embeds all the Closure resources into the server binary, making deployment much easier: just one file (the server binary) to put on your server.
- Easier initial setup. More helpful initial configuration of
camput, etc. - Config files moved. We now respect the XDG Base Directory Specification on Unix systems. If you had your config files in
~/.camlistore/before, move them to~/.config/camlistore/. - Fixes:
- The SQLite backend now uses WAL when available, for improved throughput with high concurrency. A bug in our build system's detection of SQLite was also fixed.
- The sharing handler was partially broken in 0.1, now fixed.
Get involved!
We welcome feedback, feature requests, bug reports, and code contributions!
Feel free to email us on our mailing list, and/or file a bug (or see existing bugs).
While we welcome user bug reports, we also welcome code contributions. See the Contributing page for details. While most the codebase (the server and command-line tools) are written in Go, there's also a lot of JavaScript which needs love, as well as Java (for Android) and Objective C (for iOS). Or anything useful you'd like to contribute.