Go to file
Colin Walters 5235cc5559 doc: Delete bit about having to disable SELinux
This is only true for the libguestfs-based disk image generation.
2015-02-05 09:07:54 -05:00
buildutil tests: Enable glib-tap.mk 2014-12-19 10:47:55 -05:00
design design/package-layering: New file 2014-06-18 08:48:03 -04:00
doc doc: Delete bit about having to disable SELinux 2015-02-05 09:07:54 -05:00
man Fix small typo in manpage 2015-01-15 15:49:07 +01:00
packaging packaging: Update BRs 2014-11-14 18:07:47 -05:00
scripts compose: Add check-passwd/group JSON options, fails compose if uids/gids change 2014-12-18 16:59:33 -05:00
src build: replace libhif/hif-context-private.h with libhif/hif-utils.h 2015-02-03 11:07:54 +01:00
tests tests: Add tests for automatic_version_prefix 2015-01-12 15:13:55 -05: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 build: Require 0.2.0 libhif, drop hawkey/libsolv build option 2015-02-02 16:44:06 -05:00
COPYING COPYING: Update to latest LGPLv2+ 2014-03-10 16:40:16 -04:00
Makefile-decls.am Import some code for using GJS 2014-01-03 17:14:10 -05:00
Makefile-man.am Add basic man page 2014-03-25 09:07:49 -04:00
Makefile-rpm-ostree.am [libhif] Port to new hif_error_set_from_hawkey() 2015-02-02 16:39:26 -05:00
Makefile-tests.am tests/jsonutil: New test 2014-12-19 10:47:55 -05: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