Considerations for moving our web app to an appliance

We have developed a web application running on Linux that is quite popular. We now wish to release it as an appliance so customers can run it internally on their own networks.

We are unsure of the best approach. We are flexible on areas such as: the Linux distro, whether it's a hardware or software only appli开发者_开发百科ance. Does anyone have any advice on the best way to go about this? Links to any good resources on the subject? Questions we should be asking ourselves? Legal considerations for a commercial app? Security considerations?

UPDATE:

It's a Python based web application. We would like the user to be able to do everything via a web interface. No command line stuff etc.

I know when Github needed to do something similar, they contracted with a company who specializes in building installers called BitRock.

If you want to develop the solution yourself, you can't go wrong building a Debian package (or RPM if you prefer). That's what most linux system admins would be comfortable with, and there are very well-known ways to give them a mix of customization/control while also making the process easy to manage on your end. That gives you and your users a very well-known update path as well.

Unless you have had very specific requests from customers, I would shy away from a turnkey-style appliance where you provide hardware. It's extra work for you and could be a turn-off to customers. Different business have different needs though, so maybe your client-base doesn't have IT and would prefer an all-in-one solution. Until you ask, you can't be sure though.

It depends on what langauge/tecnology application is written. If it is java, release war file + tomcat/jboss. If it is python, release eggs. If it is php... not sure, probably just .tar.bz2.

Linux distro or virtual image mught be advantage, but I dislike using them, because they are usually does not fits to my infra (why do I have to install some custom debian-based distro to my rhel-only infrastructure?).