Zoltan Olah

@siddharthkp it's ok to make the Chromatic `app_code` public. It can only be used to create new builds -- it's not possible to use it to read data or do...

I second this motion. I'm having the same problem after having installed the heroku toolbelt, and having the heroku gem installed in one of my ruby versions. Whilst the message...

I'm seeing this error too. Notice the repeated `api/services` in the path of the input files in the debug output. I think this is showing the error.

@zeroasterisk Thanks for submitting this PR. I hear your use case but I'm not sure I'm comfortable with solving it like this. The reason being that I don't like the...

Hey @LoeLobo - Thanks for creating this PR. I'm not going to merge it however as it breaks the mental model that the migrations package is designed with. I'll leave...

@aramk - Good idea. Right now you're free to use any numbering scheme you want but of course the ordering probably won't be right. I'll add a configuration option for...

@jakobdamjensen they don't have to follow each other. They will be ordered by this line: https://github.com/percolatestudio/meteor-migrations/blob/master/migrations_server.js#L62 so timestamps will work fine right now if that is how you want to...

That would be great. Our SyncedCron package has a `cronHistory` collection to do something similar.

Nice work @AnthonyAstige, that's rad!! I encourage you to share it as a package with `migrations` as a dependancy. We'd like to keep core very light.

You're thinking along the right lines there with Mongo's lack of transactions. However, your concern is tied to how/when your run your migrations. In our case, we deploy our code...