Composer, bower, gulp, svnignore.

[mikaelmattsson]

I'm guessing you are already running composer because Herbert uses it. But I couldn't find any info on it on the site. Also, if you are using composer, it would be nice if I were ably to add custom parameters like --optimize-autoloader --no-dev --prefer-dist

And what about bower and possibly gulp? Would it be possible to implement these and set it up so that it will always run gulp or gulp build.

.svnignore isn't an official thing, but could be a nice additional feature. I might want to specify some dev-specific files or direcories that should not be pushed to the svn plugin directory.

[jasonagnew]

We actually took composer install out of Ship for now, we had a lot of issues with our test plugin we used here. It’s dependencies would pull in test’s with requires PHP5.4+ code: example, causing WordPress.org to reject releases. We decided to commit the vendor folder and include below in the git ignore:

vendor/**/tests/

What would your thoughts on having a ship.json where you could do:

//No composer needed
{
    “composer”:false
}
//Or
{
    “composer”:”install —optimize-autoloader --no-dev --prefer-dist”
}

Then you could set files to remove/ignore

{
    “ignore”:{
            ‘vendor/**/test/’,
            ‘tests/local’
    }
}

We could use the same idea for Gulp or handling assets.

[mikaelmattsson]

This would be ideal. I figured you could put these in the control panel, but it is a way better idea to keep these settings visible and under version control like you suggest.

Is the environment isolated when doing this? Docker? This was a concern of mine when I was thinking of building something similar to Ship and giving people free access to it because I would not want people to be able to execute bash commands using composer scripts and possibly destroy the system.