Go to file
Matthew Barnes 56d28a76f3 app: Add "deploy" command
Command-line interface for new D-Bus "Deploy" methods.
2015-11-06 09:10:48 -05:00
buildutil tests: Adapt to rpm-ostree daemon 2015-09-09 22:00:05 -04:00
design
doc docs: Add generated D-Bus interfaces 2015-09-09 22:00:04 -04:00
libglnx@0cf50c6735 daemon: Start of sysroot interface implementation 2015-09-09 22:00:04 -04:00
man app: Add "deploy" command 2015-11-06 09:10:48 -05:00
packaging daemon: Start of work on daemon 2015-09-09 22:00:04 -04:00
scripts
src app: Add "deploy" command 2015-11-06 09:10:48 -05:00
tests tests/test-basic.sh: make dots literal 2015-09-11 10:35:47 -04:00
.gitignore daemon: Start of work on daemon 2015-09-09 22:00:04 -04:00
.gitmodules
autogen.sh autogen.sh: tweak program checking logic 2015-09-11 10:24:44 -04:00
configure.ac automake: squash warnings re. subdir-objects 2015-09-11 10:30:09 -04:00
COPYING
Makefile-daemon.am daemon: Rename all the things! 2015-09-09 22:00:05 -04:00
Makefile-decls.am
Makefile-lib-defines.am lib: Add RpmOstreePackage 2015-04-16 13:26:58 -04:00
Makefile-lib.am (cleanup): Move the refsack and root loading code into libpriv 2015-05-20 20:51:42 -04:00
Makefile-libpriv.am libpriv: Add RpmOstreeRefTs and API to create one from a commit 2015-05-23 09:30:57 -04:00
Makefile-man.am
Makefile-rpm-ostree.am app: Add "deploy" command 2015-11-06 09:10:48 -05:00
Makefile-tests.am Makefile-tests.am: fix program typo in note 2015-09-11 10:25:38 -04:00
Makefile.am automake: squash warnings re. subdir-objects 2015-09-11 10:30:09 -04:00
README.md remove erroneous rpm-ostree equals /usr/bin/atomic reference 2015-05-28 11:51:39 -07:00
TODO

rpm-ostree

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