Make Copcopter run as a mountable Rails engine

[croaky]

I'm thinking of a particular use case where it would be awesome to let http://stattleship.com crowd-source translations of their stories to their users.

[patricksrobertson]

I think this would be a pretty good idea. For example, I could mount this in an app where I had a clearance/CanCan auth/auth setup and could allow people to create projects that don't know what rake is.

[kwerle]

+1

[natebird]

+1

I think this would be a great idea. We have an internal application that it would be great to have this as a mountable part of the admin instead of a separate app.

Any reason why this was closed?

[patricksrobertson]

I've reopened it. I'd like to explore this some when I've got a free minute.

[ghost]

Definitely a must to have this as a mountable engine. +1

[patricksrobertson]

I disagree as this being a 'must'. I think this is something that I'll be working towards as a nice-to-have. The typical user of Copycopter today is managing two or more applications and doesn't want to manage their keys directly from within each Rails app.

The use case I'm imagining for this being a mountable engine is providing greater extensibility for authorization/authentication for a deployed server app. It would probably as a side result be embedable within an application that uses Copycopter, but I still think thats of questionable use.

Copycopter is already designed around having one having 1 app being the authoritative source for your copy. Having a dev/test/staging version of Copycopter embedded in each environment brings up questions for me.

• Do you point the config to copycopter to production?
• Does each environment point to its own Copycopter engine?
• How do you ensure keys are used consistently across developers machines?

[rubenfonseca]

+1

[kwerle]

"I disagree as this being a 'must'. I think this is something that I'll be working towards as a nice-to-have. The typical user of Copycopter today is managing two or more applications and doesn't want to manage their keys directly from within each Rails app."

I'll buy that. But if it become an engine, then I think the typical user of Copycopter tomorrow will be that everyone bolts on the engine to their app and only deploys one thing to one service instead of multiple apps. Because having it centralized as a service is great if you're a consulting company, but it makes a lot less sense if you're just deploying a single app.

"Do you point the config to copycopter to production?
Does each environment point to its own Copycopter engine?
How do you ensure keys are used consistently across developers machines?"

If you want to. Depends on the shop. That's what config files are for! I think the sensible default is to point 'em all at production...

[patricksrobertson]

We originally decided not to throw time at this feature request because both Iora and Crowdtap are product companies with multiple applications. We generally have the same requirements:

• Our product managers want one location to change copy for all our applications
• Adding copycopter data into our production applications schema is not acceptable
• Adding a browser reachable endpoint for copycopter on our production application is not acceptable

We could work around the latter two by only enabling Copycopter on a staging/demo server... but then we are storing production data on a DB not intended for production use.

As a consultant I'd love to embed Copycopter into my clients application. I don't want to build/maintain a separate application for this. Unfortunately, I'm not a consultant.

As a product centric developer though, I'd love to be able to have finer control over authentication and authorization. Placing the meat of Copycopter into an engine and then making this repository be a basic application that utilizes said engine and then building out a secondary repo that uses something like Devise + CanCan is really sexy to me.

[jgn]

+pi

(Patrick: Attempt at humor)

[croaky]

I believe Vermonster's CopyCat project uses a Rails mountable engine now so you could just point users to it and keep Copycoptet a standalone service.

On Apr 5, 2012, at 1:26 PM, Patrick [email protected] wrote:

We originally decided not to throw time at this feature request because both Iora and Crowdtap are product companies with multiple applications. We generally have the same requirements:

• Our product managers want one location to change copy for all our applications
• Adding copycopter data into our production applications schema is not acceptable
• Adding a browser reachable endpoint for copycopter on our production application is not acceptable

We could work around the latter two by only enabling Copycopter on a staging/demo server... but then we are storing production data on a DB not intended for production use.

As a consultant I'd love to embed Copycopter into my clients application. I don't want to build/maintain a separate application for this. Unfortunately, I'm not a consultant.

As a product centric developer though, I'd love to be able to have finer control over authentication and authorization. Placing the meat of Copycopter into an engine and then making this repository be a basic application that utilizes said engine and then building out a secondary repo that uses something like Devise + CanCan is really sexy to me.

---

Reply to this email directly or view it on GitHub:
#49 (comment)

[bradhaydon]

+1

[wm]

+1

[eendeego]

+1

[patricksrobertson]

Yeah I'm closing this. Tired of the +1. Happy to have you but Vermonster instead of me about it :P.