Hello Magnus and thanks for your answer !
I tried to be crystal clear, that's why I described all the steps I did...
Seems I didn't succeed. So I will start by saying I never encountered a
issue with git itself. It's just the project I took that is build on a very
strange coding way. I can't work with it on windows. At all. (slashes
issues, fonts issues, and a lot more. Don't ask; I curse the previous
developper every then and now ^^)
What I really need is just advices on how to work as a team. Not about
branching and this kind of things, I got it. But about the environnment to
use for every developer when working on a regular project (not a messy one
like the last I worked on). Subdomains ? Local machine with easyPHP or
another local webserver and commiting when ready for testing ? If so, what
about eventually needed callbacks like Paypal's ?
I come to realize my questionning is not really about git but it's more
about how to actually work as a team...
Le mercredi 7 mai 2014 07:35:28 UTC+3, Magnus Therning a écrit :
> On Tue, May 06, 2014 at 02:59:45PM -0700, Jeremy Belolo wrote:
> > Hello all !
> > I started using git 1 year ago. At the beginning I tried to work
> > with it on my local env on windows, and I would push the changes to
> > the dev server when ready. But I came across countless issues.
> What git issues did you come across?
> > So I tried something else. Using Virtualbox to create a virtual
> > Ubuntu that I used to work. I was able to access files and edit them
> > on Windows, and the versionning was great.
> > But the connectivity gave me headaches. Plus, there is a big
> > downside, the site I was working on used Paypal IPN, which calls an
> > arbitrary script on your server to send results of transactions.
> > Unable to reach my local PC, or the VM, this side of things was very
> > difficult to test. No need to say this was a huge problem.
> > So I moved on and created a subdomain. There already was mysite.com
> > and dev.mysite.com on the server. I added jer.mysite.com for me,
> > dan.mysite.com for another dev, ext.mysite.com for external services
> > working with us, and so on... Then cloned dev.mysite.com in every
> > one of those.
> > This works nice. Everyone got his own environnment on the server
> > directly, every external scripts such as Paypal's or Facebook's
> > works without any issue. We worked like this for many months now.
> > What I'm not very satisfied about, is the concept. Working like this
> > forces to use the main server, the production server, directly for
> > development purpose. Not only it could be a real problem if your
> > team grows to include 20, 30 developers, but it also cause
> > unnecessary server load. A dev testing a consuming script could
> > really slow down the production site... Which is not acceptable.
> > So, what would you guys recommend ?
> I am confused. Probably I just don't understand you, but it does
> sound like the choice of VCS is completely unrelated to your headaches
> with connectivity. The issue at hand is that in order to test your
> code Paypal IPN performs a callback, and therefore needs to be able to
> reach the machine you are running the tests on, i.e. your dev machine
> has to be exposed to the internet in order for the tests to pass. No?
> Magnus Therning OpenPGP: 0xAB4DFBA4
> twitter: magthe http://therning.org/magnus
> Goto labels should be left-aligned in all caps and should include the
> programmer's name, home phone number, and credit card number.
> -- Abdul Nizar
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.