luminus 2020-03-06

I don't have the context of the question, but it's probably to avoid storing passwords in source control. Also if you're working on a team, every dev may have some different configuration relative to their system. (let me know if I'm way off with this answer)

So when you get an exception. how does one see the exception. im looking for the logs etc but i cant find how to get the details of the exception

do you have an example you'd like to go through together?

so im following the book

you get the swagger part

if i miss something swagger says 500 Exception

now say i want to see the trace for that exception so i can look into what happened

how can i get that printed to the log?

I already figured out what the problem was. However i would like to know how i can get exceptions printed either in the repl or even better to the log file

ok, I see what you mean. but I cannot imagine why you would not see exception in repl.

I mean, when using "lein repl" the config is there for you, and it should just work... not like you have to do something for that

there is the log directory at the root of the project, do you not have that

yeah. but the exception didnt get printed

and your log config file is env/dev/resources/logback.xml

500 is internal server exception. I guess it is not being caught and therefore not printed out

makes sense