Closed Bug 1084562 Opened 11 years ago Closed 11 years ago

Deploy staging server for mozillafordevelopment/webmaker-app-publisher

Categories

(Webmaker Graveyard :: DevOps, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kate, Assigned: johns)

Details

Repo: https://github.com/mozillafordevelopment/webmaker-app-publisher This app needs an s3 bucket configured to publish with it. After the bucket is made, we need to commit the name, region and URL at which it can be accessed (preferably through cloudfront -- maybe apps.mofodev.net) here: https://github.com/mozillafordevelopment/webmaker-app-publisher/blob/master/config/staging.env Secret keys which can't be committed include: # Login secret key SECRET_KEY= # Makedrive endpoint # e.g. http://testuser:password@makedrive.mofodev.net MAKEDRIVE_ENDPOINT_WITH_AUTH= # AWS credentials ACCESS_KEY_ID= SECRET_ACCESS_KEY=
Ok, I created the bucket (webmaker-publisher-staging) and a user with the correct policy, committed the bucket name and region. I can email you credentials or feel free to just generate new ones. Is this enough to get started?
Flags: needinfo?(johns)
Yes!! So do we want it on staging, or want it on mofodev?
Flags: needinfo?(kate)
mofostaging please, I've got mofodev set up to point to heroku
Flags: needinfo?(kate)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(johns)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.