Typical production install would have just the server running on a machine with the database (on linux in our case) and employees can access the server through their windows pcs with the client installed. For this kind of scenarios, the integrated client will just add up the dependencies. In most of the cases, the server might not even be GUI based.
Deepak PS: I thought replying it to the mailing list updates the message on the forum too. But I think I was wrong. and an older one I mailed to the mailing list: The issue with linux is there are so many distros and each one of them have their own idiosyncrasies. One solution would be to put the client/server packages into online package repositories like karan's or dag's repos for CentOS/RHEL or similar ones for other distributions. Then, installing will be as easy as 'yum install tinyerp-server' or similar ones for urpmi/apt and the package manager will resolve the dependencies. The problem with it is, it takes time for any one to do these things (mainly keeping the packages updated) and its lot easier to put in a packaged source on to the site. Added to that the installation docs are pretty straight forward. And as said above, the issue is just for the first time you try installing it. _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
