[Collozeum] public directory structure

[Filip Konvička]

>> Regarding MOGUL ids, you have to decide whether to get one for
>> Collozeum, or one for each subproject. The tricky part about getting a
>> new id is that you have to expose the web structure prior to making the
>> request (and it must contain valid data), so that when the id gets
>> activated, the librarian does not choke. So I recommend getting just
>> single id, if possible.
>
> Hm, I don't recall reading anything about this in the MOGUL doc.. As I 
> said, I am completely new to MOGUL. The doc appears to suggest that 
> one first gets a MOGUL id and then sets things up doing
>
> ozmake --config=put --mogulrootid=$MOGULID
> ozmake --config=put --moguldir=$MOGULDIR
> ozmake --config=put --mogulurl=$MOGULURL
>
> see http://www.mozart-oz.org/mogul/node11.html#sec.own.section.new

I may be wrong, but I think that this is only how you build your 
package, not how you set up MOGUL librarian.

The thing about first publishing to the web and only then activating the 
account is that if the librarian is unable to download a package, it 
crashes (every night, hence not updating anything, even from the other 
mogul_ids). So it is best if you first make sure that the librarian 
won't die and only then actually activate the mogul_id. And this is also 
why I propose to use a single mogul_id - simply because it's more 
error-prone.

>
> Anyway, it appears we should first figure out what our public URL 
> could be, and how we can access the data there. If we need to call 
> ozmake in that directory, than we need to install Mozart on the 
> machine in question and we would need a ssh access or something similar.
>
> Any comments?

I think you're right about this.

Cheers,
Filip