|
Hi all, I'm certainly not an authority in this field, but willing to change our tools (SVN, mercurial, Drupal or whatever), a few weeks before the event is not really a bright idea in my point of view. We already spent weeks doing the actual LGM2011 website, and even if it's not prefect, it do the job. In the best scenario , trying to restart everything again now will only conduct to a beta quality website two weeks before the event. Furthermore, using a revision control system is not ideal because it increase complexity, and forbid quick testing in the production environment (it's easy to make a typo mistake in a _javascript_ file for example). Drupal is a good CMS, but we will need time to set it up fully, so it will be wiser to use it for next year. Said simply, as already said by a number fo people here, let's focus on next tasks instead of re-doing the same ones again and again. Cheers, Camille Le 20/03/2011 22:32, a.l.e a écrit : ciao yuval,On March 18, 2011 07:57:25 pm a.l.e wrote:the content is managed in a wiki form and is stored in a database.the source control architecture would not back up the database itself, only the code to generate it and access it. however you don't need SSH to access a wiki/database from the html front end?the access to the server is only need to modify the forms and the templates.for forms and templates it would work. i have set up recently a mercurial over https configuration. it boils down to adding users in the .htaccess file, no SSH access required (which I understand is what you are wary about?).personally, i haven't yet used mercurial yet (nor git; i still normally use svn, which is not ok to publish a website).Why do you state that SVN is not OK to publish a website? Hugin moved to Mercurial only a year ago. Prior to that it was in SVN. The website too. And it worked well.it's not really practical to put a svn check out on a webserver: it's polluted with .svn directories...let's see how we will manage the site next year... i think that we will give up with anwiki. mercurial could then be a way to manage it!I don't know the site's architecture. I do know that before giving up a tool I would want to have a comprehensive look at what works and what not, and make sure that the change of tool is not just for the sake of changing tool.we are changing now for drupal. the new site will be up as soon as possible. i hope we won't have to change again next year! not sure if it's worth to put a drupal instance in a revision system... we will see. ciao a.l.e _______________________________________________ CREATE mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/create |
_______________________________________________ CREATE mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/create
