Closed (fixed)
Project:
Drupal.org infrastructure
Component:
Servers
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
17 Feb 2009 at 18:42 UTC
Updated:
21 Aug 2014 at 21:00 UTC
Jump to comment: Most recent
In the D5 version of d.o, in the document root, there's a "release-history" directory with its own .htaccess file. While importing this stuff into SVN to deploy on d6.d.o, davidstrauss recommended we just handle it directly via the root .htaccess file.
This is a critical task before the upgrade so we can test that update_status still works.
I'm not much of a .htaccess hacker, so I'll work on this, but I'll need some help to make sure I don't break anything. ;)
Comments
Comment #1
dwwThe way it currently works on d.o is there's a "release-history" directory in the document root with a symlink to the real project-release-server-history.php file, and the following .htaccess:
The idea is to put this logic directly into the root .htaccess file and don't bother with the release-history subdir at all. However, I don't understand mod_rewrite voodoo enough to make this work. ;) This isn't working on my test site:
the .htaccess is clearly being used, and rewriting works, but when I try to visit:
[site]/release-history/drupal
I just get a 403:
"You don't have permission to access /release-history/drupal on this server."
Help? ;)
Comment #2
dwwAfter further consideration in IRC, we decide it was better still to move updates.d.o into its own webroot. This avoids the release-history subdir hack from d.o's webroot entirely, and solves the problem of google indexing, etc, since updates.d.o will no longer be a full-blown copy of d.o, but its very own site. So, we're going to set all this up right now and test it, so we can have this as a separate site before the d.o upgrade itself tomorrow morning.
Comment #3
dwwhttps://svn.drupal.org/drupal/updates.drupal.org/trunk now contains everything we need for this site. I've checked that out to /var/www/updates.drupal.org/htdocs on www1. If anyone else wants to test, here's how:
1) Put this in /etc/hosts:
2) Put this in settings.php:
Currently, updates2.d.o is pointing to /var/www/updates.drupal.org/htdocs for its webroot.
Personally, I think we're ready to pull the trigger to change the webroot for updates.d.o itself, but I'd be happy to hear someone else tried to break it and couldn't. ;)
Thanks!
-Derek
Comment #4
dwwNote: if you're testing on D5, you want this in settings.php instead:
(and you still need to tweak your copy of /etc/hosts)
Comment #5
alex_b commentedJust tested with Drupal 6.8. I got a valid response from the server. I can see suggested updates for Drupal, Coder, Devel and Views on admin/reports/updates .
Comment #6
crashtest_ commentedAlso works great on both of my installs, a 6.9 installation and on a 5.12.
Comment #7
dwwThis is now live.
Comment #8
jcmarco commentedI have this links for the modules updates links:
http://drupal.org/var/www/drupal.org/project/scripts/project/drupal
Comment #9
dwwThat bug's actually separate from this move -- it's due to the D6 port.
See #376550: Available Updates Links Broken about fixing this.
Comment #11
nnewton commentedRe-opening this as we have discussed before to work on converting this webroot from PHP based serving to Apache/Rewrite-based.
-N
Comment #12
nnewton commentedThe main issue with rewrite is that I don't particularly like rewrites that cross docroots. However, the PHP script already crosses docroots, so I'm willing to set that aside for now. Could we write this with a symlink though? This would allow us to at some point have a jenkins job drop release-history in the updates docroot itself.
-N
Comment #13
eliza411 commentedClosing old issues. Please re-open if needed.