ruby on rails - What is the best strategy to combine IntrAnet and Web-exposed website? -

I was thinking that someone has some insights on this issue.

A small background :

We are using tracks to build an internal company from an old Debugging and Visual Basic based system, which Works as an intranet for internal printing.

Dilemma

Now we need to replace an old customer-facing website in Java, which will connect to our internal systems. To use, we want to be able to draw information such as inventory, order placement, details of our internal system's account details and make it live on the site. The reason for this is that we order the website through fax and amp; Phone and sometimes we are walking-ins, sometimes (very difficult you), even in the inventory update on our old Java site, we get an opportunity to order the last limit, because we Sell ​​the same item to 2 customers within half an hour. It is usually fixed within a day, but we want to avoid this in the future.

The real question

Does anyone have a suggestion about how to accomplish this is a better way?

These are the three options I see:

a) Create a separate rail app on the web server, which will connect to it similar DB which connects to our internal app.

• +++ plus: live data - the same thing that we see inside our internal app, i.e. the real time in the order, the list has expired

• - Minimum: Potential security risk, duplication of code - that is, I need to duplicate all the controllers, models, ideas etc.

b) Create a separate rail app on the web server, which will connect to a different db from our internal app.

• +++ plus: less security risks
• --- Minimum: additional effort to sync Web DB and internal DB (or using a web service) IKE REST-API), additional code to reduce inventory and order # build, Duplication of code - that is, I need to duplicate all the controllers, models, ideas etc. which deal with the order.

C) Expose the internal app on the web

• +++ Plus: All the above problems have been eliminated, this is a very "dry" er method.
• --- Minuses: Too many security headaches more complex login systems - A & amp; For internal users using a LDAP

So what is the idea? Has anyone had similar problem solving? Please keep in mind that our company has limited resources - that is, a developer who is dedicated to it. So it should be one of those "rights" and "smart" solutions, "do not solve money / people / resources on this".

Thank you.

I will probably create separate controllers for the public site and you can use ActiveResource to draw data from internal applications. Can be used.

Edit - Take a look at Fixed Link and Added API Link