|
[
Permalink
| « Hide
]
Anthony Borrow added a comment - 19/Aug/09 05:43 AM
Adding MD, ML, and Mihai as watchers so they can weigh in ... the plan is to create a patch in CONTRIB for paintweb for Moodle 1.9 and for 2.0 to add it to core. Peace - Anthony
if the code is still under development it should go on test.moodle.org, if its stable & ready for public viewing it should probably go on demo.moodle.org
Let me know which and il do it asap Jordan - The code is still under development and will need an occasional update so I think it best to add it to test.moodle.org. Peace - Anthony
Is the code anywhere in contrib cvs? test.moodle.org has an automated web interface for installing new sites & plugins.. the whole process can be done by any dev from a browser that way
Jordan - No the code is not in contrib as it is hoped that the 2.0 code will go straight into core's HEAD. ML and Mihai have been using GIT and I suspect were hoping to be able to continue to do so. Unfortunately I do not know enough about GIT to be helpful here so perhaps ML or Mihai may have a few ideas about how to set this up so that it can easily be updated. I am interested in the new interface - where can it be found? Does it also allow for the removal of those sites when testing finishes? Peace - Anthony
Well, there are definitely tools to make cvs-git migration easier, but I am also a "beginner" with git myself - which means I cannot make any recommendations myself, having no experience with such tools. I started using git only this summer at the suggestion of MartinL.
Mihai - Perhaps it would be helpful if you could give an idea of how often you want the site updated. If you could live with something like a daily update then we should be able to fairly easily automate it with a cron job that gets the latest code from the git repository. This allows you to continue to work with GIT and would prevent any manual intervention. Does that sound reasonable? Peace - Anthony
Anthony - yes, that's reasonable. For me it's OK even if the site is updated every two days or so. I don't want to put much strain on the server.
Mihai - I don't think a daily update would be too much and it keeps it regular enough that if there is a major change it will be available within 24 hours. Plus I think daily stuff is easier to setup. Peace - Anthony
Hi Jordan,
Just wondering how things are going with setting up a test.moodle.org site for Mihai's paintweb project? Do you have everything you need? Those instructions don't seem to result in a full version of Moodle. Can you provide entire instructions for setting this up using git? (we don't use git here)
MartinD: If you do git checkout mdl20-paintweb you will actually get the entire Moodle 2.0 codebase + PaintWeb integrated.
The full instructions to get the code from the git repo onto your disk are those provided: git clone git://repo.or.cz/moodle/mihaisucan.git ~/public_html/moodle-paintweb execute that on a Linux/Mac/Windows where you have git installed. You will end up with the moodle-paintweb folder containing the entire Moodle 2.0 codebase (the snapshot I based my work on) + PaintWeb integrated and fully functional. I should note that at times I rebase my patches on the latest Moodle 2.0 codebase. When you want to update the folder from the online git repo you only do: Done. OK I have checked it out but I get the following error when trying a 'git pull'
fatal: 'origin': unable to chdir or not a git archive Hey Jordan, thanks for trying this.
Git pull works for me. I use git version 1.6.0.4, the default git package on Ubuntu 9.04. Here's what I executed, and my results: robod@athlon:~% git clone git://repo.or.cz/moodle/mihaisucan.git ~/testgit robod@athlon:~% cd ~/testgit
From the above you can see that git clone warns there's no HEAD branch, thus when I go into the folder ls shows nothing. The "git branch" command shows the branches I did checkout locally. "git branch -r" shows me the remote branches. Checkout for the mdl20-paintweb branch worked fine for me - doing a "ls" shows me all the correct files. Next, I ran "git branch" just to make sure the branch shows up. Lastly, I ran "git pull" to check for updates - which worked for me. I am unsure what could be affecting your git pull. Network connection issues? [root@server8 paintweb]# git branch
I searched on Google for the error message and I saw it might be related to the folder being a symlink. Is the "paintweb" folder a symlink?
No the folder is not a symlink
 I am attaching a patch file which can be applied to the Moodle 2.0 development branch (cvshead). The patch includes binary content as well. To apply the patch please use:
git apply --binary mdl20-paintweb-full.patch Jordan: what Git version do you use? What OS? Are you trying to checkout the code on a network-mounted folder? Please provide more details. I never got that error. Does anyone else get this error? Just to add that I tried steps mentioned by Mihai in the 03/Sep/09 05:45 PM post without incident. It seems to have worked just fine for me with git 1.6.0.4. Peace - Anthony
this is Red Hat Enterprise Linux 5.3 with git 1.5.2.1
There is nothing special about the directory, its not network and its not symlink Mihai, I think it would be faster if we communicated via the jabber dev chat - please drop in at your convenience Thanks Jordan for your time. I believe your git version is too old. I don't know git for too long, so I don't know any workaround.
Anyhow, Jordan has been really kind and had the test site installed and configured for me. The test site is now available at: http://test.moodle.org/paintweb/ User is: user. Password is: demo. Enjoy! Thanks Mihai, I'm just making a few small improvements to your Paintweb test site, including creating a test user with username and password 'test', so that it's the same as our other test sites.
closing for now, re-open if required.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Task
Closed
Major
Create test site for GSOC PaintWeb project on test.moodle.org
 |
|
