search

ftlabs / perf-widget

22 stars 2 forks source link

Don't drop tables on deploy #76

Closed seanmtracey closed 8 years ago

seanmtracey commented 8 years ago

Issue

Currently, with every deploy to a local/live/test server, we drop the tables in our database so that we can recreate them with any changes in the structure. While this is a nice, convenient way to ensure that we have consistent table structure across our instances, regrettably, we lose all of the information/history about every page that we've ever perfed (perf'd, perf-d?).

Solution

While not an issue for local/test instances that information would be useful to keep once on our live servers.

Proposed Solution/s

  1. Agree to not change our current table structure and only run the database destruction+creation code when we're not on a production server
  2. Come up with a smarter way to migrate table data across different data structures
JakeChampion commented 8 years ago

I vote for option 2.

JakeChampion commented 8 years ago

We need to do this prior to the next deploy from Test to Live

seanmtracey commented 8 years ago

Closed by #134