I think I've made some progress. The problem seems to be that since the URL
has "static" in it, nginx is trying to serve it directly (instead of
calling "admin/default/edit"). I think the offending lines in nginx.conf
are the following:
location ~* /(\w+)/static/ {
root /home/aicbt/webapps/nginx_uwsgi_web2py/web2py/applications
/;
}
I don't want to match URLs like this:
http://www.domain.com/admin/default/edit/treatment/static/skeleton/javascripts/tabs.js
but continue to match ones like this:
http://www.domain.com/treatment/static/images/run.jpg
Can anyone recommend a safe update to the regular expression?
Thanks,
Neil
On Monday, June 18, 2012 9:27:43 PM UTC+1, Neil wrote:
>
> Arnaud - did you find a solution to this?
>
> I am having the same problem: I deployed to nginx, and I can edit the
> models/views/controllers/etc. without any problems. However, I get a 404
> when I try to edit static files (like a css). All files appear to have the
> same permissions. Anyone have ideas of other things I can check?
>
> Thanks,
> Neil
>
> On Sunday, October 3, 2010 10:09:48 AM UTC+1, Arnaud Masselin wrote:
>>
>> Hi MAssimo,
>>
>> on localhost, I use web2py server. I look in httpd config.
>>
>> Thanks.
>>
>>
>> On 2 oct, 22:04, mdipierro <[email protected]> wrote:
>> > Could be a permission issue. When you open it from localhost do you
>> > still use lighttpd or do you start web2py user your user account?
>> >
>> > On Oct 2, 10:58 am, Arnaud Masselin <[email protected]> wrote:
>> >
>> >
>> >
>> > > Hi all,
>> >
>> > > i have deployed Web2py 1.83.2 on lighttpd production server. And i
>> > > have a problem for edit css files in the admin interface. I raise a
>> > > 404 error when I try to edit files.
>> >
>> > > Files seems to be accessible because, for example, <app_name>/static/
>> > > landing_a_default_new.css display content of my css file.
>> >
>> > > All others files (language, contoller, html files in views) are
>> > > editable without problems.
>> >
>> > > When i run the same app on localhost, I can edit my css.
>> >
>> > > Where comes this problem ?
>> >
>> > > Thanks.
>
>
