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

Request: do not reset/clear the console output #794

Closed
veqryn opened this issue Sep 28, 2016 · 6 comments
Closed

Request: do not reset/clear the console output #794

veqryn opened this issue Sep 28, 2016 · 6 comments

Comments

@veqryn
Copy link

veqryn commented Sep 28, 2016

My team runs this create-react-app as a single process inside docker, in order to host and build our web site (dev version).

It runs beside many other containers, such as the backend api server and our database.

When running docker (such as using docker-compose up), we get the output of all our container's stdout, which is normally great as we can see any activity as we test and use the app in development.

However, create-react-app resets/clears the console several times, effectively deleting from my screen every other container's output up until that point.

Is there a way to not reset/clear the screen or a workaround?

@gaearon
Copy link
Contributor

gaearon commented Sep 30, 2016

Is there any way for us to determine when the output is being piped like this?

@veqryn
Copy link
Author

veqryn commented Oct 1, 2016

I was going to saw I didn't think so, but some googling sort of says yes:
http://stackoverflow.com/questions/911168/how-to-detect-if-my-shell-script-is-running-through-a-pipe

@marekciupak
Copy link

marekciupak commented Nov 29, 2016

Is there a way to fix that problem for https://github.com/ddollar/foreman gem? cc: #1032

@gaearon
Copy link
Contributor

gaearon commented Nov 29, 2016

Was this fixed on master by #1032?

@marekciupak
Copy link

Yes, it was fixed. Thanks!

@gaearon
Copy link
Contributor

gaearon commented Nov 29, 2016

Closing. The fix will be out in the next release (0.8.0).

@gaearon gaearon closed this as completed Nov 29, 2016
@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants