Re: [oll-user] Call for initial feedback
Resources for LilyPond and LaTeX users writing (about) music
Status: Alpha
Brought to you by:
u-li-1973
From: Janek W. <lem...@gm...> - 2013-03-20 16:12:21
|
2013/3/20 Urs Liska <ul...@op...> > the website content is in a dedicated directory within the openLilyLib > repository. (you can browse that in the "Code" area of openLilyLib, the > directory is 'project-web'. > AFAICS one can't use Git to manage the project web space (which is a pity > if it's true). > So the work-flow is: Make changes to the content (or the templates or the > css ...), commit and push them to the openLilyLib repo and upload them to > the web space with rsync. > It's conceptionally a little bit awkward but works quite smoothly. > ah, ok. > I like tinkering with git and i think i could learn how to merge > repositories. However, maybe git submodules would be a correct answer? A > submodule is just a repository inside another repository, so that we could > have a big repo containing all projects, while all of them would remain to > be separate repos. > I don't know how well that plays with SourceForge, however. > > Hm, for some reason I don't really know I'm 'scared' by Git submodules. > The documentation on SourceForge doesn't mention submodules, but I don't > know if there are special needs for that on the server. > I think I will look in the official Git docs and get a better idea what > submodules really are. > I have a bit of experience with them and they seem to be pretty straightforward. I was even able to debug a corrupted git repository which contained a submodule, as you can see here: http://stackoverflow.com/questions/14797978/git-recovery-object-file-is-empty-how-to-recreate-trees (that was really awesome! I felt like a pro when i had finished ;-) ) best, Janek -------------- next part -------------- An HTML attachment was scrubbed... |