# Can we remove extra cruft from build logs?

**URL:** https://meta.discourse.org/t/can-we-remove-extra-cruft-from-build-logs/54309
**Category:** Feature
**Created:** [2016年十二月15日 17:17 UTC](https://meta.discourse.org/t/can-we-remove-extra-cruft-from-build-logs/54309 "2016-12-15T17:17:29Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [2016年十二月15日 17:17 UTC](https://meta.discourse.org/t/can-we-remove-extra-cruft-from-build-logs/54309/1 "2016-12-15T17:17:29Z")

</div>

> [@Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/set-up-https-support-with-lets-encrypt/40709/250):
>
> What does
> 
> less /var/discourse/shared/standalone/log/var-log/nginx/error.log
> 
> says?

It has several hundred lines of text, most of which mean nothing. If there is an error, to most people, it looks just like the ones helpfully saying “oh, everything is great! I compressed a file!”

Is there a way to reduce the output?

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2016年十二月15日 17:40 UTC](https://meta.discourse.org/t/can-we-remove-extra-cruft-from-build-logs/54309/2 "2016-12-15T17:40:02Z")

</div>

> [@pfaffman](#):
>
> less /var/discourse/shared/standalone/log/var-log/nginx/error.log

Not following. The `error.log` of a working new install is empty.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [2016年十二月15日 17:47 UTC](https://meta.discourse.org/t/can-we-remove-extra-cruft-from-build-logs/54309/3 "2016-12-15T17:47:29Z")

</div>

Ooops. Apparently I can’t pay close attention when reading on a handheld device. The nginx logs are not example of what I’m talking about.

I’m talking about when you do a `./launcher build app` there are hundreds of lines of stuff that flies by, most of which is meaningless. If there is an error in the build, you get an error at the bottom that says “Well, something went wrong. It could be anywhere in the vast number of lines that just scrolled by.”

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2016年十二月15日 23:11 UTC](https://meta.discourse.org/t/can-we-remove-extra-cruft-from-build-logs/54309/4 "2016-12-15T23:11:26Z")

</div>

Not really, no. Maybe search for the word “error”.