[railroad-dev] I am a bit lost

[Julian Davison]

JR wrote:
> 4. Railroad Apache configuration
> OK with the sample but I didn't manage to do the simple installation 
> (not using authorization)

I had some trouble making it all work without a database, as I
recall. Ultimately it didn't concern me as I want to use a
database, and I sorted it out using one.

> Another problem is that if I do run again mk_conf.py it simply print me 
> the apache conf.

Which is good if you need it again, and not good if you want
to change anything :)
mk_conf.py stores a copy of your answers in a file called
".apconf" which can be removed to make it start again.
(There might be a better way, but it seemed to work for me)

> 5. Initialising a repository
>  > python repoadm.py add railroad_data admin ***** localhost:82 
> /www/rrr/ /www/rrr/ /www/rrr/
> is the command I typed cause I had no idea of what I could make.
> Do the params have to match with something entered before (I guess yes, 
> but which of them ?).

doc/install.txt has a summary of the params for repoadm.py.
It perhaps could make it clearer that params 4, 5, and 6
(host, path, and upload_path) refer to URL paths and
7 is a filesystem path.
I used
     python repoadm.py add contentdb admin * cdb.cbhs.school.nz /repo/ 
/repo/upload/ /home/julian/rrr/

as the test setup is hosted on the (virtual) server cdb.cbhs.school.nz,
the repository is at cdb.cbhs.school.nz/repo/ and things get uploaded
to cdb.school.nz/repo/upload/.
And for now the files reside in /home/julian/rrr/ on the servers local
harddrive.

> 6. The client data
> Things I didn't do cause I am not sure the step before worked properly
> and I don't know what params mean...

doc/install.txt has some info.
The 'name' of a client is used to work out which 'auth_url' to
use to determine whether or not to permit a given request.
So the name can be anything, so long as you remember it to use
it in things like the Plone proxy object/service/etc.
The 'auth_url' is what Railroad uses to actually verify a given
username/password on access. Using the provided Plone/Zope products
it looks something like
     http://127.0.0.1:9673/cdb/portal_railroad/cdb/authorize

for a Plone instance called 'cdb', with a RailroadTool called
'portal_railroad' that has a PloneRailroadService called 'cdb'.

> On the other side I already put Railroad and PloneRailroad directories 
> in the Product dir of my Zope...
> 
> Then maybe some Icon will appear in my plone site and everything will 
> become clear.

:)
The Plone products need the right config too, or they won't do much :)




J,