Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logs in wrong place #9

Open
drmike opened this issue Jun 13, 2011 · 3 comments
Open

Logs in wrong place #9

drmike opened this issue Jun 13, 2011 · 3 comments

Comments

@drmike
Copy link

drmike commented Jun 13, 2011

Just noticed that a log directory is created alongside the domain directory.

Shouldn't we be using whatever directory nginx is already using for storing the logs? Is there a way to detect for that?

Plus it's in the /var/www/ directory. Not sure if we want to place those logs where Nginx can access. I would think that would be a security issue.

@xeoncross
Copy link

The www directory should be owned by root. Each site is created in a www/sub.tld directory so there is no worry about some script reading the log files. However, it's totally up to the user where they want the log folder. By default I like each site's log separate so I just create a matching log folder near the site directory for ease.

@drmike
Copy link
Author

drmike commented Jun 20, 2011

We're going to disagree then. Logs need to be in one place, not two.

Why not just put them in /var/logs/nginx/$domain with the other nginx logs?

@xeoncross
Copy link

If you think people would prefer them in /var/logs/nginx/$domain I'll change it. Like I said, it doesn't matter too much to me. I just want them separated by site.

peterdorsi referenced this issue in peterdorsi/lowendscript May 15, 2013
Adding menu option for MOTD and LOCALE subroutine
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants