Closed Bug 1005905 Opened 11 years ago Closed 11 years ago

Deploy Gallery Maker to staging, prod

Categories

(Webmaker Graveyard :: MakeAPI, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cade, Assigned: cade)

References

Details

(Whiteboard: [thurs])

This doesn't have to be a very complex tool. I prototyped a tool called the MakeLister (https://github.com/cadecairos/MakeLister demo here: https://www.youtube.com/watch?v=Xg0notQGUBk) It'd be great to get some design ideas so that this can be as simple to use as possible. The basic elements I built for the prototype were: 1. a list of the logged in users lists 2. a rudimentary Make tag search 3. a sortable list display area
* Chris: what's the MVP on this for something we could get folks using in the May 6 - 8 curriculum sprint? (and who should we assign this ticket to?) * could we just ship whatever you demoed at All Hands to start, then pretty up the UI later?
Flags: needinfo?(cade)
Whiteboard: [tues]
We can definitely ship the UI I demoed - but there's a few tweaks that should be made before it will be MVP. * It needs to expose list id's so that they can be plugged into wherever they'll be used (i.e. webmaker.org/gallery ) * It needs a better search tool other than tags (title, desc, author) * scrollable containers! should we host this on the Makeapi? `makeapi.webmaker.org/list-editor` right now it's a separate server
Flags: needinfo?(cade)
Blocks: 1006660
I think it should remain a separate app; it makes life easier on us for sure.
Blocks: 1006662
Assignee: nobody → cade
* Chris: understood that those blockers need to clear before we can test drive it. Maybe pop into our demo sessions at any point Wed, Thurs or Fri so we can at least get the prototype in front of these folks while they're in T.O. so the blockers are: 1) expose list id's 2) better search tool (include title, desc, author, etc) 3) scrollable containers
@ Cade: what do you think about calling this tool a "gallery maker"? instead of a "MakeLister?"
Whiteboard: [tues] → [thurs]
So, They're not really full on blockers - there are ways to work around each issue: 1) You can copy the list id from URL bar in list view 2) tag search works well enough, but more options is definitely better. It would also benefit from some pagination, so makes don't flood the webpage. 3) Without scrolling containers, the position on the page tends to jump around.. which is very annoying, but not the worst. I'd be happy to give a demonstration of the tool at any point in the week! Jon and I are working on landing the API and hooking it up to a Deployment of the MakeLister that anyone can use. from there we'll just be enhancing its UX
+9001 to Gallery Maker!
Summary: Design and Build a Tool for Managing Make Lists → Test drive new Gallery Maker tool at work sprint
* Sweet. Cade, why don't you plan on demo-ing this Wed at 4pm / 4:30pm for us in the community space.
Unfortunately, it seems Jon is going to be on PTO tomorrow, so I don't think I'll be able to get a live deployment working. I'll see if I can figure something out tomorrow, otherwise the demo might have to be local to my machine for now.
I've killed MakeLister, and Gallery Maker has risen from its ashes: https://github.com/cadecairos/Gallery-Maker Includes a UI and UZ fixes: better alignment, drag and drop, fixed ordering, scrollable containers. TODO: better search options, add list ID somewhere highly visible on the Preview page.
**UX Fixes**
Jon and I figured out that express 4.x and 3.x cookie middleware doesn't play nicely with each other, so I've downgraded Gallery Maker to use Express 4.5.2 so it'll remain compatible with our other session cookies. I've filed bug 1007712 to get us onto express 4.x, which will bring us some really nice features.
Status: NEW → ASSIGNED
Morphing this ticket into a deployment one for the Gallery Maker.
Summary: Test drive new Gallery Maker tool at work sprint → Deploy Gallery Maker to staging, prod
What's step one in getting this thing live?
Flags: needinfo?(jon)
Flags: needinfo?(johns)
Blocks: 1011568
Cade: Can you please fill this fella out? https://docs.google.com/a/mozillafoundation.org/spreadsheet/gform?key=0AvM9v6bzUw_bdFBONmhPUXcxVVp5TFBiS0I4OWZ1RFE&gridId=0#edit I'm especially interested in what kind of data it requires, whether it needs ssl, and what kind of traffic it might get. Additionally, I'd like to move this to a Mozilla repo prior to deploying it.
Flags: needinfo?(jon)
Flags: needinfo?(johns)
Flags: needinfo?(cade)
What kind of data it requires: None, just access to https://makeapi.webmaker.org Needs SSL: yes, uses Webmaker Auth, for webmakerprototypes.org What kind of traffic it might get: Very few users This is probably appropriate for Heroku
Depends on: 1013400
Depends on: 1013407
Yeah, I think Heroku would be good for this.
Flags: needinfo?(cade)
These are deployed: gallery.mofostaging.net gallery.webmaker.org
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Guys this should be on prototypes.webmaker.org, no? It has not been through design review.
Flags: needinfo?(cade)
Sure, we'll move this over to webmakerprototypes as soon as we can :jp lets make this switch next time we're both online.
Status: RESOLVED → REOPENED
Flags: needinfo?(cade) → needinfo?(johns)
Resolution: FIXED → ---
Well, which domain/url? prototypes.webmaker.org or gallery.webmakerprototypes.org ? I'll need to then get a new SSL cert for whichever we choose.
Flags: needinfo?(cassie)
gallery.webmakerprototypes.org
jbuck said it :)
Flags: needinfo?(cassie)
I've updated DNS and the SSL cert up on Heroku, so this should now be in the new namespace.
Flags: needinfo?(johns)
On this end, seems to be working. Closing out as resolved!
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.