Someone at WordPress decided that if you want to create a plugin for WordPress, you’ll have to host it at their SVN server. Personally I’m not a big fan of SVN, I’m more a GIT person.
- Github wants a README.md (markdown) file and WordPress wants a readme.txt file with some required options
- How do I deploy a new version of my plugin to the WordPress SVN server?
- And how can I make this proces as easy as possible?
Grunt to the rescue
You can instruct it to do some tasks for you. These steps I created to make my life as a WordPress Plugin developer easier:
- Use ‘wp_readme_to_markdown‘ to create a README.md file right from the required README.txt
- Use ‘grunt-contrib-copy‘ to create a ‘build’ folder with all the files required for the plugin
- Use ‘grunt-wp-deploy‘ to parse the ‘readme.txt‘ and the ‘rest-api-filter-fields.php‘, to verify their version tags match (required) and to deploy this new version to the wordpress svn
This way when I edit my readme.txt, I run ‘grunt build‘ to create the readme.md file (for Github). This takes about 1 second. And it makes sure they both have the same text (only formatted slightly different).
If I edited the plugin (and the version number / changelog), I enter the command ‘grunt deploy‘. It then copies all the files to the ‘build’ directory, asks me if I want to deploy the version x. And then it prompts for my wordpress svn password.
Sounds good, how do I use it?
Before you get started you’ll have to make sure that you install ‘node‘,’npm‘ and ‘grunt-cli‘.
The first two should be easy, the last one can be installed by using ‘npm install -g grunt-cli‘
Getting started with Grunt is described at their site, see Getting Started. Using the modules to create the readme.md and to publish the plugin, are also not that hard. Just check-out their repositories.
If you cannot get this setup (for publishing your wordpress plugin) working, you can always have a look at the Gruntfile.js file in the repository.