Hi all,

Before my holidays I started on making the code exporter for pier3 work easy. I 
had some issues, and fixed most of the before my holidays. But now after my 
holidays I had time to test the entire path, so we can deploy our website 
www.legacycode.nl from continuous integration.

We now can use the following script on a clean pharo 2.0 image:
" load the configuration and from the configuration the code exporter for pier "
Gofer new
   url: 'http://smalltalkhub.com/mc/Pier/Pier3Addons/main';
   package: 'ConfigurationOfPier3AddOns';
   load.
((Smalltalk at: #ConfigurationOfPier3AddOns) project version: #'stable') load: 
'Code-Exporter-Pier3'.

" load and start the webserver. For Pharo this we use Zinc "
((Smalltalk at: #ConfigurationOfSeaside3) project version: '3.1.0') load: 
'Zinc-Seaside'.
(Smalltalk at: #ZnZincServerAdaptor) startOn: 8080.

" load your own exported code and perform line below to recreate the kernel
PRKernelCreatorForPier register

and copy the files pier created (css) to the correct folder (default 
.../Resources/files/* )
Note: the pier image sets the folder to a fixed location in 
MAExternalFileModel. To reset this:
        MAExternalFileModel baseDirectoryPath: nil
Setting this folder is also possible if you want to use a location outside of 
your image for your css files. I.e.
        MAExternalFileModel baseDirectoryPath: '~/css'
"

Stephan and Diego

Reply via email to