Arnaud Castellanos Galea

Error: TorchBear needs an app to run. Change to the directory containing your application and run torchbear again.

This should be IMO the default behaviour of actix_lua's on_lua method, instead of running the passed code on every handle it should that once and use the returned function as...

The [init file](https://github.com/foundpatterns/torchbear/blob/6a3c851a69edb489141c6fbc9488fed7e68a0591/src/lib.rs#L108) should return [a function](https://github.com/foundpatterns/torchbear/blob/6a3c851a69edb489141c6fbc9488fed7e68a0591/src/lib.rs#L111) and [that function](https://github.com/foundpatterns/torchbear/blob/6a3c851a69edb489141c6fbc9488fed7e68a0591/src/lib.rs#L113-L115) be used as the [handler](https://github.com/foundpatterns/torchbear/blob/5f719b153a43449ddd6104b7362da0b88b4e5617/src/handlers/web_server.lua#L11) for actix requests. (It's fixed already)

https://github.com/foundpatterns/torchbear/issues/53

read file is in the lua standard io library it's not crazy to have them separated, some languages have separate libraries for io (read/write file content) and filesystem (directories and...

When logging everything (with the log-scope option), log as well which module logged which messages.

Change the date to be gray and the log level to be colored like in https://github.com/rxi/log.lua

log the same levels on the terminal and in the files (currently terminal logs whatever passed as the option level and files only log info)

Fixed by https://github.com/foundpatterns/torchbear/commit/afe0cde2ad2f04873d248cf819a0033460c93a06, the next step is print it in lua after #81

The logging support is provided by rust's [log crate](https://crates.io/crates/log), it only supports the currently implemented levels