search

rapidftr / tracker

The Issue Tracker for RapidFTR
2 stars 3 forks source link

Production deployment (Test upgrade with clickable deployment) #153

Closed baziwane closed 9 years ago

baziwane commented 10 years ago

@scampo, this will require an actual production instance to pull off. This would complete #147

scampo commented 10 years ago

Let's discuss on Monday which instance to use.

On Fri, Aug 1, 2014 at 4:06 PM, baziwane notifications@github.com wrote:

@scampo https://github.com/scampo, this will require an actual production instance to pull off. This would complete #147 https://github.com/rapidftr/tracker/issues/147

  • Data migration required for servers with existing data
    • Images and attachments should migrate
    • Child data should migrate (broken after form builder refresh)
    • Forms should migrate (broken after form builder refresh)
    • Users and Roles should migrate (not affected yet)

— Reply to this email directly or view it on GitHub https://github.com/rapidftr/tracker/issues/153.

baziwane commented 10 years ago

Include #167 as a task on this card

New Form Builder has Form > Form Section > Field.

Old Form Builder has only Form Section > Field.

Make sure to write migrations for the old data.

Pinging @baziwane to take a look at this story as well. If there is any "Ensure Backwards Compatibility" story, this can also be added as a sub-task of that.