Strategy for using git on laravel project when using git to manage Laravel4-Vagrant

[erichgoldman]

My plan is to manage the changes I make to laravel4-vagrant using git, but I also want to manage my laravel changes using git. I am not quite sure how to set this up as /var/www is ignored and that is where my work would be. Can I start a git repo there somehow so that way outside of the VM I can use git to then manage a specific laravel project? e.g., I want to be able to vagrant up, do some work, manage my work in git, have my laravel project saved outside of the vm, and be able to redeploy via vagrant and then load up my laravel git repo. How is the best way to go about doing this, or should I be following a different game plan?

[SegFaultx64]

I am doing this now. Let me see if I can dig up an example for you.

On Fri, Mar 14, 2014 at 7:37 PM, Eric notifications@github.com wrote:

My plan is to manage the changes I make to laravel4-vagrant using git, but
I also want to manage my laravel changes using git. I am not quite sure how
to set this up as /var/www is ignored and that is where my work would be.
Can I start a git repo there somehow so that way outside of the VM I can
use git to then manage a specific laravel project? e.g., I want to be able
to vagrant up, do some work, manage my work in git, have my laravel project
saved outside of the vm, and be able to redeploy via vagrant and then load
up my laravel git repo. How is the best way to go about doing this, or
should I be following a different game plan?

Reply to this email directly or view it on GitHubhttps://github.com//issues/59
.

• Max Walker

[robwalkerco]

I've just been trying to work out how to get around this same problem as well? Did you find a solution to this?
Thanks

[erichgoldman]

I was reading this today: Git submodules and going through some posts on stack overflow. I haven't had the opportunity to try this out yet, but I believe that if the folder is set as a submodule it will be ignored by the parent? I will attempt to try this out, but if there are any git experts perhaps they can opine. I think there may also be some complications when setting this to deploy because laravel is not installed by cloning the git repo, but I would imagine this could somehow be scripted into vagrant so it will be all setup as a base and then easy to change if you already have a laravel project in a git repo.