Go to file
2015-04-10 16:51:25 -04: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
libglnx@376219a9c2 libglnx: Update 2015-04-10 16:28:23 -04:00
man man/rpm-ostree.xml: fix XML tag 2015-03-28 13:33:50 +01:00
packaging Makefile.dist-packaging: fix make rpm with submodules 2015-03-06 14:30:02 +01:00
scripts compose: Add check-passwd/group JSON options, fails compose if uids/gids change 2014-12-18 16:59:33 -05:00
src compose: Drop internal containerization for now 2015-04-10 16:48:36 -04: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
.gitmodules Start using libglnx 2015-02-15 14:01:13 -05:00
autogen.sh Fix running autogen.sh from outside the source directory 2015-04-08 09:16:17 +02:00
configure.ac Release 2015.4 2015-04-10 16:51:25 -04: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 build: Split up src into app/ and libpriv/ 2015-04-08 16:17:06 -04:00
Makefile-tests.am build: Split up src into app/ and libpriv/ 2015-04-08 16:17:06 -04:00
Makefile.am Start using libglnx 2015-02-15 14:01:13 -05:00
README.md README.md: Fix minor typo 2015-03-09 11:37:56 -04:00
TODO TODO: Update 2014-03-31 16:33:05 -04:00

rpm-ostree, aka /usr/bin/atomic

A 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