Proposal: Simplified Log Access & Tailing with a Sail Commands

[TalAter]

I would love to see a way to easily read and tail logs inside a ⛵Sail container. This can improve the developer experience and aligns with Sail's philosophy of simplifying Docker's complexity for Laravel developers.

I can imagine a number of new Sail commands such as:

sail log
sail log:laravel
sail log:laravel --file=api_requests.log
sail log:docker

The above examples would translate to something like:

docker logs --follow <container>
docker exec -t <container> tail -f /var/www/html/storage/logs/laravel.log
docker exec -t <container> tail -f /var/www/html/storage/logs/api_requests.log
docker logs --follow <container>

Notes:

• sail log (or a possible alias sail log:docker) could be a helpful way to view the logs written to STDOUT and STDERR when sail is running in detached mode.
• sail log:laravel can allow an easy way to peer into Laravel's logs without having to exec or ssh into the container
• sail log:laravel --file=filename can let you view other logs saved in storage/logs
• sail log:laravel can perhaps use Pail if it is installed and support passing options to it (e.g., level, message, filter, etc.)
• My above suggested implementation defaults to always tail and follow (i.e., tail -f) as that seems to be the most common behavior when viewing logs in a development environment. Additional options to sail log can be added to view entire logs instead of just the tail, tail without following, etc.

If this is interesting, I would love to discuss more, flesh the API a bit more, and then start working on an implementation.