| /*********************************************************************************************************************** | |
| *********************************************************************************************************************** | |
| * CONTENTS: | |
| * Native Object | |
| * Object Literal | |
| * Basic Object | |
| * Psuedo-Class | |
| * Self Executing/Invoking Structure | |
| * Lazy Function | |
| * Module Pattern |
I've made a new web template to make Laravel work easily on VestaCP, and so I wouldn't have to change my Laravel installation, if I ever wanted to deploy it elsewhere.
Each file should be put in /usr/local/vesta/data/templates/web/apache2
Then, when you edit your domain/site, you can change the web template to Laravel and just upload your whole project into public_html
The git command-line utility has plenty of inconsistencies http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/
A GUI like http://sourcetreeapp.com is often helpful, but staying on the command line usually quicker. This is a list of the commands I use most frequently, listed by funcional category:
git status list which (unstaged) files have changed