Implement that with a logging adapter and a process-manager which logs everything. this log file can be written into the local directory and pulled to the server. also a dry-run can be implemented with that.

The config for password is always present (default in config). The check in ssh-connection is wrong (or false order)

Add option to restore latest backup.

The cleanup command should clear all the old backups in a configurable way. As an example:

• Each day for the last week
• Each week (first backup) for the last month
• Each Month (first backup) for the last year
• Each Year (first backup)

Change to format: Y-m-d_H-i-s

The size will increase while backup is running. If the backup size is 12GB for example the temp-dir will use at least this size. so the minimum free space for a single backup will be the double size of the resulting zip file.

A possible solution could be to implement a FilesystemAdapter with a zip streaming library.

./bin/console doctrine:phpcr:workspace:export asdf.xml --session default -p /cmf
./bin/console doctrine:phpcr:workspace:export asdf.xml --session default -p /jcr:versions
./bin/console doctrine:phpcr:workspace:export asdf.xml --session live -p /cmf
./bin/console doctrine:phpcr:workspace:export asdf.xml --session live -p /jcr:versions

only interresting for jackrabbit installations.

nanbando self-update throws error because padraic/humbug_get_contents has a deprecated method.

Multiple remote-storages should be configurable and specify for push and pull commands

This command should print following information:

• name
• description
• dependencies (which cannot be handled by composer)
• parameters (mandatory, optional and default values)

There should be a proper description for the update option.

Version: 0.8.1

Plugins should be able to hook into a backup process and extend configuration.

To achieve that the architecture has to be refactored. The whole process should be handled over events.

• PRE_BACKUP_EVENT:
  • Create destination and source
  • Create and fill system-database (with basic values)
  • (optional - with plugins) The configuration can be extended
• BACKUP_EVENT: Thrown foreach backup-part
  • Create part-database and write started to database
  • Find plugin
  • Resolve options
  • Call backup from plugin (inclusive exception handling)
  • Write finished, close and write database
• PRE_BACKUP_EVENT:
  • Write informations to database
  • Close and write system-database
  • Close destination & source

Same for restore.

The preset can hook into the PRE_BACKUP_EVENT. The check command should also be able to extend it. Maybe also call an CHECK_EVENT or a better name which can also be used.

Preset should have a PresetPool hook into the events and hold PresetInterface objects.

This Architecture should enable also other features in the future and make extensions more powerfull.

When local_directory is defined as relative path in nanbando.json file, i.e.:
"storage": {
"local_directory": "./backups"
}
nanbando backup command throws the following exception:
[League\Flysystem\Exception]
Impossible to create the root directory "./backups".

I've tried cloning nanbando/core and running pure PHP files instead of PHAR and it worked fine:
php ../local-nanbando-copy/bin/nanbando backup

Use packagist api to search for nanbando plugins (maybe by tag).

at least make it possible to restore them.

Enable environment variables. One example beside the database would be a environment variable like dev, prod, stage which will be used to generate the path where the backups will be stored. in the restore you should be able to choose also other environments.

Ask user if backup should be continued and save status in the database. when trying to restore print a warning message.

dflydev/dflydev-embedded-composer#20

Problem here is that the interact of the command has to lookup for local backups on the remote server.

See here: https://docs.travis-ci.com/user/deployment/releases/

The backup command will have a new options --process files which then only executes the backup-steps which has the process defined. All the other backups will be ignored. The default is all steps.

The backup will have a new database entry with process which will be used in restore command.

{
    "name": "application",
    "backup": {
        "data": {
            "plugin": "directory",
            "process": ["files"],
            "parameter": {
            }
        },
       {
            "plugin": "mysql",
            "process": ["databases"],
            "parameter": {
            }
        }
    }
}

@chirimoya @c00n64 can you add some thoughts?

This says more about the "actual" work of the command than update

https://github.com/romainneutron/Temporary-Filesystem

The update command should have a (optional) argument where the user can specify which version should be downloaded.

like composer composer self-update 1.2.4

Show how nanbando can be used in real-life examples.

• How remotes can be used to sync prod-stage
• How can sync developer the prod in their local dev environment
• How can ssh-servers be used to backup and download backups from prod-server

Hi,

If you run nanbando self-update (or probably any other nanbando command) without having nanbando.yml in your home directory, you'll get an error:
Fatal error: Uncaught exception 'Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException' with message 'The service "storage" has a dependency on a non-existent service "filesystem.remote".' in phar:///usr/local/bin/nanbando/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php on line 58

You could add an additional step to create the file to the docs before running the self-update command or throw an appropriate Exception if the file is not present

I think there are a few possible solutions for this issue:

• Add an additional step to the docs to make sure that the user adds the file
• Throw an appropriate Exception if the file is not existent
• Create the file with default values if it's not there

See https://travis-ci.org/nanbando/core/jobs/206264483

Currently the build creates broken phars. 0.8.0 was build locally and there it seems to work. Seems an incomatabillity between onup/flysystem-bundle and league/flysystem

Use it for source in backup / restore.

Presets for:

• Sulu > 1.3 & Jackrabbit & minimal
• Sulu > 1.3 & Mysql & minimal
• Sulu > 1.3 & Jackrabbit & standard
• Sulu < 1.3 & Jackrabbit & standard
• Sulu > 1.3 & Mysql & standard
• Sulu < 1.3 & Mysql & standard

Additionally detection of version an options.

Hi,

I think that the auto-completion in the fetch command is a bit confusing.

Let's assume I have 2 backups.

1. I enter nanbando fetch
2. This is displayed:

[0] 11-11-11 2016-11-11
[1] 23-11-25 2016-11-22

Now I want to fetch backup nr. 1 from 2016-11-22. If I type "1", the auto-completion suggests "11-11-11 2016-11-11". If I press enter, it fetches the backup I didn't want to fetch, just because it begins with 1.

Take a look at: https://github.com/xboston/phalcon-php-elasticsearch-backup

Integrate configuration of flysystem into nanbando.

In this step the oneup/flysystem-bundle can be removed.

I created a backup on Environment A with a message:
php nanbando.phar backup -m "Automatic backup from build server".

Now I want to apply (restore) this backup on Environment B:

The problem is that it's a bit difficult to distinguish the backups now. It would be great if the message of the backup would also be printed in the console.

Also: What exactly is the label argument good for when creating a backup?
This label will be used to generate the filename for the backup.

Is it really used in the filename? or is it "meta information" like the message?

When pushing data to a remote storage the system database should be pushed individually (e.g. application/2017-04-03-12-00-00.json) to enable read easily the configuration of the backup (over flysystem).

This feature is needed to enable following features:

• Cleanup Command #89
• Incremental Backup #84

Backup should be able to define "previous" backup. The backup command will have a new options --incremental. In the archive only new file will be saved and a list of deleted files.

This has to be handled in:

1. Restore: A ChainAdapter which receives a list of adapters in the right order and go thruh them foreach function in AdapterInterface.
2. Fetch & Get: load also the dependencies
3. Information: should display all the dependencies

@chirimoya @c00n84 can you add some thoughts?

when you do a self-update and have a bc break it should be shown the https://github.com/nanbando/core/blob/master/UPGRADE.md text.