Default and user gitconfig

[scottrigby]

CC @conortm @ericduran @breathingrock

There are so many things I want in my gitconfig, and it's annoying to add if we want these VMs to be treated as disposable.

Question

What does Acquia's default gitconfig look like?

Note

we could do something like this.

Related

For the user override part, see #52.

[ericduran]

I say we leave this for the user. Most people will not be managing the repo from the box. The git portion of it is on the users pc .

This is why I want a user base ansible.

Also Acquia doesn't do anything because you don't manage the repo on their server with git.

[scottrigby]

@ericduran OK I definitely agree the user ansible stuff is important ( #52 ). For this i was thinking some defaults might be useful, but maybe you're right that git configs don't belong on the base vm because they're not on Acquia.

But it might be interesting to make a separate project devs can pull in to start with (an example of a good NBCU dev user playbook… maybe gitconfig would be a good idea there)?

One thing I don't agree with though is the idea that most people should do their git work outside the vm (if we recommend this, why do we install drush?). But cool, people can do it in or outside.

[ericduran]

Yea, that's fair. That being said we install drush because you need it on the server to run drush command from a remote. So the drush alias won't work if drush isn't on the server.

[scottrigby]

OK you're right. I'm still hoping running git from within the VM isn't horribly slow, because that would be my personal ideal (so I can load up all the tools I would need in my user ansible playbook on my VM if it's not in our shared set of tools)

[scottrigby]

Either case, we agree this should not be in the default playbooks. I'm gonna close this one :)

[ericduran]

Yea, that being said I do think if you want to run git from the VM it shouldn't be slow, do we want to start a performance task?

[scottrigby]

@ericduran totally, just make #75 :+1: