We have a basic site setup for the areweslimyet.com domain, and need a place to host it. Right now the site is running on a nginx daemon on albus.mv.mozilla.com, and doesn't require any serverside CGI. Arewefastyet.com is another domain that is setup similar to this, though I'm unclear on the details. If we could get the domain setup to simply point at albus via a firewall rule or proxypass, that would be ideal - otherwise we'd need at least the ability to do automated rsync's to whatever server it ends up living on. jrmuizel has the registration for areweslimyet.com, CC'd The site is currently accessible on albus here, albeit a slightly out of date version: http://albus.mv.mozilla.com:8000/
This looks like an IT bug that was file without the IT bug form, and thus in the wrong place. Moving to the IT bug queue.
Assignee: nobody → server-ops
Component: Operations → Server Operations
Product: Mozilla Services → mozilla.org
QA Contact: operations → cshields
Version: unspecified → other
Can we get a rough eta on getting this set up?
Where is the code for the website located? We don't own that domain - will need transferred to us first.. Who owns it? (fwiw, we are not hosting any of the other meta domains internally - happy to do this one but it needs to be internalized first, infrasec review, etc)
Component: Server Operations → Server Operations: Web Operations
Jeff Muizelaar owns the domain.
This doesn't need to be hosted "internally" per se, we just need a place to put this code. As long as it's on a publicly routeable static ip we're good, but no need to be in any sensitive networks or whatever. How are we hosting arewefastyet.com? Is Mozilla IT involved in that one at all?
awfy is on a server shaver setup for me - I think it was through IT, and I think it is a VM on rackspace. the domain is owned by me so I just point it there.
(In reply to David Anderson [:dvander] from comment #6) > awfy is on a server shaver setup for me - I think it was through IT, and I > think it is a VM on rackspace. the domain is owned by me so I just point it > there. Ah ha. If that's the case, I could probably spin up something there and give access to Johnny to set things up. Would that be acceptable? Also, Corey, ack?
Yeah, that should be fine, except give John Schoenick access instead of me (or in addition).
Or maybe this can even live on the same VM as awfy? Either way is fine with me...
(In reply to Johnny Stenback (:jst, firstname.lastname@example.org) from comment #9) > Or maybe this can even live on the same VM as awfy? Either way is fine with > me... this would be the cheaper route.. and much better from my opinion, but at any rate we don't run that VM so you'd have to talk to dvander for that.
It seems easier and less risky to use separate VMs. Esp. since awfy is just plopped into root folders, someone would have to separate it out into virtual hosts or something. Sounds like a pain :) but if another VM is prohibitively expensive or something, let me know and I'll make an account on the box.
Its the pain of setting up 2 virtual hosts versus paying monthly for VMs to host meta sites? Again, we don't run those so we can't force you to set it up and share.. but if this is going to be a trend we need to bring this in house and internalize these sites if we are going to spend more money on them.
Would it be a possibility to setup a public IP for the albus machine so it could just be hosted there? This site is going to be static and probably very low traffic. Otherwise I'm tempted to just host it externally, since it seems silly to go through the full infrasec review/etc for internalizing these things when they're really just engineering-maintained stats pages.
(In reply to David Anderson [:dvander] from comment #11) > It seems easier and less risky to use separate VMs. Esp. since awfy is just > plopped into root folders, someone would have to separate it out into > virtual hosts or something. Sounds like a pain :) but if another VM is > prohibitively expensive or something, let me know and I'll make an account > on the box. David, in the long run it is pretty expensive for such low traffic sites. Feel free to create and account for John, if you guys need any apache help etc, either me or someone from the webops team will be happy to help.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Alright, this is going to be setup either externally or on an existing VM. I'm marking this as resolved, those CC'd for the status of this site can follow Bug 704646
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.