[Seaside] Remote Development with Squeak/Seaside

[Adrian Lienhard]

On Dec 9, 2004, at 9:32 PM, Jimmie Houchin wrote:
>
> Okay.  That's kind of what I figured would be best. Developing on a 
> local image.
>
> Do you use VNC to load the new code or update from the MC repository?

yep

> Or do you simply have a method in your deployed image you can call via 
> the web which does it for you?

actually, about a year or two ago we used a web interface to Monticello 
or DVS, the ancestor of Monticello, to load the new code. We also had 
(and still have one) images running headless. But sometimes it's really 
useful to have the ui remotely, e.g., to evaluate some initialization 
scripts or to flush the seaside cache. You could also do this over the 
web of course, its just more convenient. Especially when there were 
problems it was very useful to have VNC, to look at the process 
browser, or even to do a alt-. Though, this should, hopefully, not be 
very often needed ;-)

>
> So basically,
> Develop locally.
> Publish to MC repository.
> Update server from the MC repository.

exactly

Cheers,
Adrian

>
>>> Is VNC the predominant means of developing remotely?
>> yes, we use VNC, and it was reasonably fast in my experience.
>
> OK.
>
>>> How well or much can you do with the Seaside browser (inside the web 
>>> browser)?
>>> ie: how practical?  not fixing or minor development, but full 
>>> development.
>> my opinion is that this browser is nice for demos, but... well, I 
>> have never used it to do anything else.
>
> Gotcha.
>
>>> How close or ready is LiveWeb?
>>>
>>> Just wanting to keep the discussion alive and learn how active 
>>> Squeak/Seaside developers handle development on a remote deployed 
>>> machine.
>> does anybody really develop on a deployed app? I can't imagine.
>
> I have not developed a website, so have no experience. I wasn't sure 
> how it was normally done in Squeak/Seaside. I couldn't imagine 
> actively developing with the deployed image machine. But I wasn't 
> quite sure how one went about adding new features and items to a 
> deployed website that you don't have physical access to.
>
> My server currently is at my home on my LAN. I wanted to learn 
> somewhat how these issues were handled,while I can explore and 
> experiment with the different processes while I currently do have 
> physical access. Once I deploy access is about 80 miles, 128 km, or 
> about 2 hours away. Not horrible, but also not horribly convenient. :)
>
> Thanks.
>
> Jimmie Houchin
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>
>
___________________
Adrian Lienhard
www.adrian-lienhard.ch
www.netstyle.ch