[Seaside] Seaside on EC2 Amazon Service

[Dale Henrichs]

I agree with Nick ... I told you I wasn't a web guy:)

----- Original Message -----
| From: "Nick Ager" <nick.ager at gmail.com>
| To: "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
| Sent: Tuesday, October 18, 2011 1:26:04 PM
| Subject: Re: [Seaside] Seaside on EC2 Amazon Service
| 
| 
| 
| 
| 
| I got access to SeaSide on my Amazon EC2 instance by opening port
| 8080 and
| hitting Swazoo
| 
| I'm sure I'm all wrong, somehow, with doing this, but it was nice to
| see that I actually do have end to end connectivity to my Seaside
| code
| running on EC2. What if I just ran Swazoo on port 80? Would that be
| bad?
| 
| 
| 
| Debugging FastCGI problems isn't easy. You add a 'debug' directive to
| Nginx and examine the log file.
| 
| 
| You can always use Nginx to as the font-end server; then delegate to
| Swazoo on 8080.
| 
| 
| Nick
| _______________________________________________
| seaside mailing list
| seaside at lists.squeakfoundation.org
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|