[GenABEL-dev] web-server todo's

[L.C. Karssen]

Hi all,

One of the things that I think needs to be done before "public release"
is to change some DNS settings. This would take 10-15 minutes. 
Right now only forum.genabel.org is working as expected. For the website
(Drupal) we have www.genabel.org planned, right? 
I think that for consistency we should also set the correct DNS entries
for genabel.com and genabel.net.

Furthermore, do we want to point devel.genabel.* and/or dev.genabel.* to
https://r-forge.r-project.org/projects/genabel/ ?
And how about 
man.genabel.* -> http://test.genabel.org/drupal6/?q=manuals
doc.genabel.* -> idem dito

Any other suggestions?

I added some notes below as well.

On Fri, 2011-02-11 at 20:44 +0700, Yurii Aulchenko wrote:
> I am sending a short description of web-server todo's to keep things documented
> 

> Here are the things we need to do about web-server (add more and join
> into discussion :) )
> 
> * Solve links (will tell more about that below)

Also see below.

We should also check the links for absolute references to
http://test.genabel.org/drupal6/etc. I suggest to make all links
relative: <a href="/drupal6/etc">link</a>. 
To automate this we could try to think of a search/replace action on the
Drupal database (after a backup of course :-)).

Furthermore, we can configure the web server to "strip" the /drupal6/
part as well. The URL of the pages will then be like this:
www.genabel.org/?q=acknowledgements 

> 
> * Solve HTML documentation (will tell more about that below)
> 
> * Ask PredictA and ParallA developers to generate HTML -- this will be
> handy if they include this bit as a part of their package update
> process (Yurii) We will also need to write instructions on how to do
> that and put @developers' pages (other primary link at
> www.genabel.org? R-forge?)
> 
> * Check integrity -- all links work, and bring to right place

I came across a Firefox extension that can validate the links on a page.
It gives a visual indication (green/red links) for each link on a page
which shows if the links points to an existing page. What it doesn't do,
of course, is check whether the link goes to the intended place. That
requires human intelligence, I'd say. However it doesn't give some sort
of aggregated output, you'll have to visit each page and run the link
checker. On the other hand, it beats going over the HTML code by
hand :-). 
The URL of the extension is
http://www.kevinfreitas.net/extensions/linkchecker/



> * Replace MGA *ABEL pages with something, which re-directs the traffic
> to www.genabel.org

This depends a bit on the level of access that you have on MGA. IIRC you
have the files in your ~/public_html dir, right? There are a couple of
ways to redirect pages. If the sysadmin of MGA has Apache's mod_rewrite
enabled we can use that. See e.g.
http://www.stevenhargrove.com/redirect-web-pages/#301modrewrite for an
example.

Otherwise the .htaccess file can be used. See e.g.
http://www.stevenhargrove.com/redirect-web-pages/#301htaccess for an
example.

Steven Hargrove's page lists a few more examples. 



Lennart.

> 
> * Announce (forum, mail-list, social networks)
> 
> Now some more details about 'problems'
> 
> (*) Solve links
> 
> Primary links look like http://test.genabel.org/drupal6/?q=node/6
> (this is to Packages section). Can we have something more
> human-readable? I believe Lennart figured what module we need to
> enable, but doing so was not so trivial...
> 
> (*) Solve HTML documentation
> 
> We need to keep HTML documentation for packages, and eventually
> update, keeping the link stable.
> 
> This is a bad one, though there is workaround. What we have figured
> out with Lennart about htmlimport module, is that if you import html
> pages (e.g. from dir http://test.genabel.org/old/htmlMetA/), the
> delete it in drupal, and then try to import again, it will not work.
> So now trying to import http://test.genabel.org/old/htmlMetA/
> generates crap, and that's it. The workaround is to say rename
> htmlMetA to say htmlMetA1, then import, -- it will work. But! It will
> bring htmlMetA1 into the link's name, so the link to 'updated' version
> changes!
> 
> So, for the moment I just put all docs to http://test.genabel.org/old/
> and make links to there. It is kind of ok, but two problems here I
> believe: (a) search engines will eventually index 'old', and people
> will land @ old without noticing we have this beautiful web-site :)
> (b) just esthetically would prefer to see docs appearing "within"
> drupal frame, see example
> 
> in old: http://test.genabel.org/old/htmlDatA/00Index.html
> 
> how it should be:
> http://test.genabel.org/drupal6/?q=htmlDatA/00Index, and it should be
> linked from http://test.genabel.org/drupal6/?q=node/84
> 
> I wonder -- if you just try to import updated page, without prior
> delete of pages to be updated, would that work just fine solving the
> problem?
> 
> If nothing works, would that be reason good enough to try other CMS or
> even go to very simple plain HTML site?...
> 
> best wishes,
> Yurii
> _______________________________________________
> genabel-devel mailing list
> genabel-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel

-- 
-----------------------------------------------
L.C. Karssen
Erasmus MC
Department of Epidemiology
Room Ee2224

Postbus 2040
3000 CA Rotterdam
The Netherlands

phone: +31-10-7044217
fax: +31-10-7044657
email: l.karssen at erasmusmc.nl
GPG key ID: 0E1D39E3
-----------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.r-forge.r-project.org/pipermail/genabel-devel/attachments/20110307/d2a74463/attachment.pgp>