On Aug 19, 2013, at 13:41 , Diego Lont wrote:
> 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'
That comes pretty close to working on Pharo 3 too. Only changes needed was replacing
ensureDirectory by ensureCreateDirectory in MAExternalFileModel
For production you'd of course want to remove the default applications and set the loaded kernel
as default application.
Stephan