modified migration files

[omricohen]

I removed all the migration updates and moved them into 4 their respective create migrations. This will greatly simplify new installs.

[msevestre]

I fixed the build. Should be back in businesss soon

[msevestre]

@omricohen could you somehow update that PR to trigger the build again?Thanks

[omricohen]

@msevestre I did -- still failed

[msevestre]

yeah thanks. @jipiboily is going to look into that soon :)

On Tue, Mar 7, 2017 at 11:39 AM Omri Cohen [email protected] wrote:

@msevestre https://github.com/msevestre I did -- still failed

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jipiboily/monologue/pull/312#issuecomment-284777947, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_jVYImMP3CwUH1l0oEjsNtaOiytILrks5rjYg3gaJpZM4MPoMc .

[jipiboily]

yeah, I want to make the build pass again shortly. :)

[jipiboily]

@omricohen while working on making the build pass (#301) I had to resetup Monologue locally, and the migrations worked perfectly fine for me.

What is this PR trying to fix/change exactly? Not 100% clear to me.

Thanks!

[jipiboily]

That's going to be more complicated than I thought. See #301 please. Happy to pay $100 if someone wants to get Monologue back on track.

[jipiboily]

Actually, see https://github.com/jipiboily/monologue/issues/314 instead.

[omricohen]

@jipiboily This PR makes it so that you can rollback a monologue install. The current migrations do not allow for a rollback. Plus, not point in keeping so many migration 'change' files, makes it harder to maintain and understand what is going on.

[msevestre]

I am going to close this PR as it is polluting my Review list and is clearly outdated :)