2 ms·
Additionally, it's not exactly ideal to have to start with a bunch of boilerplate. If something changes in the template, you have to manually port that to ever
by yellowapple 9y ago
Additionally, it's not exactly ideal to have to start with a bunch of boilerplate. If something changes in the template, you have to manually port that to every project using that template.
This is really the sort of thing that gems are designed to accomplish. The only boilerplate should be the Gemfile and maybe some configuration files; all the other shared functionality should be packaged up and distributed as versioned gems listed in that Gemfile.
If Rails in this day and age is somehow an obstacle to that (e.g. because it insists upon an excess of setup tasks that can't be encapsulated as a gem that provides a rake task), then it might be high time to consider an alternative.