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, we could say that initializers are the right place for database migrations. > Or, maybe do you want to put it in `bin/setup` so you would run it the first time after you clone your application? No, I want to run things just once and save their states (have been run or not). The same thing as database migrations do. > Alternatively, there are a few data migration gems that you could use, but I think that's still not what you are looking for either, right? Actually, they are quite what I need. I wrote this email just to figure out what the community / core team thinks about adding such feature in Rails. :) Best wishes, Vitaliy On Fri, Nov 24, 2017 at 12:28 PM, Prem Sichanugrist <sikand...@gmail.com> wrote: > 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 still not what you are looking for either, right? > > Thank you, > Prem > > On Nov 24, 2017, at 9:34 AM, Vitaliy Klachkov <blackst0ne...@gmail.com> > wrote: > > 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 what I need in migrations which is not right as migrations > go for database related logic. > My actions are not related to database (e.g. clean some files, do > something with cache, send something to an external service, etc). > > I can use those actions in initialiazers with `if` conditions, but that > looks quite weird. > > My proposal is simple. > Please consider adding a DB migrations-like mechanism for actions that > should be run once on start. > > Thank you. > > Best wishes, > Vitaliy. > > -- > 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.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at https://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > > > -- > 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.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at https://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- 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.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
