|
00:18
Pe_Elle left
00:32
Pe_Elle joined
00:48
Pe_Elle left
00:49
Pe_Elle joined
00:50
Pe_Elle left
00:52
Pe_Elle joined
11:08
Pe_Elle joined
11:12
Pe_Elle left
11:13
Pe_Elle joined
11:17
Pe_Elle left
11:54
Pe_Elle joined
12:56
Pe_Elle left
13:28
Pe_Elle joined
14:34
Pe_Elle left
15:03
Pe_Elle joined
15:08
Pe_Elle left
15:23
Pe_Elle joined
15:59
Pe_Elle left,
Pe_Elle joined
16:51
Pe_Elle left
17:07
Pe_Elle joined
17:12
Pe_Elle left
17:17
xinming joined
|
|||
| xinming | Anyone here has good ways to auto restart cro service so it can be easiier for doing developement please? | 17:18 | |
|
17:42
Pe_Elle joined
17:48
Pe_Elle left
|
|||
| patrickb | not entirely sure, but I think the "cro" tool can do that | 17:57 | |
|
18:18
Pe_Elle joined
19:20
Pe_Elle left
|
|||
| coleman | if you need to run a more elaborate script, try entr eradman.com/entrproject/ | 19:20 | |
| but I do think the cro tool does have a hot reload mode for template updates. I haven't used it for a while though | 19:21 | ||
| it was a part of docs.raku.org before we went all-static | |||
|
19:34
Pe_Elle joined
|
|||
| melezhik. | Yes cro app when runs in dev mode does hot reload on changes in any file | 19:58 | |
|
20:36
Pe_Elle left
|
|||
| xinming | Ok, thanks, I lost cro cli for a long while, and now, when I create project, I copy the skeleton to other folder, and rename modules. | 20:41 | |
|
21:06
Pe_Elle joined
21:10
Pe_Elle left
21:25
Pe_Elle joined
22:06
coleman left
22:07
coleman joined
22:26
Pe_Elle left
22:48
coleman left,
coleman joined
22:53
Pe_Elle joined
22:57
Pe_Elle left
23:13
Pe_Elle joined
23:39
Xliff joined
|
|||
| Xliff | Hello! | 23:39 | |
| I'm trying to see if I can act on Cro internal exceptions when I am running a Cro server. Say an exception of type X::Cro::HTTP::Router::OnlyInHandler is thrown. Is there any way for me to act on that at the application level? | 23:40 | ||
| Near as I can tell, it looks like Cro handles those internally and I can't even get a notice that such has occurred at the application logic level. | 23:41 | ||
| *SMACK* -- there is Cro::UnhandledErrorReporter.... thanks anyways! | 23:44 | ||