Page MenuHomePhabricator
Create Task
Maniphest T126142

Set up a new dashboard staging server
Closed, ResolvedPublic
Actions

Description

Ready to use:
https://wikiedu-dashboard-staging.wmflabs.org/

Many things are going to be a bit broken, feel free to report as bugs but please don't do exhaustive QA. This server is running development code, and the main purpose is to make a live demo of new features available to us.

Notes

We've started making promises to not break https://outreachdashboard.wmflabs.org/ . This means we have no staging server. In order to develop and get feedback on our work, we should set up another, publicly routable labs server, by hand if puppet is not available in time.

Deployment is unfortunately tied to my user account. We need to create a shared account for this, I suppose. The command is simply:

cap wmf-staging deploy

Related Objects
Search...

Event Timeline

awight created this task.Feb 7 2016, 12:37 AM
awight raised the priority of this task from to Needs Triage.
awight updated the task description. (Show Details)
awight added a project: Education-Program-Dashboard.
awight added subscribers: awight, • dduvall.
Restricted Application added subscribers: StudiesWorld, Base, Aklapper. · View Herald TranscriptFeb 7 2016, 12:37 AM
Ragesoss subscribed.Feb 7 2016, 12:44 AM

I brought up previously the idea of using wikiedu-dashboard-staging.wmflabs.org for the purpose. The name would be easy to change. The one wrinkle at present is that I used that server to test out the process of upgrading to ruby 2.3, which means that it's currently not configured in a way that is compatible with master.

But, I hope to switch to ruby 2.3 for master (and production) next week, and then we could put that server in sync with master and use it as staging for outreachdashboard.wmflabs.org.

Or, it's not that difficult — maybe a couple hours at most — to spin up a new instance on labs by hand.

awight assigned this task to Ragesoss.Feb 7 2016, 1:08 AM

@Ragesoss:
Oh, thank you for doing the footwork! I had missed this somehow.

I'm assigning this to you just as a reminder to let us know it's unblocked, once master is compatible with ruby 2.3. After that, if the server you set up can't be used for some reason, please don't worry about setting up a third one! We eventually need to build this provisioning knowledge "in-house" anyway...

• dduvall added a parent task: T127103: [epic] Puppetize labs deployment of the Program Dashboard.Feb 16 2016, 7:30 PM
awight moved this task from Backlog to Support tasks on the Education-Program-Dashboard board.Feb 17 2016, 6:08 AM
• Elitre subscribed.Feb 17 2016, 4:48 PM
awight added a project: Program Dashboard Sprint 1.Feb 18 2016, 7:27 PM
Ragesoss removed Ragesoss as the assignee of this task.Feb 18 2016, 7:37 PM
awight edited projects, added Programs-and-Events-Dashboard-Sprint 2; removed Program Dashboard Sprint 1.Feb 18 2016, 7:42 PM
awight set Security to None.
awight edited projects, added Program Dashboard Sprint 1; removed Programs-and-Events-Dashboard-Sprint 2.Feb 20 2016, 10:52 PM

Change of heart--I'm moving to the first sprint cos demoing our changes will be good for morale. I can probably do the work, twiddle the Ruby version, etc.

awight updated the task description. (Show Details)Feb 23 2016, 1:33 AM
awight moved this task from Next Up to Done on the Program Dashboard Sprint 1 board.
awight updated the task description. (Show Details)Feb 23 2016, 1:37 AM
awight closed this task as Resolved.Feb 27 2016, 6:59 AM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL