[Freeipa-devel] New web directory

[Adam Young]

On 07/06/2010 02:35 PM, Rob Crittenden wrote:
> Adam Young wrote:
>> I think we need a new web directory, something similar to 
>> /usr/share/ipa/html, but that shows up in the web url.
>>
>> The wsgi code chops off the file extension, so user.html becomes 
>> user.  THis will break the javascript.  I'm assuming that was why 
>> we're currently  putting the .js files into /var/lib/cache/assets.
>>
>> I think the simplest appraoch would be to create a directory in 
>> /var/www/html  For static content.  Then, the stuff that I have 
>> checked into freeipa/web (minus the sample data sub dir) would be 
>> deployed to there.   Of course, the problem is that the /ipa URL path 
>> gets redirected to WSGI, but I think we can put an explicit excludes 
>> in for it.
>
> Well, we made a conscious decision not to put data into /var/www/html, 
> I believe mostly related to SELinux, and also to keep our stuff 
> separate. This is also legacy from having TurboGears serving up the UI.
>
> I'm ok with having multiple listeners on /ipa/*, we just want to be 
> sure to keep everything under /ipa and not take over the whole root 
> (well, we do that now but it is easily resolved by removing a couple 
> of redirects).

We already moved forward with putting things into 
/usr/share/ipa/static.  Right now this maps to /ipa/static in the URLs


Not thrilled with the currrent naming scheme.  I'd like to put all of 
our web content under one dir, perhaps /usr/share/ipa/html, with images, 
config, and error as subdirs.  We can turn on auth for all, and turn it 
off for error and config.

I'm not sure that the wsgi code should go under share, as the rest of 
the dynamic python code is under the /usr/lib/python directory.

>
>> As I said before, one of my goals is to be able to do development 
>> completly offline, with no round trips to the server, to ease both 
>> development and to allow for automated testing of the javascript code.
>>
>>
>> If people want to continue to put the static code into 
>> /usr/share/ipa/html then the current html directory should probably 
>> be renamed to 'errors' or something so the good name can be used for 
>> the main html.
>
> Well, error and config both sort of share the same space right now. We 
> need some controlled place to redirect users when kerberos 
> authentication fails, as well as an area to store configuration files. 
> I cheated a bit and used the same directory for both purposes. I don't 
> really care what we end up calling this directory though.



>
> rob