Submit

Back to the channels

#repopack

  1. * phaleth joined #repopack
  2. blue https://repopack.com/project/repopack/tasks/392
  3. blue finally closed it :)
  4. phaleth great
  5. phaleth there is something running as `npm run serve` and I don't know what that is
  6. blue where?
  7. blue that sounds like primate serve
  8. phaleth yeah, on the VPS, there is one process like that
  9. phaleth I guess I'm just gonna kill that and see which container crashes if any
  10. blue is it not inside a container?
  11. blue that's weird
  12. phaleth it is this container
  13. phaleth rpcr.io/p00000a/a000005/u000006:d00001x sh -c npm run mig... 6 weeks ago Up 14 seconds 127.0.0.1:42021->6161/tcp rp-p00000a-a000005-u6-d10-app
  14. phaleth it's the socialcloud runtime
  15. phaleth could you update the Containerfile there?
  16. blue I invited you to project
  17. phaleth ok, thanks
  18. phaleth the Containerfile has CMD ["sh", "-c", "npm run migrate:apply && npm run serve"]
  19. phaleth I will update the Containefile, looks a bit messy
  20. blue ok, thanks. also i need to update primate there
  21. blue it's like primate 0.41 or smth
  22. blue in fact, let me shortly do it
  23. phaleth and no flog
  24. blue yes, hold on, I'll fix all that
  25. blue redeploying shortly, first
  26. blue ok, deployed
  27. blue https://repopack.com/project/repopack/tasks/1017
  28. blue phaleth: excited about this
  29. phaleth clanker will be nagging that it wants to clanker
  30. blue https://repopack.com/project/repopack/tasks/1020
  31. blue this is alrady going in the directionou wanted phaleth
  32. blue phaleth: I'm gonna rename the concept of `blueprint` to `template`
  33. blue OMG phaleth
  34. blue after you submitted your changes revision, chat went BACK into action
  35. blue this is amazing!
  36. phaleth template is shorter
  37. blue good
  38. phaleth yeah, I was wondering how you were so fast :)
  39. blue dreamreal: idea: `--editor` to `rp task note` as well
  40. blue and possibly to `rp task review`, for the review text
  41. blue phaleth how do you currently write those request-changes ?
  42. blue like how I you do it multiline
  43. blue do you use the ui, rp, or rp-via-clanker?
  44. phaleth for that comment i used the web UI
  45. blue gotcha
  46. blue did you see clanker tlaking to itself on socialcloud#23?
  47. blue it's all chat :)
  48. blue chat is pretty powerful at this stage
  49. phaleth yeah, well, tell it to submit or whatever, I have more feedback
  50. blue I've turned off autoreview
  51. blue so you can review it
  52. phaleth what is .flog-bootstrap btw?
  53. blue where did you find that?
  54. blue brb
  55. phaleth anyway, I'm just gonna rewrite the Containerfile, you can merge that if clanker confirms it works
  56. blue k
  57. blue merged
  58. phaleth still failed to run
  59. phaleth maybe the way health is checked is wrong, I saw container create and container start indicators were successful there right before the healthcheck error
  60. * phaleth quit (Ping timeout: 266 seconds)
  61. * phaleth joined #repopack
  62. blue dreamreal: stacks are coming to Repopack Chat
  63. dreamreal blue: *nod* and --editor is a fine idea
  64. blue good
  65. * nevet joined #repopack
  66. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  67. * dreamreal joined #repopack
  68. blue so I've discovered a gap in Repopack Chat, which is: task chats try to execute tools (for example, flog tries to use go, then podman) and fail. I'm introducing Task compute as a primitive; for starters, this will be scoped to rp itself: `rp agent start --enable-compute`; in the future, we would be able to sell Task compute via repopack.com
  69. * lioloc quit (Server closed connection)
  70. * lioloc joined #repopack
  71. * phaleth quit (Quit: phaleth)

Search posts