Not much to say but I’ve had great success with it on projects. I’m working on a new wordpress site using this and git modules. (More to come on that)
https://box.scotch.io/
Month: June 2016
Current Setup(s)
Browsers
Chrome (up to date)
- Postman
- Web Developer
- Edit This Cookie
- Gitlab Notifier
- The Great Suspender
Safari (up to date)
Firefox (up to date)
For older versions of Firefox, I use a simple app called MultiFirefox.
You need to create a default profile for the up-to-date version and then a profile named after the version it is the profile it is for.
Download each release you want, open the image one at a time, drag the Firefox.app file to your desktop, then rename it to the version it is Firefox_14.0.1.app. Take the file and now put it in your applications folder.
Open the MultiFirefox app and pick the version and profile you want and click start. You now can run as many version as you want and not break profiles.
Homebrew
This is a great application to install anything you need linux related.
Bash / iTerm2
Git
Git Flow
MySQL Workbench
Other options
Atom
Plugins
- Atom Beautify
- Bracket Matcher
- Highlight Line
- Highlight Selected
- Merge Conflicts
- Project Manager
- Todo-Show
MacDown
OpenOffice
Evernote
SourceTree
Slack
Git Submodules
https://git-scm.com/book/en/v2/Git-Tools-Submodules
I took on a simple wordpress website. Well yes the site is very simple, almost no custom development but, it is wordpress and I am trying to do things with best practices. So it hasn’t been easy.
- Getting a virtual environment working has been a headache.
I settled on Scotchbox because it had a lot of tools but didn’t require to many strange dependencies like ruby plugins when my site is only php behind nginx or apache.
- I wanted to have a git repo for the environment to do code on multiple computers or to be able to hand off the project to someone else if I ever needed too.
-
I wanted to have a git repo for the theme to be able to have releases and features.
This is the most difficult part.
Create the theme as its own git repository.
It can be a single file to start, this only to get the module setup going.
Create the top level of your project (ie the contents of a wordpress install). Use the GIST to ignore basically everything but the vagrant file, your gitmodule file and the path to the theme you are developing.
Structure:
/website-server
VagrantFile
.gitignore (see gist file below)
.gitmodules
.git
/public_html
/wp-content
/themes
/website-theme-01
.gitignore
.git
Follow these direction using the path to your theme in the themes folder.
git-submodules-adding-using-removing-and-updating
Once that is setup, you will be able to commit any vagrant file changes to your wordpress-site-vagrant repo and any changes to your theme can be committed to your website-theme-01 repo.
Now developing themes is a harmony and is easy to replicate across projects and is easy to share a project to multiple developers.