Thanks everyone for the replies.
Thanks Ed, I'm glad to hear that there are more people doing it, which
means my suggestion wasn't that bad after all :-)
On Wednesday, 2 November 2016 09:37:50 UTC+10, ed wrote:
>
> an alternative to this change would be to symlink log/yourlog.log to
> /dev/nul
Thanks everyone for the replies.
Thanks Ed, I'm glad to hear that there are more people doing it.
On Wednesday, 2 November 2016 09:37:50 UTC+10, ed wrote:
>
> an alternative to this change would be to symlink log/yourlog.log to
> /dev/null
>
> $ ln -s log/production.log /dev/null
>
> I do this,
an alternative to this change would be to symlink log/yourlog.log to
/dev/null
$ ln -s log/production.log /dev/null
I do this, and it works well for me in dev mode without impact to others
sharing the repo or other environments.
On Mon, Oct 24, 2016 at 5:44 PM, Lucas Caton wrote:
> Hi there
I use them too, but at work we only write to the log if the file already
exists. So if you rm `log/test.log` it won't be written to, but if you
touch it, then you'll get logs.
On Tue, Oct 25, 2016 at 02:15:51AM +, Rafael Mendonça França wrote:
> I personally use `test.log` a lot to check the
I personally use `test.log` a lot to check the sql queries that are being
made in my test run.
Also setups using pow or any long running web server only uses the
development.log so changing this will break that setup. I can see we
disabling the boardcast, but I’d not do that by default.
On Mon, O
Hi there.
I know this, although easy, would be a big step. So I'd love to hear your
thoughts.
I can't remember the last time I needed to open/read log/development.log or
log/test.log.
This is just consuming disk space unnecessarily (my test.loge easily
reaches more than 1 GB!).
After talk
