[Seaside] Re: Internal/external order tracking system
webmail at pielka.de
Sat Dec 18 17:11:42 UTC 2010
From the security and reliability point of view it makes no difference whether to run it internally or externally.
In any case you have to give at least one party external access to the system.
I setup my webserver in the following way:
- ordered a virtual server at a hosting provider (strato.de in Germany)
- let the hoster install a Debian linux system
- installed Seaside on this Debian system
- installed Cherokee Webserver on the Debian system as reverse proxy; this is necessary to run your site on port 80 (http) or 443 (https)
- all the traffic receives port 80/443 on the Cherokee Webserver and is forwarded to Seaside
What you need in addition is a server certificate to run https - I guess you need secure login for your application, right?
Am 18.12.2010 um 15:36 schrieb Sean P. DeNigris:
> Thank you both for the responses.
> I guess my question is what is the best architecture for the system? I see
> three options:
> * run the server externally and provide logins for employees (but what
> happens when they lose their internet connection?)
> * run the server internally and provide public access (I'm hesitant to do
> this because I don't do much web stuff and don't understand the security
> * keep two servers running and export the internal w/r system's data out to
> the external server at regular intervals (this seems very complicated). If
> I did this, could it be done without a DB (e.g. with a reference stream)?
> I've read all the docs and done the tutorials, and everything seems
> straightforward once the direction is set. And I'm curious if/how people
> are setting up existing systems like this with Seaside.
> View this message in context: http://forum.world.st/Internal-external-order-tracking-system-tp3093410p3093713.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside