Closed Bug 840816 Opened 13 years ago Closed 13 years ago

[Verbatim] Dev DNS entry for Verbatim

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: peterbe, Assigned: nmaul)

References

Details

After a lot of discussion we (jakem, Milos, myself) decided the best thing would be to set up a dev instance on the same server as the current production verbatim. We'll change to a local mysql and try not to pollute the memcache server and we'll set up dev repos for SVN. First of all, we need a DNS entry. Something like verbatim-dev.allizom.org to point to the same as https://localize.mozilla.org/
You L10n folks might have a different opinion about what the dev DNS entry should be. Ie. should it be "localize-dev.allizom.org" or "verbatim-dev.allizom.org"
I've already set up localize.allizom.org pointing to the appropriate IP. You can reach it now... it should 404 until the app is set up there. localize-dev.allizom.org is similarly configured, although it does not have a separate Apache config. Right now it's falling back to the primary one (localize.mozilla.org)... but it could easily be divorced from that and set up just like localize.allizom.org. I didn't, because it seemed unnecessary... for this purpose I think one extra environment will do fine. Going to mark this as resolved, but feel free to re-open if there's a problem or change needed.
Assignee: server-ops-webops → nmaul
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
DNS name is cool, thanks.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.