Some progress

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Some progress

Schwab,Wilhelm K
Hello all,

My plan is to use secure servers even in testing.  This particular
Apache installation is not yet cooperating, but I am gradually tracking
down the problems.  Either the current stumbling block is not related to
rewrites, or my rewrite logging is not working.

At some point, I expect to hit snags with Seaside's configuration.  I
have the book, and recall mention of the base URLs needing to be set.
Do you any of you script the setup?  My goal is to have something along
the lines of

   ConfigureSeaside
       application:'something'
       development:false
       on:'here.there.net'
       ssl:true.

The configuration part of Seaside is impressive, but I suspect a good
script would be easier to use and less error prone.  Any examples that
you have working and don't mind sharing would be appreciated.

Bill







Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: [hidden email]
Tel: (352) 273-6785
FAX: (352) 392-7029

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Some progress

John Thornborrow
Hi Bill,

We (at Pinesoft) use 'secure' servers to deploy our apps. We prefer to
use the Apache module http_proxy to redirect instead of mod_rewrite, but
others may prefer differently.

Apache is setup as close to default as can be for SSL, with an OpenSSL
encryption key in most instances (unless the client is willing to pay
for a signed one..)

As for scripting the setup, here is an example from one of our apps:

OurApplication class>>registerAsSSLApplication
    "Register with deployment preferences."
   
    | application |
   
    application := self registerAsApplication: 'foo'.  
   
    application preferenceAt: #deploymentMode put: true.
    application preferenceAt: #resourceBaseUrl put: '/'.
    application preferenceAt: #serverPath put: '/'.
    application preferenceAt: #serverPort put: 443.
    application preferenceAt: #serverProtocol put: #https.
    application preferenceAt: #errorHandler put: OurErrorHandler.
    "etc .. "

Hope this helps.

John

www.pinesoft.co.uk

Bill Schwab wrote:

> Hello all,
>
> My plan is to use secure servers even in testing.  This particular
> Apache installation is not yet cooperating, but I am gradually tracking
> down the problems.  Either the current stumbling block is not related to
> rewrites, or my rewrite logging is not working.
>
> At some point, I expect to hit snags with Seaside's configuration.  I
> have the book, and recall mention of the base URLs needing to be set.
> Do you any of you script the setup?  My goal is to have something along
> the lines of
>
>    ConfigureSeaside
>        application:'something'
>        development:false
>        on:'here.there.net'
>        ssl:true.
>
> The configuration part of Seaside is impressive, but I suspect a good
> script would be easier to use and less error prone.  Any examples that
> you have working and don't mind sharing would be appreciated.
>
> Bill
>
>
>
>
>
>
>
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
>
> Email: [hidden email]
> Tel: (352) 273-6785
> FAX: (352) 392-7029
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>  


******************************************************************************************************************************************
This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. *******************************************************************************************************************************************


Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside