{ "info": { "author": "Frank Sachsenheim", "author_email": "funkyfuture@riseup.net", "bugtrack_url": null, "classifiers": [ "Development Status :: 4 - Beta", "Environment :: Console", "Intended Audience :: System Administrators", "License :: OSI Approved :: ISC License (ISCL)", "Operating System :: POSIX", "Programming Language :: Python", "Programming Language :: Python :: 3", "Programming Language :: Python :: 3.4", "Programming Language :: Python :: 3.5", "Programming Language :: Python :: 3.6", "Programming Language :: Python :: Implementation :: CPython", "Topic :: System :: Archiving :: Backup" ], "description": "Overview\n========\n\n::\n\n This piece of code is tested with only a small number of use-cases yet.\n You are invited to contribute.\n\n\n``compose-dump`` let's you backup and (not yet) restore `Docker Compose`_\n-projects. Like ``docker-compose`` this tool operates usually in a project-\nfolder. It's intended to be a simple tool for usage within a broader\nbackup-logic. The extent of a backup can be controlled by content scopes and\nservices.\n\nMain features\n-------------\n\n- Archives Docker Compose projects.\n- Optionally include configuration with all its referenced files.\n- Optionally include volumes of specified services.\n- Store dumps in a directory, as archive on disk or as archive to the standard\n output.\n\n\nSee planned features below.\n\nInstallation\n------------\n\nWith `pipsi`_ (recommended to avoid library version conflicts)::\n\n $ pipsi install compose-dump\n\nOr with `pip`_::\n\n $ pip install compose-dump\n\nTo install an editable development instance::\n\n $ cd compose-dump\n $ pipsi install -e . # or use `pip`\n\nUsage\n-----\n\nExamples\n~~~~~~~~\n\nFully dump a compose-project from ``project_path`` to ``/var/backups/compose``::\n\n $ cd project_path\n $ compose-dump backup -t /var/backups/compose\n\nWrite a gzip-compressed archive to a remote host via ssh::\n\n $ cd project_path\n $ compose-dump backup -x gz | ssh user@host \"cat - > ~/backup.tar.gz\"\n\nOnly dump configuration and data from container-volumes of the service ``web``::\n\n $ compose-dump backup --config --volumes web\n\nBackup all projects with a ``docker-compose.yml`` to ``/var/backups/compose``::\n\n $ find . -name \"docker-compose.yml\" -type f -execdir compose-dump backup -t /var/backups/compose \\;\n\nCommand line reference::\n\n $ compose-dump\n $ compose-dump backup --help\n\nBackup structure\n~~~~~~~~~~~~~~~~\n\nAny data that is located outside the project's scope is ignored. In\nparticular this are mounted volumes that are not in the project-path or below\nand volumes in ``volumes_from``-referenced containers. Consider this not as\na limitation, but as a feature to endorse good practices; handle these\nobjects in your broader backup-logic.\n\nThe resulting dump is structured this way:\n\n::\n\n + _______