Re: [Rails-core] [Feature proposal] Migrations-like actions

I maintain a gem here which I think has some cross-purpose for that need https://github.com/jasonfb/nondestructive_migrations it's stated purpose is for data migrations but it sounds like you can use it for your use case almost as-is. -Ja

Re: [Rails-core] [Feature proposal] Migrations-like actions

Can you provide concrete use cases? -- Sent from Gmail Mobile -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.c

Re: [Rails-core] [Feature proposal] Migrations-like actions

Hi Prem, > I actually think initializer is the right place to put those kind of stuff I don't think initializers are the right place for actions that have to be run just once. They are good for setting initial states/configuration of various parts of an application though. Following this logic, w

Re: [Rails-core] [Feature proposal] Migrations-like actions

Hi Vitaliy, I actually think initializer is the right place to put those kind of stuff. Or, maybe do you want to put it in `bin/setup` so you would run it the first time after you clone your application? Alternatively, there are a few data migration gems that you could use, but I think that's

[Rails-core] [Feature proposal] Migrations-like actions

Hello! Sorry if this proposal is a duplicate, I couldn't find anything related. Quite often I have to run some actions on my application starts. Those actions should be executed just once like database migrations. Once an action is executed, it should never be invoked again. Right now I do wha