Goals: – Keep a local WordPress \u00a0installation under version control (but ignore WordPress core files) – Use WP-Skeleton (wordpress core as submodule in separated folder, content and config files in root) – Use\u00a0the starter theme Roots 101 – Deploy to a staging and production server (depending on the current Git branch?) – Keep uploads out of version control, sync them separately – Use a\u00a0good DB migration strategy – If possible: automate repetitive tasks<\/p>\n
– Windows 7 – WAMP – Cygwin (linux environment) – Git, (Ruby, Compass, Grunt, Rsync) – Bitbucket account – SSH access to server (shared host) – SSH-keys set up for your servers and Bitbucket<\/p>\n
If you set up this project recently, you can use an existing repo with WP-Skeleton and roots. See 1b.<\/em><\/p>\n Create a new repository with your project name on bitbucket. Then push:<\/p>\n Remove the temp folder created in the steps above – open up the url localhost\/project\/wp\/wp-admin in your browser Now clone a theme. We will use Roots 101. You can clone it into a folder named after your project. the default name of the folder is roots.<\/p>\n Add and commit the changes<\/span><\/p>\n <\/del><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n
mkdir temp\ncd temp\ngit clone git@bitbucket.org:[USERNAME]\/wordpress-skeleton-[version].git .\nrm -rf .git\nrm .gitmodules\nrm -rf wp\ngit init\ngit add .\ngit submodule add https:\/\/github.com\/WordPress\/WordPress.git wp\ncd wp\ngit tag\ngit checkout [version]\ncd ..\ngit add .\ngit commit -m'setup skeleton'<\/pre>\n<\/li>\n<\/ul>\n
\n
\n
git remote add origin git@bitbucket.org:[username]\/[projectname].git\ngit push -u origin --all\n\n#Of course there should be an easier way to remove history, but for now this works<\/pre>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
\nNow create a project folder and clone the repository into a subfolder (e.g. www). Recursively, because the wp submodule should also be cloned (don’t need to add\u00a0–recursive if\u00a0you added a localized WP installation as descrived above).<\/p>\ngit clone --recursive git@bitbucket.org:USERNAME\/PROJECTNAME.git www<\/pre>\n
1b. Headstart from existing repo<\/h4>\n
\n
\n
git remote add origin git@bitbucket.org:[username]\/[projectname].git\ngit push -u origin --all<\/pre>\n<\/li>\n
\nNow create a project folder and clone the repository into a subfolder (e.g. www). Recursively, because the wp submodule should also be cloned.<\/p>\ngit clone --recursive git@bitbucket.org:USERNAME\/PROJECTNAME.git www<\/pre>\n<\/li>\n<\/ul>\n
2. Local Database and aliases<\/h4>\n
\n
3. Configure\u00a0Wordpress files<\/h4>\n
\n
\n
\/\/ debug for local development\ndefine('WP_DEBUG', true);\ndefine('WP_DEBUG_LOG', true);\ndefine('SAVEQUERIES', true);\n\nini_set('log_errors',TRUE);\nini_set('error_reporting', E_ALL);\nini_set('error_log', dirname(__FILE__) . '\/error_log.txt');<\/pre>\n<\/li>\n
\n<\/span>$table_prefix \u00a0= ‘wp09g3h4kg_’;
\n<\/span><\/span><\/span><\/li>\n===================================================\n\/\/ Load database info and local development parameters\n\/\/ ===================================================\nif ( file_exists( dirname( __FILE__ ) . '\/local-config.php' ) ) {\n define( 'WP_LOCAL_DEV', true );\n include( dirname( __FILE__ ) . '\/local-config.php' );\n} else {\n define( 'WP_LOCAL_DEV', false );\n if (file_exists( dirname( __FILE__ ) . '\/.staging' ) ) { \/\/ STAGING SERVER\n define( 'DB_NAME', '%%STAGING_DB_NAME%%' );\n define( 'DB_USER', '%%STAGING_DB_USER%%' );\n define( 'DB_PASSWORD', '%%STAGING_DB_PASSWORD%%' );\n define( 'DB_HOST', '%%STAGING_DB_HOST%%' ); \/\/ Probably 'localhost'\n } else {\n define( 'DB_NAME', '%%DB_NAME%%' );\n define( 'DB_USER', '%%DB_USER%%' );\n define( 'DB_PASSWORD', '%%DB_PASSWORD%%' );\n define( 'DB_HOST', '%%DB_HOST%%' ); \/\/ Probably 'localhost'\n }\n}<\/pre>\n\n
if ( WP_LOCAL_DEV ) {\n define( 'WP_CONTENT_URL', 'http:\/\/' . $_SERVER['HTTP_HOST'] . '\/wptest7\/content' );\n} else {\n define( 'WP_CONTENT_URL', 'http:\/\/' . $_SERVER['HTTP_HOST'] . '\/content' );\n}<\/pre>\n<\/li>\n\n
\n
define('WP_MEMORY_LIMIT', '64M')<\/pre>\n<\/li>\n\/\/ forces the filesystem method: \"direct\", \"ssh\", \"ftpext\", or \"ftpsockets\"\ndefine('FS_METHOD', 'ftpext');\n\/\/ absolute path to root installation directory\ndefine('FTP_BASE', '\/path\/to\/wordpress\/');\n\/\/ absolute path to \"wp-content\" directory\ndefine('FTP_CONTENT_DIR', '\/path\/to\/wordpress\/wp-content\/');\n\/\/ absolute path to \"wp-plugins\" directory\ndefine('FTP_PLUGIN_DIR ', '\/path\/to\/wordpress\/wp-content\/plugins\/');\n\/\/ absolute path to your SSH public key\ndefine('FTP_PUBKEY', '\/home\/username\/.ssh\/id_rsa.pub');\n\/\/ absolute path to your SSH private key\ndefine('FTP_PRIVKEY', '\/home\/username\/.ssh\/id_rsa');\n\/\/ either your FTP or SSH username\ndefine('FTP_USER', 'username');\n\/\/ password for FTP_USER username\ndefine('FTP_PASS', 'password');\n\/\/ hostname:port combo for your SSH\/FTP server\ndefine('FTP_HOST', 'ftp.example.org:21'); \n<\/pre>\n<\/li>\ndefine( <\/code>'WP_POST_REVISIONS'<\/code>, 3 );<\/code><\/code><\/div>\n<\/div>\n<\/div>\n<\/li>\n\/content\/uploads\/<\/span><\/pre>\n<\/li>\n<\/ul>\n\n
\n
\n<\/strong><\/strong>Consider adding the following files to git.ignore<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n.staging\n.production\n*.log\n.htaccess\n.DS_Store\n*.bak\n*.swp\nThumbs.db\n*.log\n\/*DB backups (folders depend on the plugin you use)*\/\nwp-content\/backup-db\/\n\/*Cache files (folders depend on the cache plugin you use)*\/\n\nwp-content\/advanced-cache.php\nwp-content\/wp-cache-config.php\nwp-content\/cache\/*\nwp-content\/cache\/supercache\/*\nwp-content\/cache\/\n\n*\/+ the files in .gitignore of roots theme*\/\n\n*\/specific live-only OR development-only plugins*\/<\/pre>\n
\n
\/assets\/vendor\/*\n\/assets\/css\/main.css.map\n\/assets\/css\/*main*.css\n\/assets\/js\/*scripts*.js\n\/assets\/js\/vendor\/modernizr.min.js\n\/assets\/manifest.json\n<\/pre>\n<\/li>\n
4.\u00a0Install wordpress locally<\/h4>\n
\n– Do the install
\n– Log in
\n– Change the site address to the root folder (instead of the sub folder wp)
\n– Optional: change tagline, time format, timezone
\n– Change permalinks to postname (preset)
\n– If htaccess not writable: changer permissions to 666 (temporarily After changes are made, change it back to 644)
\n– Add and commit the changes (to .htaccess) with message: \u2018changed permalinks and site url\u2019
\n– Push to bitbucket<\/span><\/p>\n5. Install Roots 101 via a git branch<\/h4>\n
- git checkout -b roots\n- git branch\n- cd content\/themes<\/pre>\n
git clone https:\/\/github.com\/roots\/roots.git THEMENAME<\/pre>\n
\n
\n<\/span>cd PROJECTNAME
\n<\/span>rm -rf .git
\n<\/span>rm .gitignore<\/span><\/span><\/li>\n\/*\nTheme Name: THEME NAME\nTheme URI: WEBSITE URL\nDescription: Custom theme for ..\nVersion: 1.0.0\nAuthor: YOUR NAME\nAuthor URI: YOUR URL\n\nLicense: MIT License\nLicense URI: http:\/\/opensource.org\/licenses\/MIT<\/a>\n*\/<\/pre>\n<\/li>\n
git status\ngit add .\ngit commit -m'Addition of the Roots 101 Theme'<\/pre>\n
6. Setup Roots 101<\/h4>\n
\n
\n
package.json<\/code> by running the following from the Roots theme directory.
\nNote: this doesn’t work with cygwin for me. I need to run the command from a windows command prompt. Also: run command prompt as admin<\/strong><\/strong>NOTE 2: if there is already a\u00a0node_modules folder (from a previous installation), remove it first!<\/li>\nnpm install<\/pre>\n<\/li>\n
\ngrunt dev –\u00a0Compile LESS to CSS, concatenate and validate JS<\/span><\/span>
\n(I had permission problems on my new windows 7 install. Setting the noacl option in fstab solved it. see this post<\/a>)grunt watch –\u00a0Compile assets when file changes are made<\/span>
\ngrunt build –\u00a0Create minified assets that are used on non-development environments<\/span><\/span><\/li>\n
Note:<\/strong> I opted for the old Roots approach concerning the building of minified assets. see next part (‘Adding *.min.css …’)
\n<\/span>You need to add\u00a0define('WP_ENV', 'development');<\/code><\/del>\u00a0to your wp-config.php, while developing, so your Roots won’t look for the minified version.<\/p>\ngrunt dev<\/code>\u00a0basically will do all the work but* minifying;
\ngrunt watch<\/code>\u00a0will run\u00a0grunt dev<\/code>\u00a0when something is modified;
\ngrunt build<\/code>\u00a0will do all the work + minify, so you can send your project to your production server.<\/p>\n\n
\n
Add\u00a0define('WP_ENV', 'development');<\/code>\u00a0to wp-config.php;<\/del><\/li>\ngrunt watch<\/code>;<\/li>\ngrunt build<\/code>;<\/li>\n