Google App Engine and Git best practices

Posted by systempuntoout on Stack Overflow See other posts from Stack Overflow or by systempuntoout
Published on 2010-05-27T08:25:21Z Indexed on 2010/05/28 18:22 UTC
Read the original article Hit count: 360

I'm developing a small pet project on Google App Engine and i would like to keep code under source control using github; this will allow a friend of mine to checkout and modify the sources.

I just have a directory with all sources (call it PetProject) and Google App Engine development server points to that directory.

Is it correct to create a repo directly from PetProject directory or is it preferable to create a second directory mirroring the develop PetProject directory? In the latter case, anytime my friend will release something new, i need to pull fetch from Git copying the modified files to the develop PetProject directory.

If i decide to keep the repo inside the develop directory, skipping .git on Gae yaml is enough?

What are the best practices here?

© Stack Overflow or respective owner

Related posts about best-practices

Related posts about git