eZ Community » Forums » Developer » git life-cycle, development to...
expandshrink

git life-cycle, development to production

git life-cycle, development to production

Tuesday 10 August 2010 4:49:02 am - 6 replies

I'm interested to learn how other developers use git in their working environment. I've recently made the move from svn to git so am in the process of reassessing the best ways to work with code from development to testing and finally live.

Using the git archive command would be an option as would be rsync. I could also just run a git clone in each environment which is probably the best solution with easier ability to individualise each .gitignore per instance.

Also do you generally put the entire ez publish file structure into git for simplicity or do you set-up your ignore file to exclude it?

Love to hear others experiences and suggestions.

Tuesday 10 August 2010 9:42:21 pm

I really don't like github, I think svn+tortoise svn is much more easy to use then github + that beta github windows tool. The only one feature I liked about github is that I can search a repo, fork and edit it online, but when I hade to download a repo to my computer, edit and then upload I have some problems.

I hade several problems trying to create and maintain two or more repo, because when I tried to upload my local files to a repo I got an error, some key problem thing....

Github will be great only if it be as easy to use as svn+tortoise...

About ez publish versioned folders, I think it could be like svn, only extension, settings, and var/yoursite/storage folder, maybe design folder.

Modified on Tuesday 10 August 2010 9:50:19 pm by Thiago Campos Viana

Tuesday 01 March 2011 3:45:39 pm

I'm pretty much interested by this topic too.

I want to store that in a single remote (origin), and fetch updates from the upstream (ezpublish git repo).
What is the best way to do?

Because what I need:

  • adding/modifiying files at the root folder of eZ Publish (custom .gitignore, fabric config files etc.)
  • adding my own extensions, project specific: submodules (same repo with other branches or specific repo) or plain files within extensions/ folder?
  • if possible, not publishing the entire history of the upstream on origin, but only changes from the time the project is initiated

For the last point, I created my project, added origin, added upstream, rebased upstream and commited.
However, once I want to clone, I encounter a git packing error, as I have not commited the past history, but only the current snapshot.

Any clue? Any strategy?

Thanks happy.gif Emoticon

Tuesday 01 March 2011 4:17:29 pm

Hi Thomas,

The draft version of the "How to contribute to eZ Publish using GIT" is linked to from there. The final version should be published in a matter of days.

Also, another application of GIT/github and eZ Publish contribution, int he frame of localization, is presented in the following tutorial : http://share.ez.no/learn/ez-publi...ting-localizing-ez-publish-using-git

Stay tuned for the full version of the former,
I hope this helped,
Cheers,

Wednesday 02 March 2011 3:43:02 pm

Hi Thomas,

The draft version of the "How to contribute to eZ Publish using GIT" is linked to from there. The final version should be published in a matter of days.

Also, another application of GIT/github and eZ Publish contribution, int he frame of localization, is presented in the following tutorial : http://share.ez.no/learn/ez-publi...ting-localizing-ez-publish-using-git

Stay tuned for the full version of the former,
I hope this helped,
Cheers,

Hello,

thanks for your reply but unfortunately, I can't see how it could help me during my daily dev on my projects.
What I would like is to fetch changes of eZ, like patches, without pushing the whole eZ history on my own remote.

Thanks

Wednesday 02 March 2011 11:56:44 pm

thanks for your reply but unfortunately, I can't see how it could help me during my daily dev on my projects.
What I would like is to fetch changes of eZ, like patches, without pushing the whole eZ history on my own remote.

Hello Thomas,

I will have to leave this question to better GIT experts than i am, i am afraid.

Cheers,

Saturday 22 October 2011 4:50:34 am

It's been a while since eZ Systems switched to hosting eZ Publish and certified extensions on Git.  After trawling the interwebs for an answer, I'm wondering how ezp developers are setting up their code repositories for projects and libraries, whilst drawing on these GitHub repos.  

SVN code libraries tend to be monolithic, whereas Git ones seem to be broken down into individual repos for components.

So how to put this all together and put together a Git project which pulls in various code libraries extensions etc?

There seems to be 2 solutions:

  1. Submodules - only allows inclusion of entire project, so hopeless for ezp extensions which have a build system, but potentially good for structuring a code library or individual git repos?
  2. Subtree merge - using merge & read tree on remotes, which would probably work at a web project level

I'm only a Git beginner, but I want to get this right to maximise code re-use.  Any experienced hands out there who can offer some advice?

Cheers in advance,
Geoff 

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from