3 Mar
2007
3 Mar
'07
3:46 p.m.
Hi,
I created a pier-blog image based on squeak-dev-83:
http://damien.cassou.free.fr/squeak-web/
Bye
--
Damien Cassou
4 Mar
4 Mar
4:40 p.m.
Hi,
File uploading doesn't seem to work on this image.
I don't know why, I am not good enough to fix this bug :-[
Bye
PS : Should I write SUnit? :-)
Damien Cassou a écrit :
Hi,
I created a pier-blog image based on squeak-dev-83:
http://damien.cassou.free.fr/squeak-web/
Bye
6:27 p.m.
File uploading doesn't seem to work on this
image.
I don't know why, I am not good enough to fix this bug :-[
Please check out this mail:
It appears that MAExternalFileModel uses a dictionary
to maintain the
directory location
classPool: a Dictionary(#BaseDirectory->UnixFileDirectory on
'/my/path/to/files' #BaseUrl->nil)
This is part of the file-model of Magritte. Some time ago I changed
this model to allow storing files externally as opposed to enforce the
use of a ByteArray within the image. The class MAExternalFileModel has
a two class variables (this is not really a dictionary) that allow to
configure these external files further. There are accessors on the
class-side that you can use to configure these settings:
MAExternalFileModel class>>baseDirectory: aStringOrDirectory
"Defines the base-directory where the files are stored. This
defaults
to a subdirectory of the current image-location."
MAExternalFileModel class>>baseUrl: aString
"Defines the base-URL where the files are served from, when
using an
external web server. This setting is left to nil by default, causing
the files to be served trough the image."
my questions are does anyone know if there are other
gotchas about
moving the image? How should I change this? Is there a global way of
changing the location for access? I have a feeling that there will be
more walkbacks because I moved the pier image from one server to
another.
No, I don't think so. Copy the base-directory to your new server and
update the setting if necessary.
Cheers,
Lukas
Bye
PS : Should I write SUnit? :-)
Damien Cassou a écrit :
--
Lukas Renggli
http://www.lukas-renggli.ch
Hi,
I created a pier-blog image based on squeak-dev-83:
http://damien.cassou.free.fr/squeak-web/
Bye
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
9:51 p.m.
Lukas Renggli wrote:
I assume that this has nothing to do with WAFileLibrary?
Now, with using ProxyPass and ProxyPassReverse that I'm only using in
apache (no rewrite rules) I have no idea where WAKom is looking for my
css files. No matter what pointer I place in the method styleCss, it
doesn't seem to find them (I have an exact location off of the directory
the image is located). In fact, i don't even think styleCss is being
accessed. Yes, I did add selectorsToInclude method in my own FileLibrary.
Also, bypassing apache (http://my.domain.com:9999/seaside/pier) finds no
css files either.
Can others post their apache settings and also where they place their
css files on your server? That might help. Or, what do you do for
accessing css files? Obviously, I'm confused once again. This just seems
a bit too complicated.
File uploading
doesn't seem to work on this image.
I don't know why, I am not good enough to fix this bug :-[
Please check out this mail:
It appears that MAExternalFileModel uses a
dictionary to maintain the
directory location
classPool: a Dictionary(#BaseDirectory->UnixFileDirectory on
'/my/path/to/files' #BaseUrl->nil)
This is part of the file-model of Magritte. Some time ago I changed
this model to allow storing files externally as opposed to enforce the
use of a ByteArray within the image. The class MAExternalFileModel has
a two class variables (this is not really a dictionary) that allow to
configure these external files further. There are accessors on the
class-side that you can use to configure these settings:
MAExternalFileModel class>>baseDirectory: aStringOrDirectory
"Defines the base-directory where the files are stored. This
defaults
to a subdirectory of the current image-location."
MAExternalFileModel class>>baseUrl: aString
"Defines the base-URL where the files are served from, when
using an
external web server. This setting is left to nil by default, causing
the files to be served trough the image."
my questions are does anyone know if there are
other gotchas about
moving the image? How should I change this? Is there a global way of
changing the location for access? I have a feeling that there will be
more walkbacks because I moved the pier image from one server to
another.
No, I don't think so. Copy the base-directory to your new server and
update the setting if necessary.
5 Mar
5 Mar
7:03 a.m.
No, I
don't think so. Copy the base-directory to your new server and
update the setting if necessary.
I assume that this has nothing to do with
WAFileLibrary? Now, with using ProxyPass and ProxyPassReverse that
I'm only using in
apache (no rewrite rules) I have no idea where WAKom is looking for my
css files. No matter what pointer I place in the method styleCss, it
doesn't seem to find them (I have an exact location off of the
directory
the image is located). In fact, i don't even think styleCss is being
accessed. Yes, I did add selectorsToInclude method in my own
FileLibrary.
I can't help you with ProxyPass and ProxyPassReverse, I never used that.
I don't use FileLibrary since I use Apache. Of course it is possible
to use both, but I don't see the point. For my Web site I also
created and added a file-library, but I only use it to conveniently
add the static style-sheets to the HTML head:
Also, bypassing apache
(http://my.domain.com:9999/seaside/pier)
finds no
css files either.
Can others post their apache settings and also where they place their
css files on your server? That might help. Or, what do you do for
accessing css files? Obviously, I'm confused once again. This just
seems
a bit too complicated.
The out-of-the box image (the one you get when installing Pier from
SqueakMap) just works. If you start to change settings and/or use
Apache then the complexity is in your own hands.
My Apache configuration looks like this:
<VirtualHost *:80>
ServerName www.lukas-renggli.ch
DocumentRoot /home/apache/www.lukas-renggli.ch
<Directory /home/apache/www.lukas-renggli.ch>
Order deny,allow
Allow from all
</Directory>
ProxyPreserveHost On
RewriteEngine On
RewriteCond /home/apache/www.lukas-renggli.ch/%
{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9002/seaside/pier/$1
[proxy,last]
</VirtualHost>
The rewrite rules basically says: If there is no static file on the
filesystem home/apache/www.lukas-renggli.ch matching the request the
pass it on to the Pier image running on port 9002.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
4:10 p.m.
Thanks Lukas. That's pretty much my old rewrite rules. The problem I had
was on the WAKom side - I was not able to remove the /seaside/ trailing
after the URL. That's why I went to ProxyPass.
Sure, I think it works right out of the box, but you have to work at
getting it to eliminate the trailing application path (e.g.
/seaside/pier.) I have a Seaside 2.6 site with rewrite rules and with
changing the Base URL and entry point it finds the css files fine (not a
pier site). This one is just giving me a headache!
I appreciate your clear instructions, you've provided me with some more
ideas.
brad
6528
days inactive
6530
days old
5 comments
4 participants
participants (4)
-
Brad Fuller -
Damien Cassou -
Lukas Renggli -
Mathieu Cassonnet