• Venkat (2/2) Mar 17 2018 I am running a vibed app using `dub` command. But it produces no
• Venkat (7/7) Mar 17 2018 Sorry posted the above message by accident.
• rjframe (6/15) Mar 17 2018 vibe.core.log has a setLogLevel function.
• Venkat (1/1) Mar 17 2018 Thankyou.

Venkat <venkatram.akkineni gmail.com> writes:

I am running a vibed app using `dub` command. But it produces no 
logging what so ever when re

Venkat <venkatram.akkineni gmail.com> writes:

Sorry posted the above message by accident.

I am running a vibed app using `dub` command. But it produces no 
logging what so ever when requests are made. The server returns 
http error codes but it doesn't log anything to the console. How 
do I make it show me a lot more detail than it is doing now ?

For example, in a Java webapp, one would change the logging level 
to debug if a logging library is configured.

rjframe <dlang ryanjframe.com> writes:

On Sat, 17 Mar 2018 22:37:36 +0000, Venkat wrote:

 Sorry posted the above message by accident.
 
 I am running a vibed app using `dub` command. But it produces no logging
 what so ever when requests are made. The server returns http error codes
 but it doesn't log anything to the console. How do I make it show me a
 lot more detail than it is doing now ?
 
 For example, in a Java webapp, one would change the logging level to
 debug if a logging library is configured.


vibe.core.log has a setLogLevel function.

http://vibed.org/api/vibe.core.log/setLogLevel
http://vibed.org/api/vibe.core.log/LogLevel


Also, the URLRouter class has a getAllRoutes method; if needed, writing 
that to the terminal can verify the routes are what you expect.

Venkat <venkatram.akkineni gmail.com> writes:

Thankyou.