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
I'd like to learn how you manage users in Pier. Since Pier is a
Wiki/CMS, allowing users to register, login/logout, and managing their
pages/assets is a big part of any Wiki or CMS.
My plan was to create a "register" component and a "managing users"
component for Pier, but I bet this has already been done - extending the
Unix Security component.
How do you manage users in Pier?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
I just updated to Lukas latest (you updated the tab for your stylesheet)
and now the "File Library" (I think that's what it was called) under
Pier in the configuration is gone. This is where the "file library" was
set. I had it set to my library.
Let me tell you what happens: If I use PRPierLibrary only under
"Libraries" (at the top), no problem with css. If I remove
PRPierLibrary and use my own MyLibrary (which is just a copy of
PRPierLibrary) no css file.
This worked before with MyLibrary.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Philippe Marschall wrote:
> 2007/2/17, Brad Fuller <brad(a)sonaural.com>:
>> Looking through the various Pier documentation, I see that code has
>> changed and thus there are several different explanations of how to
>> change stylesheets. I want to use a different css stylesheets but I
>> can't find out where to change it/them. Isn't there one place to
>> point Pier to one stylesheet?
>>
>> BTW: for some reason, I have no style sheet at all for Pier. I don't
>> know what I did, but I didn't edit any code... I must have loaded a
>> new version of some package. Anyway, unless it stomped on something
>> else, ifI can learn where to change the stylesheet pointer, It'd
>> give me a start.
>
> Thanks to Christoph Wysseier Pier now supports easy custom styles with
> FileLibraries. All you need to do is provide your own FileLibrary that
> implements #styleCss which returns a string that is the main CSS file.
> You can put all your CSS there, or in other selectors (as PierLibrary
> does) or in other locations by importing the CSS files you need.
>
> For example if #styleCss makes
> @import url(basic.css);
> this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary
> one of the classes that actually have a comment that describes what it
> does.
>
> In the configuration of your pier application under 'Pier' you can
> select it in 'File Library'.
Thanks, and in my Pier, it's set to PRPierLibrary.
I'm still a bit lost about File Library, though. Let's use css as an
example. My stylesheets were found only if I redirected, in apache,
where seaside retrieved the files:
RewriteCond /path/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L]
If I remove the RewriteCond, stylesheet files are not found, (even
though I also placed the same files in a sub dir of the image named
seaside/files/PRPierLibrary.)
(the access logs say apache is looking in /seaside/files/PRPierLibrary)
If I go to seaside/config and select configure for "files" I get the
listing of File Libraries, as expected. Selecting PRPierLibary lists
files that are all the css files that (I thought) are pointed to. Fine,
that seems to work. But, when I uploaded a file (just to see where the
file would go) and check the complete server, the file is no where to be
found. However, the file is retrievable from the configuration screen. I
can only assume that the image swallowed it up.
This is confusing. There is a class called PRPierLibrary. PRPierLibrary
is also a directory name - evident because apache is looking for that
directory. Also, if you go to PRPierLibrary in the configuration, the
"files" are not really files. The contents of the files are actually in
the methods of PRPierLibrary.
So, I'm still lost on exactly where seaside is retrieving files.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following classes:"
and there are many of them. Is there a better way to load Pier packages?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Will the seaside location/key of a file that has been uploaded as a
"file" in Pier be guaranteed to be static? For instance, can you always
be guaranteed that a photograph that was uploaded be guaranteed to be at
that address?
Example, this is a photo uploaded to pier:
http://www.<my_domain>/?_s=BGrhMyNQYJbYqctY"
Can this link be used to resize the photo and be guaranteed not to change?
<img src="http://www.<my_domain>/?_s=BGrhMyNQYJbYqctY" width="100"
height="300"
Or, what's the way to resize photos?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Lukas Renggli wrote:
>> But, when looking at the apache access log there is:
>>
>> GET /seaside/files/PRPierLibrary/style.css HTTP/1.1" 404 83
>>
>> In the configuration page, PRPierLibary is in the File Library under
>> Pier. But I don't know why there is css formating in the direct way
>> (http://www.my_domain.org:9999/seaside/pier), and apache is looking for
>> a css file in the second (http://www.my_domain.org/).
>
> That's the new way for Seaside to serve static files.
>
>> BTW: I did create a sub-directory called: files/PRPierLibrary with the
>> default style.css from Lukas under the directory where the image is
>> located, but that didn't do anything.
>> (I stopped and restarted WAKom just in case.)
>
> You either need to create a directory seaside/files/PRPierLibrary/
> with your files or add the following rewrite rule right after enabling
> the rewrite engine:
>
> RewriteRule ^/seaside/files/PRPierLibrary/(*.)$
> http://www.my_domain.org:9999//seaside/files/PRPierLibrary/$1 [P,L]
(I moved this to the Pier ML as I think it's Pier related, sorry if this
is confusing - don't want to bother others)
Thanks Lukas.
Along those same lines, I'm getting long lines after the domain name
when I select a link in Pier. Is this correct?
information/license?command=PRViewCommand&view=PRDefaultView&_k=swboZglt&29&_n&_s=MELVlGoXVospTlDw
?command=PRViewCommand&view=PRDefaultView&_k=zYTOouCP&21&_n&_s=MELVlGoXVospTlDw
information/license?command=PRViewCommand&view=PRDefaultView&_k=rKYbypAd&25&_n&_s=MELVlGoXVospTlDw
seems like it should be shorter.. they are shorter in my other seaside
app, although, it's not Pier.
