Have a component that prints out where the server starts, so it gets printed when the system starts, rather than when main is called. This adds an info line to how to connect to your application, even when main isn't called (eg, starting from the repl, in dev mode).
Not against a redirect, but I feel like there should be some sort of print line in any environment.
This might be overkill - we could alternatively just print in an overridden (go) function, or something of that nature, but this ensures that we print the message every time the system is started.
I've put it in for now, we can always iterate on this. It does mean the template is getting more bulky, but it reinforces the pattern of having extra components which is good.
Have a component that prints out where the server starts, so it gets printed when the system starts, rather than when main is called. This adds an info line to how to connect to your application, even when main isn't called (eg, starting from the repl, in dev mode).
Not against a redirect, but I feel like there should be some sort of print line in any environment.
(Partially) Addresses the first point brought up on the mailing list.
This might be overkill - we could alternatively just print in an overridden
(go)
function, or something of that nature, but this ensures that we print the message every time the system is started.