Problem to Solve
Knowing when the server has actually started, and the port that we are listening to (in case we changed it from the default one) is hard to know currently.
This is not an actual issue, but it would be a "nice to have" feature
Proposal
Just like the echo framework in go does, relic could print a "starter" banner and the listening port in the terminal
echo's banner and port look like this:
Personally I would go for something simpler (without a subtitle and a link)
____ ________ __________
/ __ \/ ____/ / / _/ ____/
/ /_/ / __/ / / / // /
/ _, _/ /___/ /____/ // /___
/_/ |_/_____/_____/___/\____/ v1.0.0
=> http server started on :8080
I generated the banner here: https://patorjk.com/software/taag/#p=display&f=Slant&t=RELIC&x=none&v=4&h=4&w=80&we=false
Of course, users should also have the option to hide/avoid these logs
Use Case
Alternatives
Additional context
No response
How experienced are you with this library?
None
Are you interested in working on a PR for this?
Problem to Solve
Knowing when the server has actually started, and the port that we are listening to (in case we changed it from the default one) is hard to know currently.
This is not an actual issue, but it would be a "nice to have" feature
Proposal
Just like the echo framework in go does, relic could print a "starter" banner and the listening port in the terminal
echo's banner and port look like this:
Personally I would go for something simpler (without a subtitle and a link)
____ ________ __________ / __ \/ ____/ / / _/ ____/ / /_/ / __/ / / / // / / _, _/ /___/ /____/ // /___ /_/ |_/_____/_____/___/\____/ v1.0.0 => http server started on :8080I generated the banner here: https://patorjk.com/software/taag/#p=display&f=Slant&t=RELIC&x=none&v=4&h=4&w=80&we=false
Of course, users should also have the option to hide/avoid these logs
Use Case
Alternatives
Additional context
No response
How experienced are you with this library?
None
Are you interested in working on a PR for this?