Do not display previous logs when starting the server

[Kocal]

I've always found it annoying to not being to see on what URLs your project is available, because of tons of logs you see when booting the server, each time I have to scroll-up to know what URLs to use:

Enregistrement.de.l.ecran.2025-08-03.a.13.27.11-2.mov

When booting a server, I don't really care about logs from a previous symfony serve, the most important things must be visible:

1. the two different warnings about "The local web server is optimized for local development..." and "that the Symfony CLI only listens on 127.0.0.1 by default"
2. the URLs where I can access my app

Do you think never displaying logs from a previous session could be possible?

Thanks!

[tucksaun]

Not sure it would be really easy because of the asynchronous nature of this part of the code 🤔

In the meantime, would the usage of symfony open:local help you in your use case?

[tucksaun]

Looking back at the code, I now remember why we have some logs shown in such a case.
We used (a long time ago) to clear the logs when the processes are stopped, but we don't anymore because this does not make error logs available for introspection.
Additionally, we tail 10 lines on existing logs because when we start the tailing process, the process we want to monitor might have already started writing logs that we need to show.

I have to think about what we can do about all this.

Does anyone have an idea ?

[Kocal]

In the meantime, would the usage of symfony open:local help you in your use case?

Yes it could, but I usually run the web-server through symfony serve, in foreground (allowing me to easily kill it without having to type another command), which would requires to open a new terminal and type symfony open:local.

Additionally, we tail 10 lines on existing logs because when we start the tailing process, the process we want to monitor might have already started writing logs that we need to show.

That's a fair point. But since logs have a date-time, maybe we could not display logs written before running the command? If I look back to my video, I can see ~20 lines that are not useful and could be removed:

Is it something doable?

[tucksaun]

That makes me think: what about introducing a `—open` flag to `server:start` that would open the URL once the server started?

…

On Fri 19 Sep 2025 at 07:45, Hugo Alliaume ***@***.***> wrote: *Kocal* left a comment (symfony-cli/symfony-cli#639) <#639 (comment)> In the meantime, would the usage of symfony open:local help you in your use case? Yes it could, but I usually run the web-server through symfony serve, in foreground (allowing me to easily kill it without having to type another command), which would requires to open a new terminal and type symfony open:local. Additionally, we tail 10 lines on existing logs because when we start the tailing process, the process we want to monitor might have already started writing logs that we need to show. That's a fair point. But since logs have a date-time, maybe we could not display logs written before running the command? If I look back to my video, I can see ~20 lines that are not useful and could be removed: image.png (view on web) <https://github.com/user-attachments/assets/b355b2ec-42a8-477a-8c17-19fb05d247c9> Is it something doable? — Reply to this email directly, view it on GitHub <#639 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGUNZQSB25QSPE2ULPZBSL3TOKBPAVCNFSM6AAAAACC736UICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJQGY4DEMZXGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[Kocal]

It could be interesting yes, looks like it feasible with https://pkg.go.dev/github.com/pkg/browser#OpenURL

[tucksaun]

We should already have everything we need thanks to the `open:local` command

…

Message ID: ***@***.***>