Hi,
currently using:
tiddlywiki 2.5
tiddlyweb 0.9.18
TiddlyWebAdaptor 0.6.2
ServerSideSavingPlugin 0.4.9
TiddlyWebConfig 0.3.1
python 2.4.4
solaris 10
mozilla 3.07

Apache/2.0.63 (Unix) DAV/2 mod_wsgi/2.3 Python/2.4.4 Server at
telesto.ka.tup.com Port 1030

with following config
In /etc/apache2/httpd.conf:
----------
WSGIDaemonProcess telesto.ka.tup.com user=tup processes=2 threads=15
WSGIProcessGroup telesto.ka.tup.com WSGIScriptAlias /tiddlyweb /proj/
tiddlyweb/apache/apache.py

<Directory "/proj/tiddlyweb/apache">
#    Options Indexes FollowSymlinks MultiViews
#    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
----------

In /proj/tiddlyweb/apache/tiddlywebconfig.py:
----------
        'css_uri': './static/css/tiddlyweb.css',
        'system_plugins': [],
        'log_level': 'DEBUG',
        'server_prefix': '/tiddlyweb',
        'server_host': {
            'scheme': 'http',
            'host': 'telesto.ka.tup.com',
            'port': '1030'
            }
        }
----------

The Situation is a follows:
- if we startup the server and go to /tiddlyweb you can navigate
through bags and recipes via html -> OK
- if you want to look into a bag with user policy you are redirected
to the challenger for login and you can log into tiddlyweb-> OK
- if you open a recipe you see the containing tiddlers -> OK
- but if you want to start these Tiddlers as a TiddlyWiki you get an
Internal Server Error
- also the ccs file at./static/css/tiddlyweb.css is not used

we just followed the instructions at apache.py, but can't get
tiddlyweb working together with apache
any hints to solve the problem?

Many Thanks Edi

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to