|
Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ Set by moderator on 18 March 2018. |
|||
|
02:57
ilbot3 joined
|
|||
| moderator | Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ | ||
|
04:41
ccra joined
09:03
Andiidnajc joined
10:48
Geth joined
10:52
scovit joined
|
|||
| japhb | Can haz 0.7.4 and website docs refresh? (Otherwise zef sees nothing new and I have to use github to read the updated docs) | 16:53 | |
| jnthn | I can do a 0.7.4 in the coming days; I've still a small refactor to the router I want to get in, to allow for a little more flexibility for router plugins | 16:55 | |
| japhb | Fair enough. | ||
| I guess when you do version updates, the dockerfiles need an update -- which means the stub template needs an update at github.com/croservices/cro/blob/ma...mon.pm6#L5 , which means the cro release is now out of date ... can that circularity be broken easily? | 16:59 | ||
| jnthn | No | ||
| The release script just bumps it during the release process to the version we're releasing | |||
| japhb | Ah, OK, so just "release everything as closely as possible" | 17:00 | |
| jnthn | And the docker container production is scripted, but there's a bit of lag between upload to CPAN and packages being available | ||
| So there can be a moment where somebody grabs a very fresh release, stubs a new project, and does docker build and gets an error | |||
| japhb | nodnod | 17:01 | |
| jnthn | That's not awesome, but it seems the least bad alternative | ||
| japhb | yeah | ||
| jnthn | If we have an active enough userbase that this becomes a FAQ, I guess that's a nice problem :P | ||
| japhb | Heh, agreed | ||
| jnthn | But yeah, since release is mostly scripted and container build/push is scripted, hopefully that interval can be kept small | 17:02 | |
|
19:09
FROGGS joined
|
|||
| japhb | Was preparing to update the react-redux-spa template to know about the docker work -- discovered that the rakudo-star image is made from an old enough version of buildpack-deps that it has an ancient nodejs and no local npm package. | 21:49 | |
| With some searching, discovered that buildpack-deps:sid-scm seems like it might be recent enough. Currently building a rakudo-star-sid and cro-http-websocket-sid to see if that's enough to get a working run-the-stub experience. | 21:50 | ||
| jnthn | japhb++ | ||
| japhb | Although I've got to say the concept of building Rakudo Star (designed to be stable) on top of Debian sid is a little weird. | 21:51 | |
| W00t, it worked. Now the question is, how do we want to actually make this available to users? We might be able to get a tag of rakudo-star that is built with a different base distro each time, and then I suppose we'd need to reflect that in the available croservices/docker images, so that the stub code can run from those. | 22:13 | ||
| Alternately, I can change the react-redux-spa stub code Dockerfile to build it all locally, starting with buildpack-deps:sid-scm and replicating Rakudo Star and cro-http-websocket on top of that before doing the main template commands. | 22:15 | ||
| jnthn: Thoughts? | |||
| jnthn | tbh, I'd probably look to see if there's a repository available with a newer node package, and install that | 22:20 | |
| There's already been a "can we have alpine too" request; I'd rather the containers we try to provide don't multiply out too far | 22:21 | ||
|
23:45
LAQG1Dkimmyk joined
|
|||
| japhb | Nodnod | 23:52 | |