Designate Deploy Master to avoid clobbering live server

[pkarjala]

Because we are using the live deployment on Heroku to gather data from some of our constituents during testing, and because it's an in-memory database, we need to make sure we don't touch it while it's running. To avoid any mishaps, @marknelsonengineer is declared to be the Heroku Lead.

• Only this person pushes a deploy to Heroku.
• Only this person reboots or changes the running state of the Heroku app.

We should also check in each time we're ready to do a deploy to make sure that QA has been addressed.

[marknelsonengineer]

Pre-Launch Checklist:

• Sync the local repo
• Merge with Master
• Review all Perpetual Issues
  • Scan source tree for TODO and TO-DO. CheckStyle does not pickup Scala TODOs.
  • Test with all major browsers
  • Test on Mobile devices
  • Ensure all major functionality has a test
• Update GitHub Home Page (Readme.md)
• Update Project Home Page (branch)
• Run CheckStyle & activator test
• Touch up all package-info.java files
• Check the live site for any interesting data that we might clobber (before we clobber it).

Deploy to Heroku

• git push heroku master

Post-Launch Checklist:

• Scratch test of site
• Mark the release in GitHub
• Test CRUD w/ all browsers and selected mobile devices

Before class

• Prepare talking points
• Have a 10-minute elevator pitch in the can

[marknelsonengineer]

At the next Heroku deployment... consider running this command: apps:rename NEWNAME --app APP # rename the app

...to rename the app in Heroku to PlayWithMagic.

[marknelsonengineer]

Pushed HTTPS fix into Heroku. Looks good now. Need to do an http to https redirect.

[marknelsonengineer]

Draft Milestone-3 Release Notes

This is a major feature release. Quite a bit of effort went into migrating the site from a quick-and-dirty prototype into a user-facing site. Although PlayWithMagic.org is not feature complete (we have 32 new features and more to come! the foundation for the website was laid down in this milestone.

User-oriented improvements since Milestone 2 include:

• Update User Guide
• Ability to upload images
  • Used in Magicians, Routines and Material
  • Supports a full CRUD lifecycle -- Images are deleted when replaced.
  • Backwards compatible with the old ImageURL. Use Uploaded images first, then Image URL, them placeholder image.
• Migration to HTTPS because we will be accepting user accounts and we are a trustee of their passwords (like it or not, people use the same password for lots of websites).
• Support for user authentication:
  • Create basic user (First + Last Name, eMail, Password -- hashed and secure)
  • Login page
  • Context-sensitive navigation
  • Context-sensitive page content (Browse All Sets or My Sets)
• Safe account deletion
  • Users are warned before they delete their account.
  • Deleting an account logs the user out.
  • Users can't delete other users' accounts.
• Adoption of the idea that Routines are owned by the community, not by Magicians. See Issue #187
• Implement logical unique constraints like "Routine name" and "Set name", "Stage name", etc.

Developer-oriented improvements since Milestone 2 include:

• Update Developer Guide
• Fix compatibility issues with JDK 1.6

Internal improvements since Milestone 2 include:

• Migrate from in-memory database to Postgres
  • Datatype specification
  • Unique constraints
  • Foreign key support
  • Null/not-null support
• Migrate from clunky, non-fluid tests to a Page Object design pattern
• Migrate from HTMLUnit-based test browser to Chrome
• Take full advantage of Play Framework's test classes to remove clunky callbacks in Test implementations

[marknelsonengineer]

Hello,

Here's the draft Release Notes:

• Improve authorization awareness of the applicaiton.
  • Update authorization to prevent unauthorized users from editing or deleting routines or magicians.
  • Display navigation elements based on your logged-in state and whether you are the owner of an item or not.
• We're proud to present the Set Notes feature!
  • A Magician may input desired information about a Set, and then get analysis of the Routines they've chosen for the Set.
  • Additional Set Note items are forthcoming in future releases.
• Resolved the https issues to the best of our ability with Heroku.
• Use FontAwesome icons for placeholder images in newly created Profiles, Routines, and Materials that do not have uploaded images.
• Fix image upload issue when deployed on Heroku.
• Evolutions were not being applied in Heroku.
• Cleaned up dead branches.

Please let me know if there are any changes you'd like me to make.

Thanks, Mark

[pkarjala]

Third (indented) bullet:

• Display navigation elements based on your logged-in state and whether you are the owner of an item or not.

Fourth Bullet:

• We're proud to present the Set Notes feature!
  • A Magician may input desired information about a Set, and then get analysis of the Routines they've chosen for the Set.
  • Additional Set Note items are forthcoming in future releases.

Sixth Bullet:

• Use FontAwesome icons for placeholder images in newly created Profiles, Routines, and Materials that do not have uploaded images.

[marknelsonengineer]

Most excellent. Thank you.

Mark

On May 11, 2015, at 6:36 PM, Patrick A. Karjala notifications@github.com wrote:

Third (indented) bullet:

Display navigation elements based on your logged-in state and whether you are the owner of an item or not. Fourth Bullet:

We're proud to present the Set Notes feature! A Magician may input desired information about a Set, and then get analysis of the Routines they've chosen for the Set. Additional Set Note items are forthcoming in future releases. Sixth Bullet:

Use FontAwesome icons for placeholder images in newly created Profiles, Routines, and Materials that do not have uploaded images. — Reply to this email directly or view it on GitHub https://github.com/PlayWithMagic/PlayWithMagic.org/issues/106#issuecomment-101127721.