|
Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ Set by moderator on 24 December 2017. |
|||
|
02:59
ilbot3 joined
|
|||
| moderator | Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ | ||
|
12:34
lizmat joined
12:39
lizmat joined
14:52
lizmat joined
17:51
FROGGS joined
|
|||
| FROGGS | hi! | 17:55 | |
| are the cro (micro?)services are meant to be managed by another service? | 17:56 | ||
| like, (re)spawning processes on demand and other stuff | 17:57 | ||
| another question: get -> 'js', *@path { static 'static/js', @path } | 18:06 | ||
| is this safe? | |||
| what if I request "GET /js/../../../etc/passwd" ? | 18:07 | ||
| what does cro stand for? | 18:10 | ||
| lizmat | personally, I like the idea it's short for Cro Magnon (en.wikipedia.org/wiki/Cro-Magnon) :-) | 18:31 | |
| timotimo | FROGGS: of course that is safe :) | 18:32 | |
| cro comes from how you'd write "my Cro::Service $foo .= new: ..." in your code | 18:33 | ||
| lizmat | .oO( micro-service ) |
18:35 | |
| FROGGS | lol | 18:38 | |
| I see | |||
| jnthn | FROGGS: Yes, `static` uses the IO::Path::ChildSecure module to avoid such attacks | 20:20 | |
| Ah, and on other question: yes, setting something up that runs/restarts them is probably sensible. So far I've deployed stuff in containers and left that task to Kubernetes. | 21:07 | ||