11 Apr
2008
11 Apr
'08
9:09 a.m.
I have a site running on Pier with Magma persistence.
I need to upgrade current image with site contents stay unchanged.
What are the ways of doing that?
Thanks.
Daniel.
11 Apr
11 Apr
2:06 p.m.
Даниил Баскаков wrote:
I have a site running on Pier with Magma persistence.
I need to upgrade current image with site contents stay unchanged.
What are the ways of doing that?
Thanks.
Daniel.
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
If you are using the Magma-PersistencyManager it is quite simple.
The site contents are stored in magma.
In the new image, when you create a new kernel (of the same name) and
switch it to "PRMagmaPersistency" it will see that there is already a
kernel in the database and will ask if you wish to adopt it for that kernel.
Keith
2:38 p.m.
I do some site changes on Magma-powered image then quit image without
saving. On next entering that image I have no those changes. Is it a
right behavior?
Changes persists only if I save the image. I thought that changes are
not dependent on saving image as your letter seems to confirm.
Daniel
2008/4/11, Keith Hodges <keith_hodges(a)yahoo.co.uk>uk>:
Даниил Баскаков wrote:
I have a site running on Pier with Magma
persistence.
I need to upgrade current image with site contents stay unchanged.
What are the ways of doing that?
Thanks.
Daniel.
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
If you are using the Magma-PersistencyManager it is quite simple.
The site contents are stored in magma.
In the new image, when you create a new kernel (of the same name) and
switch it to "PRMagmaPersistency" it will see that there is already a
kernel in the database and will ask if you wish to adopt it for that kernel.
Keith
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
16 Apr
16 Apr
2:11 p.m.
If you are using the Magma-PersistencyManager it is
quite simple.
The site contents are stored in magma.
In the new image, when you create a new kernel (of the same name) and
switch it to "PRMagmaPersistency" it will see that there is already a
kernel in the database and will ask if you wish to adopt it for that kernel.
Doesn't work... another kernel named 'Pier' appeared.
I explored MagmaSession's and see that in different sessions roots are
different. I found in one session root a needed kernel but current
session does not see it.
What is the right strategy of managing sessions?
I do some site changes on Magma-powered image then
quit image without
saving. On next entering that image I have no those changes. Is it a
right behavior?
Changes persists only if I save the image. I thought that changes are
not dependent on saving image as your letter seems to confirm.
Daniel
Does anybody read me?
2:17 p.m.
I do some site
changes on Magma-powered image then quit image without
saving. On next entering that image I have no those changes. Is it a
right behavior?
Changes persists only if I save the image. I thought that changes are
not dependent on saving image as your letter seems to confirm.
Does anybody read me?
2:36 p.m.
Thank you.
I wonder if my understanding of Pier persistency is correct.
If I do some changes in Pier with Magma persistency and quit image
without saving. Do I see those changes when I start the image again?
Daniel
2:41 p.m.
I wonder if my understanding of Pier persistency is
correct.
If I do some changes in Pier with Magma persistency and quit image
without saving. Do I see those changes when I start the image again?
If you change the Pier code this is not saved.
If you edit a Pier page, this should be stored in the Magma database
and therefor be persistent. As far as I know this is what the Magma
persistency is all about.
Keith, can you confirm this?
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
2:58 p.m.
Hi,
2008/4/16, Даниил Баскаков <gdaniq(a)gmail.com>om>:
Where ?
Did you look at the preference (/seaside/config), then config next to pier.
Maybe there you can change your kernel...
But I've never used Magma too.
What I did was to export a wiki be serializing into a file and then, I
loaded it in the new wiki.
If not too big this can be a solution...
I couldn't make the smartreftreamwork so I used SIXX (available in universe).
see this post if you want to try
(http://www.nabble.com/-Pier--Image-crash-after-a-kernel-import-(through-SIX…)
you have to change the persistency first:
kernel persistency: PRNullPersistency new
then also (to get rid of block-contexts or MADynamicObject instances):
PRComponent allInstancesDo: [ :each | each reset ]
and to serialize:
|xmlString |
PRComponent allInstancesDo: [:ea | ea reset].
xmlString := (PRKernel instanceNamed: 'yourKernelName') sixxOn:
(FileStream fileNamed: 'yourFileName.xml')
to load:
PRKernel instances add: (Object readSixxFrom: (FileDirectory default
readOnlyFileNamed: 'yourFileName.xml'))
there should be a magma way though...
hth
Cédrick
If you are
using the Magma-PersistencyManager it is quite simple.
The site contents are stored in magma.
In the new image, when you create a new kernel (of the same name) and
switch it to "PRMagmaPersistency" it will see that there is already a
kernel in the database and will ask if you wish to adopt it for that kernel.
Doesn't work... another kernel named 'Pier' appeared.
3:37 p.m.
Where ?
It appears at PRPierControlPanel in Persisted Kernels section.
Did you look at the preference (/seaside/config),
then config next to pier.
Of course I did.
Thanx for the proposal, I saw this post about SIXX kernel importing.
But I interested in Magma of having persistency in the way as Lucas said.
Daniel
4:47 p.m.
If PRMagmaPersistency is enabled, then each change to a PRKernel should
be saved in the database, a restart without saving the image) should
pick up the changes.
The application that has Pier and Magma, should have a "Magma" control
panel, and a "Pier"
control panel. You can use the "Magma" control panel to see the open
magma sessions and each
of these should have an "explore" link which opens an explorer.
However, the "Pier" control panel, "Persisted Kernels" section also
has
an "(explore)" link which opens an explorer
so you can see exactly what is in the database.
If you find that your kernel is not actually being persisted, then you
may have an older version of Seaside28Jetsam. I would make sure that
that is up to date.
Keith
17 Apr
17 Apr
6:08 p.m.
After playing with package versions I almost get to success now, but
have no time to check completely.
Here are some clues I found (if I am not mistaken you have relation to them):
(1) This script
(http://smallwiki.unibe.ch/smallwiki/pier/installationofseasidemagmaandpier/)
seems to be not working at least because of current MagmaServerLoader
has old dependencies.
(2) "Magma seasideHelper" from version 33 has "ProcessLocalVariable
subclass: #WACurrentMagmaHelper". I don't know what is
ProcessLocalVariable.
Daniel
2008/4/16, Keith Hodges <keith_hodges(a)yahoo.co.uk>uk>:
If PRMagmaPersistency is enabled, then each change to
a PRKernel should
be saved in the database, a restart without saving the image) should
pick up the changes.
The application that has Pier and Magma, should have a "Magma" control
panel, and a "Pier"
control panel. You can use the "Magma" control panel to see the open
magma sessions and each
of these should have an "explore" link which opens an explorer.
However, the "Pier" control panel, "Persisted Kernels" section also
has
an "(explore)" link which opens an explorer
so you can see exactly what is in the database.
If you find that your kernel is not actually being persisted, then you
may have an older version of Seaside28Jetsam. I would make sure that
that is up to date.
Keith
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
7:25 p.m.
Даниил Баскаков wrote:
After playing with package versions I almost get to
success now, but
have no time to check completely.
Here are some clues I found (if I am not mistaken you have relation to them):
(1) This script
(http://smallwiki.unibe.ch/smallwiki/pier/installationofseasidemagmaandpier/)
seems to be not working at least because of current MagmaServerLoader
has old dependencies.
(2) "Magma seasideHelper" from version 33 has "ProcessLocalVariable
subclass: #WACurrentMagmaHelper". I don't know what is
ProcessLocalVariable.
Daniel
Magma seasideHelper, depends upon the "Logging" package. In universes
it
was not obvious what Logging depends on, however Logging loads the
package "ProcessSpecific".
You can load all of the necessary items by running:
Installer install: 'Logging'.
best regards
Keith
6105
days inactive
6111
days old
11 comments
4 participants
participants (4)
-
cdrick -
Keith Hodges -
Lukas Renggli -
Даниил Баскаков