First (alpha!) release of Pier running with Magma Persistency.
Image available from ftp.seasidehosting.st
User: preloaded Password: squeak
enjoy
Keith
------
Image Use Instructions
In pier configuration click on 'Magma Control Panel', which will inform
you that the repository does not exist. If you have placed this image on
seasidehosting then you will have to manually create the repository
directory. Given the list of options as to what repository to create,
click the 'create' button (and wait). The existing pier kernel should
appear in the list with a 'persist' button next to it, click 'persist'.
Then try it and see!
------
------
Detailed Log of Image Creation Steps (alternative title: "monticello
tutorial")
This image was prepared as follows:
Beginning with Squeak3.8-6555full
Initial start asks for updates: select "do not ask again" - this is
important should you wish to deploy. Headless servers (e.g.
seasidehosting) cannot handle user interaction and will stop at this point.
From "world menu > open.... > Monticello Browser"
Browser opens with (Monticello....)
Click the "+Repository Button", select "HTTP" as the repository type,
and enter
MCHttpRepository
location: 'http://www.squeaksource.com/Seaside'
user: ''
password: ''
as the repository info (if you have a login on Squeaksource then you can
enter your initials
as the 'user' above.)
Add the following repository for Monticello.
MCHttpRepository
location: 'http://www.squeaksource.com/Monticello'
user: ''
password: ''
Add the following repository for Magma.
MCHttpRepository
location: 'http://www.squeaksource.com/MagmaTester'
user: ''
password: ''
and the following two repositories for Magritte and Pier
MCHttpRepository
location: 'http://mc.lukas-renggli.ch/magritte'
user: ''
password: ''
MCHttpRepository
location: 'http://mc.lukas-renggli.ch/pier'
user: ''
password: ''
also:
MCHttpRepository
location: 'http://www.squeaksource.com/OmniBrowser'
user: ''
password: ''
(to edit this information:
click the menu button in the right hand pane of the Monticello Browser)
----
Loading Latest Monticello.
More recent versions of Monticello provide better feedback as to which
packages are currently loaded.
Select the http://www.squeaksource.com/Monticello repository, click
"open", select the latest package (Monticello-avi.279) from the main
"Monticello" branch, and click "load".
Select the Monticello package on the left hand pane, and the
squeaksource/Monticello repository in the right hand pane. Click 'open'.
In the repository browser, click on the latest version
(Monticello-avi.279.mcz) and click 'Load'.
----
Loading Seaside
Select "world menu > open... SqueakMap"... and a dialog will ask if you
wish to upgrade SqueakMap. Which you do. Notice that SMBase, SMLoader
packages appeaer in the Monticello browser, since the upgrade is
performed by loading Monticello packages.
In SqueakMap, select the ever so convenient "Seaside Installer" which
should load in the whole of seaside with its dependencies in one go. To
do this select the left had pane menu button, "install". (Part way
through the install you will be prompted to enter an admin username
(seaside) and password (admin))
(if SqueakMap doesnt work it is being knobbled by a more recent
package-cache, remove it and try again)
Select the seaside repositoryClick the "open" and the repository browser
will open.
Select Seaside2.6b1 which is the current latest. In the right hand pane
are the releases. Releases may be made by anyone and they may be small
branches off from the main stream. Periodically an effort will be made
to ensure that all changes are merged. Click the history button in order
to browse the history of this package to get some idea of what is going
on. Look at the ancestors of a package to see if one version is being
sequentially built on the next, or whether any branching is occurring.
Seaside is fairly mature and changes infrequent, therefore it is likely
to be safe to grab the latest version.
Loaded Seaside2.6b1-mb.79
Loaded Scriptaculous-lr.137
To start Seaside doit:
WAKom startOn: 8080.
( Or use the "beach flags" SeasideMorph
available from: http://minnow.cc.gatech.edu/squeak/5862 )
To test if everything is running, check the following url in your normal
web browser.
http://localhost:8080/seaside/config
you should be prompted for you username and password (as given earlier).
----
Loading Magma
Back to the Monticello Browser. Deselect the selected package by
clicking on it once. This should re-reveal all of the registered
repositories.
(It is worth saving this. In the right hand side pane menu button there
is a menu item: "Save Repositories", which writes a simple configuration
script to the working directory.)
Select the http://www.squeaksource.com/MagmaTester repository, and click
"open".
Select MagmaServerLoader, and click "load". (it takes a while!)
loaded MagmaServerLoader-cmm.21
loaded Ma client server-cmm.123
loaded Ma exception handling-cmm.22
loaded Ma time objects-cmm.37
----
Load Magma Seaside Integration Package
Select "Magma Seaside" (lhs) and the latest package and click "load",
loaded Magma Seaside-kph.18
----
Load Magma Seaside Sushi Store Demo fixes
loaded Seaside-Examples-Store-Magma.kph-11
----
Before using Magma may need to execute the following.
MagmaSession initialize.
MagmaRepositoryController initialize.
useful snippets
MagmaSession allInstances cleanUp.
MagmaSession disconnectAndCloseAllConnectedSessions.
----
Load Magritte
loaded Magritte-All-lr.171
Load Pier
loaded Pier-All-lr.109
Load OmniBrowser
loaded OmniBrowser-avi.258
loaded Pier-OmniBrowser-lr.19
----
Latest Pier-Magma code
loaded Pier-Model-kph.80
loaded Pier-Seaside-kph.80
loaded Pier-Magma-kph.1
----
Pre-upload actions:
Monticello Browser - "flush cached versions".
----
Release Preloaded Image as Sqk3.8f-smp.image
___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
(sorry wrong thread)
Error: There is no free space in this set!
I got this error when attempting to add a page
any ideas?
Keith
___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
Howdy
I just started looking at squeak and all the great toys it can
include. I asked about squeak wiki's on the beginners list and Keith
suggested I look at the preloaded image on www.squeak.org and join
this list.
I did Thanks! :-)
I am interested in squeak for education. We are setting up some
classes for kids (of all ages ;-) ) to learn programming. I had
included an intro to squeak in a class a few years ago and am glad I
can come back to look more.
I am looking into a wiki as one way the kids can collaborate. I ran
swiki and was pleased with the little I did with it. I am interested
in the differences between pier and swiki. I plan on working with pier
for at least the next little bit.
My adventures with pier so far are:
I installed on XP and poked a bit to see it up and running.
I then installed squeak on a ubuntu 6.06 linux box from
www.squeak.org. I realized I had not looked to see if squeak was
available from the ubuntu repositories and checked and :-) there it
was. I uninstalled the first copy and then installed from the
repositories.
I then ran with the preloaded pier image and was up in way less that 5
minutes (if you don't count the test on XP and the first load of
squeak) !!!
I added a page to the wiki and can see and edit from various computers
on our network.
I will play more if I have more time this weekend but it is looking good!
Gary
The process of porting minnow from swiki to pier, is likely to happen.
It will just require a little bit of patience, as the needed components
are road-tested and refined.
As you can imagine my own testing process has been somewhat hindered by
image freezes. Now that I have been informed that Squeak vm 3.6.3 is
actually stable. I have been able to create a pier-wiki with 6200 or
more pages for testing purposes.
Initial Stats Using Pier with PRNullPersistency (i.e. everything in
memory):
6200 pages (generated one for each squeak class from squeak sources)
235352 internal links.
Adding a page 100-500ms
Removing a page 215 seconds!!
(many wikis dont support removing pages anyway)
Total Memory = 77Mb.
Compare this to minnow: Text data of its 5889 pages is about 30Mb.
Of course the swiki, has full page history, and uploaded files too.
Pier Magma should be able to handle this kind of load, but it remains to
be explicitly tested.
Anticipated work to make things workable.
1. Some explicit caching of items that will slow pier-magma down with
data on disk rather than in memory. Removal of pages may be extremely
slow without this.
2. Explicit support for an indexed full text search which avoids the
need to traverse the whole data tree for a simple search.
3. Some form of logging of user edits in addition to the default
persistency strategy.
J J wrote:
>I would say go to Pier. I think Kieth released some software that you
can point >at the swiki and it will slurp it all up. Am I right Kieth?
I haven't written any proper data slurper for minnow. I believe there is
already an importing tool. I have pointed wget at minnow to get the
current set of pages as a test data set. Its about 30Mb or so.
Which leads me to a question. How would pier handle some random person
running this script?
#!/usr/bin/ruby
for i in 1..5889
print `wget --user=squeak --password=viewpoints
http://minnow.cc.gatech.edu/squeak/#{i
}.edit`
end
this would probably create almost 5800 seaside sessions, in a matter of
minutes?
Keith
Send instant messages to your online friends http://uk.messenger.yahoo.com
>> No problem. Check out this announcement, it has an example on how
>> to plug together the Comanche modules for a Seaside application:
>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2003-May/
>> 058314.html You might also want to have a look at how WAKom itself
>> sets up the server (and modify this behavior).
> Thanks Lukas. That gets me a file server... as probably you wanted
> me to know.
> If you have any pointers, I'd appreciate it. I'm just trying to get
> the squeakfoundation.org going and Ken would rather not add any
> more rules.
Yes, but you need to modify the example to add Seaside to the root
and not to enable file-serving. Something like this might work:
| ma seaside |
seaside := WAKom new.
ma := ModuleAssembly core.
ma addPlug: [:request | seaside process: request]].
(HttpService startOn: 8080 named: 'httpd') plug: ma rootModule
I've never tried, this is just a guess from what I saw in this mail.
> Ken: there is a fundamental problem on the pointer. Going to
> www.squeakfoundation.org is not problem. But, if you hoover over
> any link, you'll see that it links to : http://127.0.0.1:7780/ ...
In the Seaside application configuration there is also a setting to
change the host-name and host-port. Unfortunately Kom (and Apache 1)
does not communicate that correctly to Seaside figure it out by itself.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
PRPier running with PRNullPersistency
6200 pages in 78Mb
Remove page 215 seconds.
18600 pages in 130 Mb
Remove page 500seconds!
It does take quite a while to copy 6200 pages ~10 Mins, but it does do it.
Keith
Send instant messages to your online friends http://uk.messenger.yahoo.com
> With respect to the other walk back. I am using a completely fresh
> image all the latest sources from monticello.
>
> (see http://smallwiki.unibe.ch/smallwiki/pier/
> installationofseasidemagmaandpier)
I get an error with the installer that #isArray is not understood in
a 3.8 image ... though that is quickly fixed.
Now I understand what you installer scripts are all about. Really
cool is the thing with #answer:with:. In wonder why you have
everything in a single class and not have subclasses for SqueakMap,
Mantis, SqueakSource, etc?
> similar walkbacks are occuring which leads me to beleive that there
> is something missing from the magritte code. Is there an update
> that has missed being checked in?
Ouch, I found a bug in Magritte that was introduced with another
project and caused some problems in Pier. Unfortunately I never
tested the latest version of Magritte together with Pier.
The problem should be fixed now.
Name: Magritte-All-lr.172
Author: lr
Time: 20 October 2006, 11:13:06 am
UUID: 707fe363-6537-4ac4-b947-e92531149efd
Ancestors: Magritte-All-lr.171
Dependencies: Magritte-Model-lr.225, Magritte-Tests-lr.95, Magritte-
Seaside-lr.198, Magritte-Morph-lr.33
- fixed a bug for single-selection and multiple-selection rendering
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Is there a way to easily change the text in the header of Pier to
something different than the object created? When editing the
environment/header I just receive the option to change the component
type and it's name. Obviously, the concept is lost on me.
brad
