Popular Threads From Lists.squeakfoundati:
List Statistics
- Total Threads: 1160
- Total Posts: 2236
Phrases Used to Find This Thread
|
# 1
25-07-2012 09:31 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
|
# 2
26-07-2012 05:09 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
|
# 3
26-07-2012 05:27 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 4
31-07-2012 07:31 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
|
# 5
31-07-2012 08:54 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 6
01-08-2012 07:35 AM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 7
01-08-2012 02:48 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 8
01-08-2012 06:51 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
|
# 9
01-08-2012 07:04 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
|
# 10
01-08-2012 07:21 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 11
01-08-2012 07:23 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 12
01-08-2012 11:08 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark,
I am from the school that wants to do eveything using command line only, not running a GUI on a server ;-)
For starters, have a look at this:
http://stfx.eu/pharo-server/
You can then test on localhost.
All you then have to do is set up a security group allowing traffic on port 1701 and it should serve pages externally.
I also don't like images saved with running servers (like Seaside is often used), I rather have nothing running in the image and start the server(s) manually in the startup script.
But there are many ways to go about this and YMMV.
Sven
PS: If you have a 64bit Linux, you need to add 32-bit support, as in
apt-get install ia32-libs
For Ubuntu
On 01 Aug 2012, at 22:35, Mark Andrew <> wrote:
> Hi Sven,
>
> I would like to take you up on your kind offer of help.
>
> I have my ec2 micro server, and as a first sanity check after I had ssh-ed into it I grabbed the current seaside 3.0.7 one-click directly via wget onto my server - which went incredibly fast - hoping to get at least something up on port 80.
>
> I had supplied a -X argument to my ssh command on my mac (which proceeded to open the crufty X-windows thingy) and then tried launching seaside just by calling Seaside.sh, imagining that the gui would turn up on the mac in the X-window environment. Instead I got
>
> [ec2-user@ip-10-228-246-197 Seaside.app]$ ./Seaside.sh
> could not find module vm-display-X11
> Aborted
>
> I also tried directly invoking the vm and the image on the command line,
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak Seaside.image
> squeak: could not find any display driver
> Aborted
>
>
> ... and even saying -headless
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak -headless Seaside.image
> could not find module vm-display-X11
> Aborted
>
> So I have pretty much run out of ideas.
>
> This is using their suggested "Amazon linux" 64 bit AMI as opposed to the ubuntu I am used to. I thought I should go with the flow to start with.
>
> Have googled this enough to see that other people get it. But found no solutions.
>
> I realise there is that special AMI from some guy using gemstone who has done the video tutorial, but I didn't want to have to grok gemstone along with the already tall stack of stuff I have gone through to get this far.
>
> Do you have any pointers?
>
> Thanks in advance
>
> Mark
>
> On Wed, Aug 1, 2012 at 8:21 PM, Sven Van Caekenberghe <> wrote:
> Mark,
>
> On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
>
>> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
>
> If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
>
> http://zn.stfx.eu/zn/index.html#livedemo
>
> If you need help, just ask.
>
> Sven
>
> PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
>
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
>
>
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 13
02-08-2012 08:01 AM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark,
I am from the school that wants to do eveything using command line only, not running a GUI on a server ;-)
For starters, have a look at this:
http://stfx.eu/pharo-server/
You can then test on localhost.
All you then have to do is set up a security group allowing traffic on port 1701 and it should serve pages externally.
I also don't like images saved with running servers (like Seaside is often used), I rather have nothing running in the image and start the server(s) manually in the startup script.
But there are many ways to go about this and YMMV.
Sven
PS: If you have a 64bit Linux, you need to add 32-bit support, as in
apt-get install ia32-libs
For Ubuntu
On 01 Aug 2012, at 22:35, Mark Andrew <> wrote:
> Hi Sven,
>
> I would like to take you up on your kind offer of help.
>
> I have my ec2 micro server, and as a first sanity check after I had ssh-ed into it I grabbed the current seaside 3.0.7 one-click directly via wget onto my server - which went incredibly fast - hoping to get at least something up on port 80.
>
> I had supplied a -X argument to my ssh command on my mac (which proceeded to open the crufty X-windows thingy) and then tried launching seaside just by calling Seaside.sh, imagining that the gui would turn up on the mac in the X-window environment. Instead I got
>
> [ec2-user@ip-10-228-246-197 Seaside.app]$ ./Seaside.sh
> could not find module vm-display-X11
> Aborted
>
> I also tried directly invoking the vm and the image on the command line,
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak Seaside.image
> squeak: could not find any display driver
> Aborted
>
>
> ... and even saying -headless
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak -headless Seaside.image
> could not find module vm-display-X11
> Aborted
>
> So I have pretty much run out of ideas.
>
> This is using their suggested "Amazon linux" 64 bit AMI as opposed to the ubuntu I am used to. I thought I should go with the flow to start with.
>
> Have googled this enough to see that other people get it. But found no solutions.
>
> I realise there is that special AMI from some guy using gemstone who has done the video tutorial, but I didn't want to have to grok gemstone along with the already tall stack of stuff I have gone through to get this far.
>
> Do you have any pointers?
>
> Thanks in advance
>
> Mark
>
> On Wed, Aug 1, 2012 at 8:21 PM, Sven Van Caekenberghe <> wrote:
> Mark,
>
> On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
>
>> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
>
> If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
>
> http://zn.stfx.eu/zn/index.html#livedemo
>
> If you need help, just ask.
>
> Sven
>
> PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
>
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
>
>
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> Mark Andrew wrote:
>>[snip a lot of things he tried to build an image for Seasidehosting]
>
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
>
> - Pharo image is now much newer and saved by CogVM - so it can
> not be used and one has to look for Squeak
>
> - meanhwile Seaside switched to Zinc (since Pharo did it)
> and nobody really cares on "Seaside for Squeak"
> that makes it hard to run a recent Seaside on Squeak
> (Zinc loading problems ...)
There is a server adapter for WebClient [1]. We actually do fix Squeak
issues where reported and possible [2]. However as Pharo and Squeak
diverge more it becomes harder to support both with the same code
base. We're already running into troubles supporting multiple Pharo
versions. In the long run Squeak versions for the corresponding Pharo
implementations will probably have to be created.
[1] http://www.squeaksource.com/WebClient.html
[2] http://code.google.com/p/seaside/issues/detail?id=650
Cheers
Philippe
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 14
03-08-2012 01:51 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark,
I am from the school that wants to do eveything using command line only, not running a GUI on a server ;-)
For starters, have a look at this:
http://stfx.eu/pharo-server/
You can then test on localhost.
All you then have to do is set up a security group allowing traffic on port 1701 and it should serve pages externally.
I also don't like images saved with running servers (like Seaside is often used), I rather have nothing running in the image and start the server(s) manually in the startup script.
But there are many ways to go about this and YMMV.
Sven
PS: If you have a 64bit Linux, you need to add 32-bit support, as in
apt-get install ia32-libs
For Ubuntu
On 01 Aug 2012, at 22:35, Mark Andrew <> wrote:
> Hi Sven,
>
> I would like to take you up on your kind offer of help.
>
> I have my ec2 micro server, and as a first sanity check after I had ssh-ed into it I grabbed the current seaside 3.0.7 one-click directly via wget onto my server - which went incredibly fast - hoping to get at least something up on port 80.
>
> I had supplied a -X argument to my ssh command on my mac (which proceeded to open the crufty X-windows thingy) and then tried launching seaside just by calling Seaside.sh, imagining that the gui would turn up on the mac in the X-window environment. Instead I got
>
> [ec2-user@ip-10-228-246-197 Seaside.app]$ ./Seaside.sh
> could not find module vm-display-X11
> Aborted
>
> I also tried directly invoking the vm and the image on the command line,
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak Seaside.image
> squeak: could not find any display driver
> Aborted
>
>
> ... and even saying -headless
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak -headless Seaside.image
> could not find module vm-display-X11
> Aborted
>
> So I have pretty much run out of ideas.
>
> This is using their suggested "Amazon linux" 64 bit AMI as opposed to the ubuntu I am used to. I thought I should go with the flow to start with.
>
> Have googled this enough to see that other people get it. But found no solutions.
>
> I realise there is that special AMI from some guy using gemstone who has done the video tutorial, but I didn't want to have to grok gemstone along with the already tall stack of stuff I have gone through to get this far.
>
> Do you have any pointers?
>
> Thanks in advance
>
> Mark
>
> On Wed, Aug 1, 2012 at 8:21 PM, Sven Van Caekenberghe <> wrote:
> Mark,
>
> On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
>
>> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
>
> If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
>
> http://zn.stfx.eu/zn/index.html#livedemo
>
> If you need help, just ask.
>
> Sven
>
> PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
>
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
>
>
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> Mark Andrew wrote:
>>[snip a lot of things he tried to build an image for Seasidehosting]
>
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
>
> - Pharo image is now much newer and saved by CogVM - so it can
> not be used and one has to look for Squeak
>
> - meanhwile Seaside switched to Zinc (since Pharo did it)
> and nobody really cares on "Seaside for Squeak"
> that makes it hard to run a recent Seaside on Squeak
> (Zinc loading problems ...)
There is a server adapter for WebClient [1]. We actually do fix Squeak
issues where reported and possible [2]. However as Pharo and Squeak
diverge more it becomes harder to support both with the same code
base. We're already running into troubles supporting multiple Pharo
versions. In the long run Squeak versions for the corresponding Pharo
implementations will probably have to be created.
[1] http://www.squeaksource.com/WebClient.html
[2] http://code.google.com/p/seaside/issues/detail?id=650
Cheers
Philippe
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
I have found seasidehosting.st really useful for demoing projects such as
http://jquerymobile.seasidehosting.st,
http://twitterbootstrap.seasidehosting.st and
http://troller.seasidehosting.st
If memory serves me correctly I had to build these images based on Pharo
1.2.1 and I used Squeak 4.2.4b1 VM.
I don't know what changed between Pharo 1.2.1 and Pharo 1.3 to stop images
working of seasidehosting? Is there any chance whatever changed could be
reverted?
It's a real shame if there isn't a site available where we can demo
projects.
Cheers
Nick
On 2 August 2012 08:01, Philippe Marschall <>wrote:
> On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> > Mark Andrew wrote:
> >>[snip a lot of things he tried to build an image for Seasidehosting]
> >
> > The reason is simple:
> > - Seasidehosting has a custom made VM that only allows you
> > to play in a sandbox
> > Looks like it is too hard for the seasidehosting crew to
> > run it on a new one/or customize a more recent VM
> >
> > - Pharo image is now much newer and saved by CogVM - so it can
> > not be used and one has to look for Squeak
> >
> > - meanhwile Seaside switched to Zinc (since Pharo did it)
> > and nobody really cares on "Seaside for Squeak"
> > that makes it hard to run a recent Seaside on Squeak
> > (Zinc loading problems ...)
>
> There is a server adapter for WebClient [1]. We actually do fix Squeak
> issues where reported and possible [2]. However as Pharo and Squeak
> diverge more it becomes harder to support both with the same code
> base. We're already running into troubles supporting multiple Pharo
> versions. In the long run Squeak versions for the corresponding Pharo
> implementations will probably have to be created.
>
> [1] http://www.squeaksource.com/WebClient.html
> [2] http://code.google.com/p/seaside/issues/detail?id=650
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
|
# 15
06-08-2012 05:40 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark,
I am from the school that wants to do eveything using command line only, not running a GUI on a server ;-)
For starters, have a look at this:
http://stfx.eu/pharo-server/
You can then test on localhost.
All you then have to do is set up a security group allowing traffic on port 1701 and it should serve pages externally.
I also don't like images saved with running servers (like Seaside is often used), I rather have nothing running in the image and start the server(s) manually in the startup script.
But there are many ways to go about this and YMMV.
Sven
PS: If you have a 64bit Linux, you need to add 32-bit support, as in
apt-get install ia32-libs
For Ubuntu
On 01 Aug 2012, at 22:35, Mark Andrew <> wrote:
> Hi Sven,
>
> I would like to take you up on your kind offer of help.
>
> I have my ec2 micro server, and as a first sanity check after I had ssh-ed into it I grabbed the current seaside 3.0.7 one-click directly via wget onto my server - which went incredibly fast - hoping to get at least something up on port 80.
>
> I had supplied a -X argument to my ssh command on my mac (which proceeded to open the crufty X-windows thingy) and then tried launching seaside just by calling Seaside.sh, imagining that the gui would turn up on the mac in the X-window environment. Instead I got
>
> [ec2-user@ip-10-228-246-197 Seaside.app]$ ./Seaside.sh
> could not find module vm-display-X11
> Aborted
>
> I also tried directly invoking the vm and the image on the command line,
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak Seaside.image
> squeak: could not find any display driver
> Aborted
>
>
> ... and even saying -headless
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak -headless Seaside.image
> could not find module vm-display-X11
> Aborted
>
> So I have pretty much run out of ideas.
>
> This is using their suggested "Amazon linux" 64 bit AMI as opposed to the ubuntu I am used to. I thought I should go with the flow to start with.
>
> Have googled this enough to see that other people get it. But found no solutions.
>
> I realise there is that special AMI from some guy using gemstone who has done the video tutorial, but I didn't want to have to grok gemstone along with the already tall stack of stuff I have gone through to get this far.
>
> Do you have any pointers?
>
> Thanks in advance
>
> Mark
>
> On Wed, Aug 1, 2012 at 8:21 PM, Sven Van Caekenberghe <> wrote:
> Mark,
>
> On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
>
>> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
>
> If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
>
> http://zn.stfx.eu/zn/index.html#livedemo
>
> If you need help, just ask.
>
> Sven
>
> PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
>
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
>
>
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> Mark Andrew wrote:
>>[snip a lot of things he tried to build an image for Seasidehosting]
>
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
>
> - Pharo image is now much newer and saved by CogVM - so it can
> not be used and one has to look for Squeak
>
> - meanhwile Seaside switched to Zinc (since Pharo did it)
> and nobody really cares on "Seaside for Squeak"
> that makes it hard to run a recent Seaside on Squeak
> (Zinc loading problems ...)
There is a server adapter for WebClient [1]. We actually do fix Squeak
issues where reported and possible [2]. However as Pharo and Squeak
diverge more it becomes harder to support both with the same code
base. We're already running into troubles supporting multiple Pharo
versions. In the long run Squeak versions for the corresponding Pharo
implementations will probably have to be created.
[1] http://www.squeaksource.com/WebClient.html
[2] http://code.google.com/p/seaside/issues/detail?id=650
Cheers
Philippe
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
I have found seasidehosting.st really useful for demoing projects such as
http://jquerymobile.seasidehosting.st,
http://twitterbootstrap.seasidehosting.st and
http://troller.seasidehosting.st
If memory serves me correctly I had to build these images based on Pharo
1.2.1 and I used Squeak 4.2.4b1 VM.
I don't know what changed between Pharo 1.2.1 and Pharo 1.3 to stop images
working of seasidehosting? Is there any chance whatever changed could be
reverted?
It's a real shame if there isn't a site available where we can demo
projects.
Cheers
Nick
On 2 August 2012 08:01, Philippe Marschall <>wrote:
> On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> > Mark Andrew wrote:
> >>[snip a lot of things he tried to build an image for Seasidehosting]
> >
> > The reason is simple:
> > - Seasidehosting has a custom made VM that only allows you
> > to play in a sandbox
> > Looks like it is too hard for the seasidehosting crew to
> > run it on a new one/or customize a more recent VM
> >
> > - Pharo image is now much newer and saved by CogVM - so it can
> > not be used and one has to look for Squeak
> >
> > - meanhwile Seaside switched to Zinc (since Pharo did it)
> > and nobody really cares on "Seaside for Squeak"
> > that makes it hard to run a recent Seaside on Squeak
> > (Zinc loading problems ...)
>
> There is a server adapter for WebClient [1]. We actually do fix Squeak
> issues where reported and possible [2]. However as Pharo and Squeak
> diverge more it becomes harder to support both with the same code
> base. We're already running into troubles supporting multiple Pharo
> versions. In the long run Squeak versions for the corresponding Pharo
> implementations will probably have to be created.
>
> [1] http://www.squeaksource.com/WebClient.html
> [2] http://code.google.com/p/seaside/issues/detail?id=650
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
On 03/08/12 05:51, Nick Ager wrote:
> It's a real shame if there isn't a site available where we can demo
> projects.
>
You can try Smallharbour. Its goal was to replace Seasidehosting.
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 16
06-08-2012 05:52 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark,
I am from the school that wants to do eveything using command line only, not running a GUI on a server ;-)
For starters, have a look at this:
http://stfx.eu/pharo-server/
You can then test on localhost.
All you then have to do is set up a security group allowing traffic on port 1701 and it should serve pages externally.
I also don't like images saved with running servers (like Seaside is often used), I rather have nothing running in the image and start the server(s) manually in the startup script.
But there are many ways to go about this and YMMV.
Sven
PS: If you have a 64bit Linux, you need to add 32-bit support, as in
apt-get install ia32-libs
For Ubuntu
On 01 Aug 2012, at 22:35, Mark Andrew <> wrote:
> Hi Sven,
>
> I would like to take you up on your kind offer of help.
>
> I have my ec2 micro server, and as a first sanity check after I had ssh-ed into it I grabbed the current seaside 3.0.7 one-click directly via wget onto my server - which went incredibly fast - hoping to get at least something up on port 80.
>
> I had supplied a -X argument to my ssh command on my mac (which proceeded to open the crufty X-windows thingy) and then tried launching seaside just by calling Seaside.sh, imagining that the gui would turn up on the mac in the X-window environment. Instead I got
>
> [ec2-user@ip-10-228-246-197 Seaside.app]$ ./Seaside.sh
> could not find module vm-display-X11
> Aborted
>
> I also tried directly invoking the vm and the image on the command line,
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak Seaside.image
> squeak: could not find any display driver
> Aborted
>
>
> ... and even saying -headless
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak -headless Seaside.image
> could not find module vm-display-X11
> Aborted
>
> So I have pretty much run out of ideas.
>
> This is using their suggested "Amazon linux" 64 bit AMI as opposed to the ubuntu I am used to. I thought I should go with the flow to start with.
>
> Have googled this enough to see that other people get it. But found no solutions.
>
> I realise there is that special AMI from some guy using gemstone who has done the video tutorial, but I didn't want to have to grok gemstone along with the already tall stack of stuff I have gone through to get this far.
>
> Do you have any pointers?
>
> Thanks in advance
>
> Mark
>
> On Wed, Aug 1, 2012 at 8:21 PM, Sven Van Caekenberghe <> wrote:
> Mark,
>
> On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
>
>> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
>
> If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
>
> http://zn.stfx.eu/zn/index.html#livedemo
>
> If you need help, just ask.
>
> Sven
>
> PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
>
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
>
>
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> Mark Andrew wrote:
>>[snip a lot of things he tried to build an image for Seasidehosting]
>
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
>
> - Pharo image is now much newer and saved by CogVM - so it can
> not be used and one has to look for Squeak
>
> - meanhwile Seaside switched to Zinc (since Pharo did it)
> and nobody really cares on "Seaside for Squeak"
> that makes it hard to run a recent Seaside on Squeak
> (Zinc loading problems ...)
There is a server adapter for WebClient [1]. We actually do fix Squeak
issues where reported and possible [2]. However as Pharo and Squeak
diverge more it becomes harder to support both with the same code
base. We're already running into troubles supporting multiple Pharo
versions. In the long run Squeak versions for the corresponding Pharo
implementations will probably have to be created.
[1] http://www.squeaksource.com/WebClient.html
[2] http://code.google.com/p/seaside/issues/detail?id=650
Cheers
Philippe
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
I have found seasidehosting.st really useful for demoing projects such as
http://jquerymobile.seasidehosting.st,
http://twitterbootstrap.seasidehosting.st and
http://troller.seasidehosting.st
If memory serves me correctly I had to build these images based on Pharo
1.2.1 and I used Squeak 4.2.4b1 VM.
I don't know what changed between Pharo 1.2.1 and Pharo 1.3 to stop images
working of seasidehosting? Is there any chance whatever changed could be
reverted?
It's a real shame if there isn't a site available where we can demo
projects.
Cheers
Nick
On 2 August 2012 08:01, Philippe Marschall <>wrote:
> On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> > Mark Andrew wrote:
> >>[snip a lot of things he tried to build an image for Seasidehosting]
> >
> > The reason is simple:
> > - Seasidehosting has a custom made VM that only allows you
> > to play in a sandbox
> > Looks like it is too hard for the seasidehosting crew to
> > run it on a new one/or customize a more recent VM
> >
> > - Pharo image is now much newer and saved by CogVM - so it can
> > not be used and one has to look for Squeak
> >
> > - meanhwile Seaside switched to Zinc (since Pharo did it)
> > and nobody really cares on "Seaside for Squeak"
> > that makes it hard to run a recent Seaside on Squeak
> > (Zinc loading problems ...)
>
> There is a server adapter for WebClient [1]. We actually do fix Squeak
> issues where reported and possible [2]. However as Pharo and Squeak
> diverge more it becomes harder to support both with the same code
> base. We're already running into troubles supporting multiple Pharo
> versions. In the long run Squeak versions for the corresponding Pharo
> implementations will probably have to be created.
>
> [1] http://www.squeaksource.com/WebClient.html
> [2] http://code.google.com/p/seaside/issues/detail?id=650
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
On 03/08/12 05:51, Nick Ager wrote:
> It's a real shame if there isn't a site available where we can demo
> projects.
>
You can try Smallharbour. Its goal was to replace Seasidehosting.
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Looked interesting, tried to register, got this :-(
>thisContext
>[:response | (TelnetProtocolError protocolInstance: self) signal] in SMTPClient(ProtocolClient)>>che...etc...selfa SMTPClientresponse'452 4.4.5 >Insufficient disk space; try again later'
Incidentally I am now the proud owner of a micro Server on EC2. Pretty
straightforward if you know your way around Linux and free for the
first year, but obviously a pretty big hurdle if you "just" want to
get your seaside app out there.
Thanks again for all your help everybody.
Mark
On Mon, Aug 6, 2012 at 6:40 PM, Francois Stephany
<> wrote:
>
>
>
> On 03/08/12 05:51, Nick Ager wrote:
>>
>> It's a real shame if there isn't a site available where we can demo
>> projects.
>>
>
> You can try Smallharbour. Its goal was to replace Seasidehosting.
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
|
# 17
06-08-2012 07:45 PM
|
|
|
Hi all,
after a few weeks of hacking on my first seaside app using Pharo 1.4 (Mac
OS), I was sad to read the following when I tried to deploy it to
seasidehosting,st:
>This interpreter (vers. 6502) cannot read image file (vers. 6505) ... with the additional explanation:
>Your image was previously saved by a JIT VM (Cog, Squeak5.x).
>Due technical reasons, we're currently unable to support such images.
>Try building your application using a Squeak 3.x/4.x VM.
My problem is that there are so many versions of Squeak out there and so
many different ways of getting Seaside, and so far none of them have worked
for me (e.g. "ConfigurationOfSeaside30 load" fails). I google and google
and feel I am drifting further away from my goal.
What is the simplest way for me (e.g. what is available on the internet now
in July 2012) to convert the image? Preferably on a Mac, although I have
Virtualboxes for XP and Ubuntu as well.
Thanks in advance
Mark
Thanks for your pointers guys. Unfortunately all I can see so far is that
my search space has exploded into a plethora of various possible
combination of Seaside Versions, Pharo/Squeak Versions and VM Versions. I
have started exploring this but am always coming up against syntax errors
and other weird stuff while trying to assemble the necessary components,
without even knowing if I am going along the right route.
I know this sounds like an appeal to be spoon-fed but what I really need is
a concrete set of instructions e.g.: "get this vm and this image from this
site and download the rest from the following Meta/Monticello repo. "
Thanks in advance for feeding me :-) And I promise if I ever get it to
work I will write it all up so that you are pestered no more.
Mark,
1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
so what are their recommendations if not find out what combination of pharo and
vms they actually support.
2. create packages for you app so you can save and reload your own application code
test that out using the version of pharo/vm that you are currently using.
Let us know what you learn from the seasidehosting folks and we'll go from there.
Dale
----- Original Message -----
| From: "Mark Andrew" <>
| To: "Seaside - general discussion" <>
| Sent: Thursday, July 26, 2012 9:09:44 AM
| Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
|
|
| Thanks for your pointers guys. Unfortunately all I can see so far is
| that my search space has exploded into a plethora of various
| possible combination of Seaside Versions, Pharo/Squeak Versions and
| VM Versions. I have started exploring this but am always coming up
| against syntax errors and other weird stuff while trying to assemble
| the necessary components, without even knowing if I am going along
| the right route.
|
| I know this sounds like an appeal to be spoon-fed but what I really
| need is a concrete set of instructions e.g.: "get this vm and this
| image from this site and download the rest from the following
| Meta/Monticello repo. "
|
|
| Thanks in advance for feeding me :-) And I promise if I ever get it
| to work I will write it all up so that you are pestered no more.
|
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Dale,
the seasidehosting folks are either all down at the beach or reckon that I
should be able to work this out by myself on the basis of what they already
say in their FAQ, which turns out to be - almost - true. Read on for grisly
details or skip to the TL;DR at the end.
ACT I
Their FAQ says:
"
Press CR to quit...This interpreter (vers. 6502) cannot read image file
(vers. 6505)
Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical
reasons, we're currently unable to support such images. Try building your
application using a Squeak 3.x/4.x VM.
"
My first idea was to try out a "Stack VM" in the hope that this would
comply with their JIT restriction. I found one for the mac here
https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zipand
was pleased when it loaded my current pharo 1.4 image. I then saved
the
image, uploaded it to seasidehosting again and got the same "Press CR to
quit" behavior I had in the first place.
(Sidenote: I have not been able to find any way of interrogating the VM to
ask what format it generates, which means the only way of finding out is by
uploading an image to seasidehosting and seeing if it is accepted. Is there
a standard way of finding this out?)
ACT II
So as a new approach I figured on following their tip and rebuilding with
the squeak.org one-click of 4.3, which I got from here:
http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
I downloaded and started this and then opened
www.squeaksource.com/MetacelloRepository and loaded the topmost
ConfigurationOfSeaside30 (dkh.375)
Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff,
giving me a error box along the way announcing "No version found for
#stable of ConfigurationOfZincComponents". Figuring I would cross that
bridge later I just hit "proceed" and it carried on fetching (a whole bunch
more) stuff until it was done.
The next issue was that I am using REST in my application. I used the
following from the seaside book to get that
Gofer new
squeaksource: 'Seaside30Addons';
package: 'Seaside-REST-Core';
package: 'Seaside-Pharo-REST-Core';
package: 'Seaside-Tests-REST-Core';
load
and that ran to completion with no complaints.
So now I tried loading my application, which I had in a local Monticello
repository. This complained at me for not using capital letters for my
class variable names (my bad), I proceeded through these messages until I
then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just
kept popping up whenever I hit "proceed".
So I gave up trying to load my application and wondered if I could at least
upload the current image, with just the stock seaside I had built and
without my app, to see if the image format was at least the right one.
Before I did this I thought I should at least test it locally. However, the
problem there was that the ConfigurationOfZincComponents message I
mentioned before meant that I was missing WAKom.
So I was stuck.
ACT III
Looking for new avenues, I found (I know, I should have seen this earlier)
that there was a prebuilt squeak + seaside at
http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
I tried uploading this image to seasidehosting and found that it worked.
Then I loaded the REST stuff again as described above and then my own
application from my local repository. Once I had sorted out a few minor
Squeak/Pharo compatibility issues it worked! .... apart from the REST
interface. When I implement a simple REST interface as described in 24.2 of
the Seaside book I get the expected response with Pharo, but the following
comes back from Squeak:
"
!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500<br />
Internal Server Error^M^MInternal Server
Error^MError: Improper store into indexable
object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at
'localhost' Port 8080^M
"
So that is where I am now. I would be pretty happy just to get REST
working, but obviously on the long run I want to be able to build from a
stock squeak so I can keep up with any new stuff that comes along.
TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images
which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips
more than welcome
On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the
> cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of
> pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own
> application code
> test that out using the version of pharo/vm that you are currently
> using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from
> there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that
> it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Mark
pay attention seaside hosting is old and I think that it will be discontinued.
It is better that you use your own server. Have a look at the book for the default apache set up.
People worked on a replacement of seaside hosting: smallHarbour so that you could run the equivalent of seaside hosting but on your machine
Stef
On Jul 31, 2012, at 8:31 PM, Mark Andrew wrote:
> Dale,
>
> the seasidehosting folks are either all down at the beach or reckon that I should be able to work this out by myself on the basis of what they already say in their FAQ, which turns out to be - almost - true. Read on for grisly details or skip to the TL;DR at the end.
>
> ACT I
>
> Their FAQ says:
>
> "
> Press CR to quit...This interpreter (vers. 6502) cannot read image file (vers. 6505)
> Your image was previously saved by a JIT VM (Cog, Squeak5.x). Due technical reasons, we're currently unable to support such images. Try building your application using a Squeak 3.x/4.x VM.
> "
>
> My first idea was to try out a "Stack VM" in the hope that this would comply with their JIT restriction. I found one for the mac here https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM/Architecture=32,OS=mac/lastSuccessfulBuild/artifact/StackVM-mac.zip and was pleased when it loaded my current pharo 1.4 image. I then saved the image, uploaded it to seasidehosting again and got the same "Press CR to quit" behavior I had in the first place.
>
> (Sidenote: I have not been able to find any way of interrogating the VM to ask what format it generates, which means the only way of finding out is by uploading an image to seasidehosting and seeing if it is accepted. Is there a standard way of finding this out?)
>
> ACT II
>
> So as a new approach I figured on following their tip and rebuilding with the squeak.org one-click of 4.3, which I got from here:
>
> http://ftp.squeak.org/4.3/Squeak-4.3-All-in-One.zip
>
> I downloaded and started this and then opened
> www.squeaksource.com/MetacelloRepository and loaded the topmost ConfigurationOfSeaside30 (dkh.375)
>
> Then I did "ConfigurationOfSeaside30 load" and it fetched a bunch of stuff, giving me a error box along the way announcing "No version found for #stable of ConfigurationOfZincComponents". Figuring I would cross that bridge later I just hit "proceed" and it carried on fetching (a whole bunch more) stuff until it was done.
>
> The next issue was that I am using REST in my application. I used the following from the seaside book to get that
>
> Gofer new
> squeaksource: 'Seaside30Addons';
> package: 'Seaside-REST-Core';
> package: 'Seaside-Pharo-REST-Core';
> package: 'Seaside-Tests-REST-Core';
> load
>
>
> and that ran to completion with no complaints.
>
> So now I tried loading my application, which I had in a local Monticello repository. This complained at me for not using capital letters for my class variable names (my bad), I proceeded through these messages until I then hit a new error "UndefinedObject>>defaultMethodTrailer" and this just kept popping up whenever I hit "proceed".
>
> So I gave up trying to load my application and wondered if I could at least upload the current image, with just the stock seaside I had built and without my app, to see if the image format was at least the right one. Before I did this I thought I should at least test it locally. However, the problem there was that the ConfigurationOfZincComponents message I mentioned before meant that I was missing WAKom.
>
> So I was stuck.
>
> ACT III
>
> Looking for new avenues, I found (I know, I should have seen this earlier) that there was a prebuilt squeak + seaside at
>
> http://ftp.squeak.org/various_images/seaside/Seaside%203.0.6.zip
>
> I tried uploading this image to seasidehosting and found that it worked. Then I loaded the REST stuff again as described above and then my own application from my local repository. Once I had sorted out a few minor Squeak/Pharo compatibility issues it worked! .... apart from the REST interface. When I implement a simple REST interface as described in 24.2 of the Seaside book I get the expected response with Pharo, but the following comes back from Squeak:
>
> "
> !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M^M500 Internal Server Error^M^MInternal Server Error^MError: Improper store into indexable object^M
^MKomHttpServer/7.1.3 (Mac OS) Server at 'localhost' Port 8080^M
> "
>
> So that is where I am now. I would be pretty happy just to get REST working, but obviously on the long run I want to be able to build from a stock squeak so I can keep up with any new stuff that comes along.
>
>
> TL;DR Used a prebuilt Squeak + Seaside 3.06 bundle. This produces images which are acceptable to seasidehosting.st. Now I'm stuck on REST, any tips more than welcome
>
>
> On Thu, Jul 26, 2012 at 6:27 PM, Dale Henrichs <> wrote:
> Mark,
>
> 1. find out from the seasidehosting folks if they support the cogvm/pharo1.4 and if
> so what are their recommendations if not find out what combination of pharo and
> vms they actually support.
> 2. create packages for you app so you can save and reload your own application code
> test that out using the version of pharo/vm that you are currently using.
>
> Let us know what you learn from the seasidehosting folks and we'll go from there.
>
> Dale
>
> ----- Original Message -----
> | From: "Mark Andrew" <>
> | To: "Seaside - general discussion" <>
> | Sent: Thursday, July 26, 2012 9:09:44 AM
> | Subject: Re: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
> |
> |
> |
> | Thanks for your pointers guys. Unfortunately all I can see so far is
> | that my search space has exploded into a plethora of various
> | possible combination of Seaside Versions, Pharo/Squeak Versions and
> | VM Versions. I have started exploring this but am always coming up
> | against syntax errors and other weird stuff while trying to assemble
> | the necessary components, without even knowing if I am going along
> | the right route.
> |
> | I know this sounds like an appeal to be spoon-fed but what I really
> | need is a concrete set of instructions e.g.: "get this vm and this
> | image from this site and download the rest from the following
> | Meta/Monticello repo. "
> |
> |
> | Thanks in advance for feeding me :-) And I promise if I ever get it
> | to work I will write it all up so that you are pestered no more.
> |
> |
> | _______________________________________________
> | seaside mailing list
> |
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark Andrew wrote:
>[snip a lot of things he tried to build an image for Seasidehosting]
The reason is simple:
- Seasidehosting has a custom made VM that only allows you
to play in a sandbox
Looks like it is too hard for the seasidehosting crew to
run it on a new one/or customize a more recent VM
- Pharo image is now much newer and saved by CogVM - so it can
not be used and one has to look for Squeak
- meanhwile Seaside switched to Zinc (since Pharo did it)
and nobody really cares on "Seaside for Squeak"
that makes it hard to run a recent Seaside on Squeak
(Zinc loading problems ...)
Maybe the community:
- is able to provide an Squeak-Seaside image that is able to
run on seasidehosting and that could be made available there
- the VM maintainers are able to help to customize a more
recent one to support the sandbox model of seasidehosting so
one can use a Pharo-Seaside image and follow recent developments
Stef wrote:
>pay attention seaside hosting is old and I think that it will be >discontinued.
Sad - it is/was a nice way to showcase seaside stuff
to other people.
http://jquerymobile.seasidehosting.st/
http://twitterbootstrap.seasidehosting.st/
>you could run the equivalent of seaside hosting but on your machine
The problem: not everybody has an own machine. How can we expect
people to use Smalltalk/Seaside if there is no possibility to
start with small budget and grow afterwards.
There are many other technologies out there that offer free hosting
(in the "cloud"). It makes it even harder to choose something exotic
like Seaside.
Thanks
Torsten
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Torsten,
I would think that Heroku buildpacks[1] would be a good (modern) direction to go....there's a buildpack for Dart.
Heroku uses git to deploy code to the buildpack, but since we can use git with Smalltalk[2], now, that shouldn't be a barrier.
Presumably one could set up a buildpack for Pharo or Squeak and/or Seaside ... if I weren't so busy with git/Metacello (the enabling technologies) I'd jump on the buildpacks right now ...
For awhile there it looked like CloudFoundry might be a good solution from VMware, but VMware isn't going to go into the hosting business itself ... which puts us back to searching for a hosting service ....
buildpack for Seaside might be a cool project for the camp smalltalk/seaside sprint at ESUG...
I've already adapted Lukas' builder for running squeak/pharo in travis ci[3] using git-based repos and Metacello so I can't imagine that buildpacks would involve much more than that, although I haven't looked into the details Heroku buildpacks yet ...
Dale
[1] http://blog.heroku.com/archives/2012/7/17/buildpacks/
[2] https://github.com/dalehenrich/filetree
[3] https://github.com/dalehenrich/builderCI
----- Original Message -----
| From: "Torsten Bergmann" <>
| To:
| Sent: Tuesday, July 31, 2012 11:35:53 PM
| Subject: [Seaside] How to convert a 1.4 Pharo Seaside image so that it will work with seasidehosting.st
|
| Mark Andrew wrote:
| >[snip a lot of things he tried to build an image for Seasidehosting]
|
| The reason is simple:
| - Seasidehosting has a custom made VM that only allows you
| to play in a sandbox
| Looks like it is too hard for the seasidehosting crew to
| run it on a new one/or customize a more recent VM
|
| - Pharo image is now much newer and saved by CogVM - so it can
| not be used and one has to look for Squeak
|
| - meanhwile Seaside switched to Zinc (since Pharo did it)
| and nobody really cares on "Seaside for Squeak"
| that makes it hard to run a recent Seaside on Squeak
| (Zinc loading problems ...)
|
| Maybe the community:
| - is able to provide an Squeak-Seaside image that is able to
| run on seasidehosting and that could be made available there
|
| - the VM maintainers are able to help to customize a more
| recent one to support the sandbox model of seasidehosting so
| one can use a Pharo-Seaside image and follow recent developments
|
| Stef wrote:
| >pay attention seaside hosting is old and I think that it will be
| >>discontinued.
|
| Sad - it is/was a nice way to showcase seaside stuff
| to other people.
|
| http://jquerymobile.seasidehosting.st/
| http://twitterbootstrap.seasidehosting.st/
|
| >you could run the equivalent of seaside hosting but on your machine
|
| The problem: not everybody has an own machine. How can we expect
| people to use Smalltalk/Seaside if there is no possibility to
| start with small budget and grow afterwards.
|
| There are many other technologies out there that offer free hosting
| (in the "cloud"). It makes it even harder to choose something exotic
| like Seaside.
|
| Thanks
| Torsten
|
| _______________________________________________
| seaside mailing list
|
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
Cloud. Wish me luck.
Shame about seasidehosting, I added a note to the (otherwise excellent)
seaside book, which was what sent me on this journey of discovery in the
first place ;-)
I must say I am very impressed by the feedback I have got here, from people
who I would have thought have much more pressing calls on their time.
Thanks to everyone. I doubt that you have heard the last of me.
Mark
Hi Mark.
2012/8/1 Mark Andrew <>
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute
> Cloud. Wish me luck.
>
I haven't tried yet (because even I haven't account on amazon, and I'm
slowly learning about gemstone), but has you seen this video?
"Deploy your Seaside application for free with an EC2 micro instance and
Gemstone" http://vimeo.com/18375790
Regards.
>
> Shame about seasidehosting, I added a note to the (otherwise excellent)
> seaside book, which was what sent me on this journey of discovery in the
> first place ;-)
>
> I must say I am very impressed by the feedback I have got here, from
> people who I would have thought have much more pressing calls on their
> time. Thanks to everyone. I doubt that you have heard the last of me.
>
> Mark
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Mark,
On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
http://zn.stfx.eu/zn/index.html#livedemo
If you need help, just ask.
Sven
PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Laurent and Romain updated that VM for the Smallharbour project
(http://www.smallharbour.org/). The idea was to upgrade seasidehosting
and make it work with much newer VMs/Images.
The project is dead (i think) but the code is still there.
http://www.smallharbour.org/
http://www.alpha.smallharbour.org/
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Mark,
I am from the school that wants to do eveything using command line only, not running a GUI on a server ;-)
For starters, have a look at this:
http://stfx.eu/pharo-server/
You can then test on localhost.
All you then have to do is set up a security group allowing traffic on port 1701 and it should serve pages externally.
I also don't like images saved with running servers (like Seaside is often used), I rather have nothing running in the image and start the server(s) manually in the startup script.
But there are many ways to go about this and YMMV.
Sven
PS: If you have a 64bit Linux, you need to add 32-bit support, as in
apt-get install ia32-libs
For Ubuntu
On 01 Aug 2012, at 22:35, Mark Andrew <> wrote:
> Hi Sven,
>
> I would like to take you up on your kind offer of help.
>
> I have my ec2 micro server, and as a first sanity check after I had ssh-ed into it I grabbed the current seaside 3.0.7 one-click directly via wget onto my server - which went incredibly fast - hoping to get at least something up on port 80.
>
> I had supplied a -X argument to my ssh command on my mac (which proceeded to open the crufty X-windows thingy) and then tried launching seaside just by calling Seaside.sh, imagining that the gui would turn up on the mac in the X-window environment. Instead I got
>
> [ec2-user@ip-10-228-246-197 Seaside.app]$ ./Seaside.sh
> could not find module vm-display-X11
> Aborted
>
> I also tried directly invoking the vm and the image on the command line,
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak Seaside.image
> squeak: could not find any display driver
> Aborted
>
>
> ... and even saying -headless
>
> [ec2-user@ip-10-228-246-197 Resources]$ ../Linux/squeak -headless Seaside.image
> could not find module vm-display-X11
> Aborted
>
> So I have pretty much run out of ideas.
>
> This is using their suggested "Amazon linux" 64 bit AMI as opposed to the ubuntu I am used to. I thought I should go with the flow to start with.
>
> Have googled this enough to see that other people get it. But found no solutions.
>
> I realise there is that special AMI from some guy using gemstone who has done the video tutorial, but I didn't want to have to grok gemstone along with the already tall stack of stuff I have gone through to get this far.
>
> Do you have any pointers?
>
> Thanks in advance
>
> Mark
>
> On Wed, Aug 1, 2012 at 8:21 PM, Sven Van Caekenberghe <> wrote:
> Mark,
>
> On 01 Aug 2012, at 19:51, Mark Andrew <> wrote:
>
>> OK, I'm off to Amazon to get myself a microserver in the Elastic Compute Cloud. Wish me luck.
>
> If you have basic Linux skills, that won't be a problem: an AWS EC2 micro instance can get you quite far for just $10 a month (first year is free). I am running multiple load balanced instances as described here:
>
> http://zn.stfx.eu/zn/index.html#livedemo
>
> If you need help, just ask.
>
> Sven
>
> PS: the only downside of a micro instance is that it is CPU throttled (once you stress it 100% for more than a minute or so), not a problem for a normal load, but it shows up in benchmarks as quite a surprise.
>
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
>
>
>
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> Mark Andrew wrote:
>>[snip a lot of things he tried to build an image for Seasidehosting]
>
> The reason is simple:
> - Seasidehosting has a custom made VM that only allows you
> to play in a sandbox
> Looks like it is too hard for the seasidehosting crew to
> run it on a new one/or customize a more recent VM
>
> - Pharo image is now much newer and saved by CogVM - so it can
> not be used and one has to look for Squeak
>
> - meanhwile Seaside switched to Zinc (since Pharo did it)
> and nobody really cares on "Seaside for Squeak"
> that makes it hard to run a recent Seaside on Squeak
> (Zinc loading problems ...)
There is a server adapter for WebClient [1]. We actually do fix Squeak
issues where reported and possible [2]. However as Pharo and Squeak
diverge more it becomes harder to support both with the same code
base. We're already running into troubles supporting multiple Pharo
versions. In the long run Squeak versions for the corresponding Pharo
implementations will probably have to be created.
[1] http://www.squeaksource.com/WebClient.html
[2] http://code.google.com/p/seaside/issues/detail?id=650
Cheers
Philippe
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
I have found seasidehosting.st really useful for demoing projects such as
http://jquerymobile.seasidehosting.st,
http://twitterbootstrap.seasidehosting.st and
http://troller.seasidehosting.st
If memory serves me correctly I had to build these images based on Pharo
1.2.1 and I used Squeak 4.2.4b1 VM.
I don't know what changed between Pharo 1.2.1 and Pharo 1.3 to stop images
working of seasidehosting? Is there any chance whatever changed could be
reverted?
It's a real shame if there isn't a site available where we can demo
projects.
Cheers
Nick
On 2 August 2012 08:01, Philippe Marschall <>wrote:
> On Wed, Aug 1, 2012 at 8:35 AM, Torsten Bergmann <> wrote:
> > Mark Andrew wrote:
> >>[snip a lot of things he tried to build an image for Seasidehosting]
> >
> > The reason is simple:
> > - Seasidehosting has a custom made VM that only allows you
> > to play in a sandbox
> > Looks like it is too hard for the seasidehosting crew to
> > run it on a new one/or customize a more recent VM
> >
> > - Pharo image is now much newer and saved by CogVM - so it can
> > not be used and one has to look for Squeak
> >
> > - meanhwile Seaside switched to Zinc (since Pharo did it)
> > and nobody really cares on "Seaside for Squeak"
> > that makes it hard to run a recent Seaside on Squeak
> > (Zinc loading problems ...)
>
> There is a server adapter for WebClient [1]. We actually do fix Squeak
> issues where reported and possible [2]. However as Pharo and Squeak
> diverge more it becomes harder to support both with the same code
> base. We're already running into troubles supporting multiple Pharo
> versions. In the long run Squeak versions for the corresponding Pharo
> implementations will probably have to be created.
>
> [1] http://www.squeaksource.com/WebClient.html
> [2] http://code.google.com/p/seaside/issues/detail?id=650
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
On 03/08/12 05:51, Nick Ager wrote:
> It's a real shame if there isn't a site available where we can demo
> projects.
>
You can try Smallharbour. Its goal was to replace Seasidehosting.
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
Looked interesting, tried to register, got this :-(
>thisContext
>[:response | (TelnetProtocolError protocolInstance: self) signal] in SMTPClient(ProtocolClient)>>che...etc...selfa SMTPClientresponse'452 4.4.5 >Insufficient disk space; try again later'
Incidentally I am now the proud owner of a micro Server on EC2. Pretty
straightforward if you know your way around Linux and free for the
first year, but obviously a pretty big hurdle if you "just" want to
get your seaside app out there.
Thanks again for all your help everybody.
Mark
On Mon, Aug 6, 2012 at 6:40 PM, Francois Stephany
<> wrote:
>
>
>
> On 03/08/12 05:51, Nick Ager wrote:
>>
>> It's a real shame if there isn't a site available where we can demo
>> projects.
>>
>
> You can try Smallharbour. Its goal was to replace Seasidehosting.
>
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
)
For DEMO hosting - just use your own local PC.
grab a free account with dyndns.org or other service. Point that to your
external IP, setup some port forwarding.
Then run your site on your local PC.
this has the added benefit that you do it once, its easy to demo other
projects.
On Mon, Aug 6, 2012 at 9:52 AM, Mark Andrew <> wrote:
> Looked interesting, tried to register, got this :-(
>
> >thisContext
>
> >[:response | (TelnetProtocolError protocolInstance: self) signal] in
> SMTPClient(ProtocolClient)>>che...etc...selfa SMTPClientresponse'452 4.4.5
> >Insufficient disk space; try again later'
>
>
> Incidentally I am now the proud owner of a micro Server on EC2. Pretty
> straightforward if you know your way around Linux and free for the
> first year, but obviously a pretty big hurdle if you "just" want to
> get your seaside app out there.
>
> Thanks again for all your help everybody.
>
> Mark
>
>
> On Mon, Aug 6, 2012 at 6:40 PM, Francois Stephany
> <> wrote:
> >
> >
> >
> > On 03/08/12 05:51, Nick Ager wrote:
> >>
> >> It's a real shame if there isn't a site available where we can demo
> >> projects.
> >>
> >
> > You can try Smallharbour. Its goal was to replace Seasidehosting.
> >
> > _______________________________________________
> > seaside mailing list
> >
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> seaside mailing list
>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
|
NewsArc Lists
| Culture Pages
| Computing Archive
| Media-Pages
Link to this page on your blog or website by copying the HTML code below and pasting it into your site:
|
|
