addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Project reuses and custom generators or gems

  • Needs a date

  • Needs a location

  • I would consider myself intermediate when it comes to rails. Something I would like a better understanding of is how to move code from one project to the next. I have a client I do pretty much the same API for all the time. I finally have a really great generic project that could handle everything they need on every project with some minor tweaks to the code for the specific project requirements. Maybe gems or generators aren't the best option here. The best way I could explain it is I would almost like a way to say $>rails new-awesome-project "name" and it set up my rails app they way I need it set up every time.

Join or login to comment.

  • Dominic R.

    I imagine it really depends on how your tying things together, but if you're writing an exposed/internal API and new projects are utilizing those features (rather that's implementation or some form of extension) it seems to me like gems would be the best practice for encapsulating plug and play API services, and creating generators customized to basically serve as a scaffolding base "with options" depending on the possible different scenarios your new projects may need. My question would be to ask why you need this? When I think about structuring repetition I always ask myself why ? Maybe a discussion on different options when this type of scenario is encountered; depending on the client, you may not have a lot of wiggle room on the way projects are structured, then again- if they're a more efficient way to derive multiple projects as base branches out of a single repository- then influencing that change could be a win-win. Sounds like an interesting discussion to me.

    January 15, 2013

Want to go?

Join and RSVP

1 going

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy