On Wed, Nov 7, 2012 at 4:26 PM, Dirk Kirsten <dk@basex.org> wrote:

Hi Colin,

this heavily depends on your application. If you really just need BaseX (e.g. you run some RestXQ application) there should be no reason why not to use solely BaseX and run it on port 80. However, if you need something more, which is quite likely, it might be wise (and I would recommend doing so as it adds some flexibility) to run some HTTP server or reverse proxy.

If you want to run Apache or nginx again heavily depends on your needs. Apache is a full-blown HTTP server and very powerful whereas nginx is quite small and very fast. We recently used nginx as reverse proxy to scale to several BaseX instances, which worked really well. So this gives you also the opportunity to scale your application depending on the server load.

Cheers,
Dirk

On Wed, Nov 7, 2012 at 9:57 PM, Colin McEnearney <colinmcenearney@gmail.com> wrote:

Hi,

Can anyone point to some help with deploying a basex webapp to a linux / apache envinroment?

I don't have much experience with Apache config. Is it best to leave basex running on port 8984 and proxy the port 80 requests? Or to config basex to operate on port 80?

Any info on this topic is greatly appreciated. I wonder if maybe it's easier to run something else altogether, such as nginx?

Thanks,
Colin

_______________________________________________
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

--
Dirk Kirsten, BaseX GmbH, http://basex.org
|-- Firmensitz: Blarerstrasse 56, 78462 Konstanz
|-- Registergericht Freiburg, HRB: 708285, Geschäftsführer:
| Dr. Christian Grün, Alexander Holupirek, Michael Seiferle
`-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22