arup_r: yup, i hate that. my new m.o. is to shed as many dependencies as i can (like shoulda). its been more work here and there, but has been fun in its own fit :)
kareeoleez: think of an engine as a "mini application" that provides some type of functionality to your application. running system commands might be outisde the scope of an engine. keeping the system command functions within a module or class might be the best bet. but then again, i don't know what the abstract of your application is.
kareeoleez: an activejob might be a better bet, more info is needed perhaps to give you a better consultation.
arup_r: i hated that crap. i left the industry becuase of that years and years ago to get into something else. well, i guess i'm still in it part-time working on jobs -- on my own time, my terms :)
kareeoleez: and thats all you want your rails app to do, is setup a system by executing those commands?
kareeoleez: no, i get it now. i actually love to see rails being used for non conventional use cases.
arup_r: cool. i left the software company i was working for at the time in 2002 to go into law. but i never stopped programming, so with my contacts i still make some $ on the side doing something i love to do.
kareeoleez: no, i don't. an engine is just another rails app within a rails app
kareeoleez: think of a gem as a software lib, but a gem could also contain an engine