613051 - bugzilla instance for bugs.ecmascript.org

Status: RESOLVED FIXED

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

Description

[Dave Herman [:dherman]]

We'd like to create a fresh bugzilla instance for ecmascript.org's issue tracking. In the past, we had a brittle Trac instance; it's unmaintainable and currently broken. We won't worry about migrating the old Trac issues into the bugzilla.

Once this is up and running I can switch over the DNS for bugs.ecmascript.org to point to the new bugzilla instance.

Thanks,
Dave

Comment 1

[Dave Miller [:justdave] ([e-mail])]

OK, I'm putting this on your cg-ecmascript01 box.  It'll live at /var/www/bugzilla and you'll have a local mysql database server on the box for it.  You're welcome to maintain it yourself but if you need help with an upgrade or something feel free to file a bug for assistance with it.

All of the prerequisites have been installed, and I checked out the code from the bzr repo, so pulling future updates from upstream should be as easy as:
bzr pull --overwrite; ./checksetup.pl

You've got the current tip of the 4.0 branch (which is almost in release candidate phase at this point).

And I got to this point and discovered you have nginx on the box instead of apache...  In theory it still ought to work, but I'm not quite sure how, that's a bit out of my expertise.

Comment 2

[Dave Miller [:justdave] ([e-mail])]

Let me know how you'd like to proceed from here.  Since you guys have root you're welcome to finish the setup if you know how to do the nginx part.  The hard part of the setup is done (all the prereqs are installed and the database is set up). The admin user is [e-mail].  You should be able to use the password reset on that username to get in once you get the webserver talking to it.

If we want to go some other direction with this, let me know.

Comment 3

[Dave Herman [:dherman]]

In theory I'm able to configure nginx but I've never done a bugzilla setup. If you could point me to instructions on how to configure Apache for bugzilla, I can see if it looks feasible for me to translate that to nginx. But I might end up needing help.

Thanks,
Dave

Comment 4

[Dave Miller [:justdave] ([e-mail])]

http://www.bugzilla.org/docs/4.0/en/html/configuration.html#http-apache-mod_cgi

I also found this via Google... might be useful.
http://www.webopius.com/content/231/how-to-get-bugzilla-working-with-the-nginx-web-server

Comment 5

[Shyam Mani [:fox2mike]]

Dave,

So I spoke with Dave (Herman) about this, and they're okay with going ahead with Apache.

I've setup a test domain bugs-test.ecmascript.org and pointed it at cg-ecmascript01. Once the DNS changes kick in (it's external, not managed by us), you can go ahead and tweak the apache config to check if everything is working and dherman will then switch over DNS for bugs.es.org when he sees fit.

Sounds good?

Comment 6

[Dave Herman [:dherman]]

Would you mind also configuring a virtual host for test262.ecmascript.org that gets static files from /var/www/test262/www ? It's all static files, so doesn't need anything fancy. Currently the only subdomains using this server are test262, bugs, and bugs-test.

Thanks,
Dave

Comment 7

[David Fugate]

Think these changes might have just blown up http://test262.ecmascript.org?  The test262 page has disappeared, and been replaced by a subset of the content found on http://hg.ecmascript.org.  If this is related to the recent changes could you please fix this ASAP?

Thanks!

Dave

Comment 8

[Dave Miller [:justdave] ([e-mail])]

I haven't touched the machine yet since November 25th.

What do you have running on nginx currently?  Do I need to preserve that/migrate it to apache?  If so, what is it supposed to be serving, so I can make sure it works after I move it?

Comment 9

[David Fugate]

Something has definitely changed since last Thursday when I ran a full test pass against the website.  I SSH'ed into test262.ecmascript.org a few moments ago, and here's what I see:
  [dfugate@cg-ecmascript01 www]$ pwd
  /var/www/test262/www
  [dfugate@cg-ecmascript01 www]$ dir
  browsersreport.html  enginereports  old            specifications.html
  default.html         favicon.ico    projects.html  staging
  ecmascripthome.html  index.html     resources      tc39.html
  [dfugate@cg-ecmascript01 www]$ pwd
  /var/www/test262/www
  [dfugate@cg-ecmascript01 www]$ echo $HOSTNAME
  cg-ecmascript01.sj.mozilla.com
  [dfugate@cg-ecmascript01 www]$ ls
  browsersreport.html  enginereports  old            specifications.html
  default.html         favicon.ico    projects.html  staging
  ecmascripthome.html  index.html     resources      tc39.html
but http://test262.ecmascript.org doesn't give me access to any of these files.

Have no idea about nginx (no root access).  All I'm certain of is http://test262.ecmascript.org should correspond to what's currently /var/www/test262/www/index.html on test262.

Comment 10

[Shyam Mani [:fox2mike]]

(In reply to comment #7)
> Think these changes might have just blown up http://test262.ecmascript.org? 
> The test262 page has disappeared, and been replaced by a subset of the content
> found on http://hg.ecmascript.org.  If this is related to the recent changes
> could you please fix this ASAP?


Fixed. I had stopped nginx and kicked off apache to setup bugzilla.

Moving forward, I'm not going to make *any* changes on this box.

Comment 11

[Dave Herman [:dherman]]

> What do you have running on nginx currently?  Do I need to preserve
> that/migrate it to apache?  If so, what is it supposed to be serving, so I can
> make sure it works after I move it?

Sorry, somehow I missed this question. Here's what we need for the moment:

- a virtual host for bugs.ecmascript.org and bugs-test.ecmascript.org for the bugzilla instance
- a virtual host for test262.ecmascript.org that reads its static files from /var/www/test262/www

Once this is set up, we can stop nginx and switch to running only Apache.

(A bit further down the road I would like to create a password-protected staging subdomain, but I can file a separate bug for that.)

Thanks,
Dave

Comment 12

[Dave Herman [:dherman]]

PS There's pretty much nothing you need to worry about copying from the nginx setup -- it's completely vanilla, just static files. You can find the relevant conf files at /opt/nginx/conf/nginx.conf and /opt/nginx/sites-enabled/test262.ecmascript.org but there's nothing at all interesting about them.

Comment 13

[Dave Herman [:dherman]]

justdave: Do you need anything else from me? Would it be possible to get this up and running soon?

Thanks,
Dave

Comment 14

[Dave Miller [:justdave] ([e-mail])]

I have everything I need, just waiting for a chance to actually do it.  I apologize for the delay, I was out at the begining of the month and I'm still playing catch-up.  More than likely I will have this done sometime this weekend.

Comment 15

[Dave Herman [:dherman]]

Sorry to be a pest but we're blocking a number of partners on the committee and in the community -- can we get this done soon?

Thanks,
Dave

Comment 16

[Dave Miller [:justdave] ([e-mail])]

OK, this is up and running. You guys apparently have DNS pointing somewhere else right now (and wherever it's pointing is broken - which confused me for a bit because I thought I didn't have it set up right).  So you'll need to changed DNS for it to actually be usable.

I got all the stuff that was in nginx ported over to apache.

It's got a self-signed certificate on the https.