leroy-merlin-br / dployer Goto Github PK

The option --parents doesn't work on Mac machines. Use a workaround solution to fix this. Maybe create folders manually to work OS agnostic =(

--verbose option catch every output line in exec command and displays them at once.

If deploy command is executed in interactive mode, output should ask user before runs each command configured in .dployer file

@Zizaco and @GuilhermeGuitte:

I think that these recent pull requests (#6, #9 and #10) resolves our actual problems.I think we can create a new version of dployer bin and tag it with version 1.1:

Main changelog:

• Added configuration file
• Moved application and environment arguments to config file
• Create events
• Configurable scripts by event
• Interactive mode
• More Verbosity

What do you guys think?

• Rebuild dployer bin
• Update README.md file
• Tag 1.1 version

Even if you don't use this parameter when you run deploy command, dployer asks for confirmation before run every script.

Create a configuration file in the project base path to configure deploy process. The file should follow this structure:

{
    "application": "MyAwsomeApplication",
    "environment": "my-staging-env",
    "scripts": {
        "init": "composer dumpautoload",
        "another-random-event": [
            "echo 'Keep going...'", 
            "echo 'Almost there!'"
        ],
        "finish": "echo 'Nicely done! =)'"
    },
    "exclude-path": [
        "path/to/non-deployed-folder",
        "i-dont-want-to-deploy-this-file.log"
    ]
}

Note: even with application and environment keys in the configuration file, the deploy command should keep the possibility to pass this arguments as command parameters.

To do:

• Create sample configuration file to test.
• Create class to read config keys.
• Remove required option from app and environment arguments in deploy command
• Exclude paths in the exclude-path key before ZIP them.
• Add support to dispatch events.
• Create a class to listen the events and execute commands.
• Apply key events in deploy process, i.e, init, finish, before-pack, after-version-deploy...

If deploy command is executed with --verbose argument, the command should display outputs from scripts that are configured in .dployer file

Note: Save -v (in lowercase) argument to display version in the future