Go to file
Matthew Barnes b827a398a7 RpmOstreeCommand: Remove unused 'flags' member
There are currently no command flags defined, but if we need any they
would likely be passed to the custom GOptionContext parse function as
in OSTree.
2014-12-01 09:25:53 -05:00
design design/package-layering: New file 2014-06-18 08:48:03 -04:00
doc docs: Update sample treefile example and add example repo file 2014-11-24 17:52:58 -05:00
man docs: Fix a typo 2014-10-08 23:01:53 -04:00
packaging packaging: Update BRs 2014-11-14 18:07:47 -05:00
scripts scripts/ostree-ls-big-files.js: New script to analyze repo files for size 2014-01-29 17:55:07 -05:00
src RpmOstreeCommand: Remove unused 'flags' member 2014-12-01 09:25:53 -05:00
tests Check rpm-ostree status output 2014-10-28 13:30:08 -04:00
.gitignore Add basic man page 2014-03-25 09:07:49 -04:00
autogen.sh Use the now external libgsystem 2014-02-07 17:29:40 -05:00
configure.ac Show capability list with --version option 2014-11-26 14:09:15 -05:00
COPYING COPYING: Update to latest LGPLv2+ 2014-03-10 16:40:16 -04:00
Makefile-decls.am
Makefile-man.am Add basic man page 2014-03-25 09:07:49 -04:00
Makefile-rpm-ostree.am compose: Introduce a little 'libcontainer', use it for the post script 2014-11-21 13:16:49 -05:00
Makefile-tests.am Import some basic testing infrastructure from OSTree 2014-09-29 16:25:36 -04:00
Makefile.am Show capability list with --version option 2014-11-26 14:09:15 -05:00
README.md doc: More updates, note atomic status, flesh out tradeoffs 2014-11-01 10:33:39 -04:00
TODO TODO: Update 2014-03-31 16:33:05 -04:00

rpm-ostree, aka /usr/bin/atomic

An system to compose RPMs on a server side into an OSTree repository, and a client side tool to perform updates.

The project aims to bring together a hybrid of image-like upgrade features (reliable replication, atomicity), with package-like flexibility (seeing package sets inside trees, layering, partial live updates).

rpm-ostree is in beta!

While many of the underlying technologies here are stable, if you are considering using this in your organization, you should perform a careful evaluation of the whole stack. Software updates are obviously critical, and touch on many areas of concern.

Contents