(Rails) Protecting code and licensing for independently deployed Rails applications...?

Question

Hi All,

I'm writing a Rails application which will have reasonably regular updates -- nothing abnormal here. I face a problem, however, due to the distribution model. Basically the application will be sold for stand-alone "intranet" installation due to its "add-on" nature (it's basically a web interface for an existing, database-driven industry standard application).

My concern(s) then revolve(s) around protecting code and update models (registration codes, etc.) for multiple independently deployed Rails applications. Does anyone have a good starting point for reading up on this? Any input regarding such a process?

Best.

Answer 1

My knowledge doesn't extend much into this realm, but you might want to look into using JRuby to package the Rails application as an executable JAR.

Github recently did something similar for their Firewall Install product (more information on the packaging process here).

It seems likely that this kind of requirement would be much more common in Javaland, so I wouldn't be surprised at all if going the JRuby route was your best bet.

Answer 2

Have a look at the way Mingle do it, I believe they offer a similar deal.

Answer 3

I'd look into code obfuscation.