Hello,
I just got this message from tech support at Webfaction. We are trying to get Seaside available as an option. But I am woefully inadequate to answer his questions well. Below is the email he sent me. > Hello Jimmie, > > Just a bit of an update. > I've managed to get the Squeak VM installed > in a test account's home directory > and it appears to load the Seaside development > image fine so long as I disable X windows using > the -headless flag. I've a few questions: > > 1) What do I need to do to get Seaside > to listen for requests on a port? > 2) What's the deal with X windows, > are they required to deploy a Seaside > application or run Seaside in a > production environment. > > If the answer to my second question is yes > then we're probably not going to support Seaside. Any help and answers greatly appreciated. I would love to enable them to get Seaside hosting going. Thanks. Jimmie _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> > 1) What do I need to do to get Seaside
> > to listen for requests on a port? I start my images like this: squeak \ -mmap 256m \ -vm-sound-null \ -vm-display-null \ "$IMAGE" \ -- PORT "$PORT" > > 2) What's the deal with X windows, > > are they required to deploy a Seaside > > application or run Seaside in a > > production environment. I am using VNC (the Squeak implementation) to connect to the image. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Lukas Renggli wrote:
>>> 1) What do I need to do to get Seaside >>> to listen for requests on a port? > > I start my images like this: > > squeak \ > -mmap 256m \ > -vm-sound-null \ > -vm-display-null \ > "$IMAGE" \ > -- PORT "$PORT" How does the -- PORT (is there supposed to be a space between -- PORT ?) affect the image if in a Workspace you have already done WAKom startOn: 8888? Do you still supply the port as above? -- PORT 8888 Webfaction has several plans at various mb of RAM allowed. Does passing -mmap 40mb constrain the image to 40mb? Would it crash if it attempted to go higher? >>> 2) What's the deal with X windows, >>> are they required to deploy a Seaside >>> application or run Seaside in a >>> production environment. > > I am using VNC (the Squeak implementation) to connect to the image. I'm pretty sure they don't have or allow VNC. Everything would have to be done via web browser or command line (ssh). Are there any problems running a development style image, squeak-dev with Seaside and running it headless? Other than extra memory and space requirements. Eventually I would love to have a kernel image with current Seaside/Pier loaded, and do OmniBrowser and Monticello via web browser. Thanks. And thanks to Isaiah also for his reply. Jimmie _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> I am using VNC (the Squeak implementation) to connect to the image.
> I'm pretty sure they don't have or allow VNC. Everything would have to > be done via web browser or command line (ssh). I think the VNC Lukas is talking about is something Webfaction will have no problem with. It's not VNC as you first think of it. It's just a function of Seaside that allows a System Browser to open in a Web Browser. This means that once your image is uploaded you can access the image in the same way as on your desktop -- except in a browser. Chris _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 10/11/07, Chris Cunnington <[hidden email]> wrote:
> > I am using VNC (the Squeak implementation) to connect to the image. > > > I'm pretty sure they don't have or allow VNC. Everything would have to > > be done via web browser or command line (ssh). > > I think the VNC Lukas is talking about is something Webfaction will have no > problem with. It's not VNC as you first think of it. It's just a function of > Seaside that allows a System Browser to open in a Web Browser. This means > that once your image is uploaded you can access the image in the same way as > on your desktop -- except in a browser. Mm, no - he's talking about the RFBServer implementation from Ian. We use that extensively too. It is indeed VNC (the Chicken of the VNC client works well), but it requires no special server support (beyond any firewalls letting port 5900 through). Avi _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> > Mm, no - he's talking about the RFBServer implementation from Ian. We > use that extensively too. It is indeed VNC (the Chicken of the VNC > client works well), but it requires no special server support (beyond > any firewalls letting port 5900 through). > > Avi Yikes, I'm wrong on this one. Thanks for pointing that out. I've found some great stuff on it: http://squeakvm.org/unix/goodies.html http://map.squeak.org/package/d4f692a8-c7fa-4d49-927f-74aba7e8fd83 And related: http://croqueteer.blogspot.com/2004/09/jasmine-status.html Chris _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Avi Bryant-2
Avi Bryant wrote:
> On 10/11/07, Chris Cunnington <[hidden email]> wrote: >>> I am using VNC (the Squeak implementation) to connect to the image. >>> I'm pretty sure they don't have or allow VNC. Everything would have to >>> be done via web browser or command line (ssh). >> I think the VNC Lukas is talking about is something Webfaction will have no >> problem with. It's not VNC as you first think of it. It's just a function of >> Seaside that allows a System Browser to open in a Web Browser. This means >> that once your image is uploaded you can access the image in the same way as >> on your desktop -- except in a browser. > > Mm, no - he's talking about the RFBServer implementation from Ian. We > use that extensively too. It is indeed VNC (the Chicken of the VNC > client works well), but it requires no special server support (beyond > any firewalls letting port 5900 through). X11 is not required? Is the port configurable? What kind of impact does it have on server resources? CPU usage? I'm not sure that a hosting provider will allow such if the resource use is above the plans limits. I presume one can write a method which can be called via a web browser to start or stop service from the RFBServer. Can one operate something like this: Have the RFBServer running but no client connected. Such would hopefully have little resource usage. Just a guess? Then if you encounter a debug situation, you can possibly have a client connect, debug, disconnect. ? Thanks for any additional information. Jimmie _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 10/11/07, Jimmie Houchin <[hidden email]> wrote:
> X11 is not required? Correct. > Is the port configurable? Yes. The standard range starts at 5900. > I presume one can write a method which can be called via a web browser > to start or stop service from the RFBServer. Yes, some versions of Seaside include WAVNCController which does precisely that. > Have the RFBServer running but no client connected. > Such would hopefully have little resource usage. Just a guess? > Then if you encounter a debug situation, you can possibly have a client > connect, debug, disconnect. ? We have it not running, and in fact suspend the UI process, until there's a problem. WAVNCController lets us start up the VNC server and resume the UI process so we can go in and take a look, and then shut these off after we're done. Suspending the UI process does help to conserve server resources. Avi _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Avi Bryant wrote:
> On 10/11/07, Jimmie Houchin <[hidden email]> wrote: > >> X11 is not required? > > Correct. > >> Is the port configurable? > > Yes. The standard range starts at 5900. > >> I presume one can write a method which can be called via a web browser >> to start or stop service from the RFBServer. > > Yes, some versions of Seaside include WAVNCController which does precisely that. > >> Have the RFBServer running but no client connected. >> Such would hopefully have little resource usage. Just a guess? >> Then if you encounter a debug situation, you can possibly have a client >> connect, debug, disconnect. ? > > We have it not running, and in fact suspend the UI process, until > there's a problem. WAVNCController lets us start up the VNC server > and resume the UI process so we can go in and take a look, and then > shut these off after we're done. > > Suspending the UI process does help to conserve server resources. Beautiful. Thanks. Jimmie _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |