Re: how to tell apache to see my projects database file?

On 12-05-30 7:04 AM, doniyor wrote:

what do you mean? should i do better chmod 755 which is more secure than 777?

You can do whatever you want. But the advice from the list is to figure out what account is actually accessing the database and keep the permissions on the DB the way they should be. That may be different for different databases.

So you have two things to figure out:
1) What is the effective user for your database accesses?
2) What permissions should be set on the database directories and files?

hth

                - Tom

 

Am Mittwoch, 30. Mai 2012 14:29:14 UTC+2 schrieb Thomas:

On 5/30/12 1:11 AM, doniyor wrote:

hey man, problem solved. i did chown www-data. .  then chmod 777 dbfile now everything is working fine. thank you so much for your time and help. 

I've lost track of the early parts of this thread, but chmod 777 on a database rarely indicates that everything is fine. The chown did not matter much once you gave everyone in the universe write access to the database.

This issue started as a permissions problem and still is a permissions problem. Figure out which user is actually accessing your database and get the permissions you need.

hth

                               - Tom

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/UOlT738Mi6gJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.