Closed Bug 272268 Opened 20 years ago Closed 20 years ago

set up developer.mozilla.org

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: fantasai.bugs, Assigned: myk)

References

Details

devmo is ready to be taking submissions, and there are some documents on other
sites and www.mozilla.org that should be moved over. However, we can't in good
conscience move anything to devmo until devmo is at developer.mozilla.org.

What needs to be done:
  - DevMo needs to be on an Apache 2.0 server. This is because we're setting up
    to do language negotiation, and it will break without certain settings that
    are only available in 2.0. So it needs to be moved from rheet.
  - DevMo needs the following rules added to its config file:
      AddDefaultCharset UTF-8
      LanguagePriority en
      ForceLanguagePriority Prefer Fallback
  - DNS needs to be changed so that developer.mozilla.org serves up the same
    thing as developer-test.mozilla.org.

The template in use at http://developer-test.mozilla.org/ doesn't quite match
the rest of mozilla.org. If this needs to be changed before we switch DNS, I can
change it. It would probably be a good idea for me to test the language
negotiation settings before we switch, too.
OK, adding Apache 2 as a requirement makes this a little more difficult to
fulfill.  All of our current machines with Apache2 on them are already running
high-bandwidth services that preclude adding anything else to those servers. 
Barring the sudden arrival of new servers (there are some things in the pipe,
but nothing is on hand yet), that makes this stalled on getting one or more of
the existing servers upgraded.
I think we need to get this up sooner rather than later, so, since we only have
English content right now, what we can do is

  - Remove the AddLanguage directive that binds .en to English so our files won't
    be tagged as having a language that can be rejected. (This is probably part of
    the default config somewhere.)
  - Add the AddDefaultCharset directive for UTF-8.
  - Switch over DNS.
  - Worry about proper language headers later.

Is that doable?
(In reply to comment #2)
> Is that doable?

Yes, with those changes, it can stay right where it is now and we'll just point
the domain name at it.
Blocks: 261101
Blocks: 245954
What's the status on this?
Now that licensing is sorted out, I cannot really do much else until this gets
fixed. If there are confidential marketing/pr/management-related reasons why you
don't want devmo-test linked from the main site, that's fine. Keep
http://www.mozilla.org/developer linked from the main site and don't announce
the DNS switch. But as of right now, this is a blocker for moving content over
because I cannot in good conscience move documents from their current stable
locations to what is effectively a temporary site. We already have people using
the XPCOM reference from "developer-test.mozilla.org" and I do /not/ want to
continue this trend.
Severity: normal → blocker
OK, it's live.  Sorry for the delay.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Thanks, Dave. Could you also remove the .en -> English mapping so that content
doesn't get blocked when I leave English out of my preferred-languages list?
ok, just for the record, the english language definition is back in, and the
site now lives on an apache2 server, so all the goodies work as intended.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.