ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Sunday, July 12, 2026

  1. bluehi phaleth
  2. blueprimate 0.40 will be out today, god willing :P
  3. phalethhi blue
  4. bluehi
  5. phalethok, anything useful for repopack there?
  6. blueyes. almost all of it is for repopack. async schemas, collocated route pages, and a few other small things
  7. bluemost of the things will allow us to reduce repetition and code in repopack
  8. bluebtw, I did some speed tests yesterday on primate-web.repopack.app
  9. blueso in frankfurt the load time is 100ms, london 300ms, but it gets higher to around 1s in washington d.c. and highest is sydney, 3s
  10. bluewe need to start things of regions at some point
  11. bluestart thinking*
  12. phalethnice
  13. phalethheh, yeah, thinking big
  14. phalethfreebsd should make things faster, the interwebz will be like "oh, I communicate with a freebsd server, huh, I better go fast"
  15. blueexactly
  16. blueno more this linux nonsense
  17. phalethfreebsd images seem to be quite large
  18. blueyeah, they pack a lot of stuff inside
  19. bluesuperarch is supposed to reduce that
  20. phalethyeah, luckily image layers are re-usable
  21. bluetrue
  22. phalethyo big error
  23. phalethblue: I've tried to deploy the repopack site on freebsd https://upaste.de/raw/9ib
  24. phalethpostgres also looks problematic
  25. bluephaleth: wow
  26. phalethheh
  27. phalethgotta try linux containers
  28. blueheh
  29. blueanyway, I'm preparing the 0.40 release
  30. blueit's almost done, then I can update RP
  31. phalethok
  32. phalethI'm building podman from source in a VBox VM, it's taking forever
  33. bluewhy are you doing that?
  34. phalethjust to see what I get
  35. bluek
  36. phaleththe pkg for podman on freebsd is little bit dated, but not too bad
  37. bluewe'll fix that in superarch
  38. blueno more dated nonsense, just rollin' all the way to the bank
  39. blueoh man we really need to move the primate website to repopack finally. doing it manually kills me
  40. bluethis is the first thing I'm gonna do when RP goes beta
  41. blueI just wanna hit a button, or better, do it automatically on commits
  42. phalethit's like 3 commands?
  43. blueyes but it's 3 commands I have to remember and/or write somewhere
  44. blueI don't do it that often so it's just opening a new tab in tmux and just hitting the up arrow
  45. blueprobably should put it into a script and be done with it
  46. blueoh great, it's not in the history anymore :(
  47. blueI guess it's time to look at the irc logs
  48. phalethheh, no
  49. blueah, found it
  50. phalethcurl --silent -X POST \
  51. phaleth "http://127.0.0.1:8080/v1.0/libpod/local/build?t=localhost/primate-site-runtime&localcontextdir=/opt/podman/primate-site/runtime&nocache=true"
  52. phalethsudo podman stop 000000-primate-site-runtime && sudo podman rm 000000-primate-site-runtime
  53. phalethsudo podman run --detach --name=000000-primate-site-runtime --runtime=runsc --network=000000-primate-site \
  54. phaleth --publish=127.0.0.1:24430:6161 --cpus 1 --oom-score-adj -1000 --restart=always localhost/primate-site-runtime
  55. bluethanks
  56. phalethok, it started building golang from source, when is it gonna build podman
  57. bluenext week
  58. phalethprolly never
  59. blueyeah, I think I messed up something
  60. phalethlet me check
  61. blueI ran the commands you provided, now it's 503 service unavailable
  62. phalethok
  63. bluefyi the script is website.sh, I put it under /tmp/website.sh for reference
  64. phalethit's a deno error
  65. bluedeno error?
  66. blueoh
  67. blueI did remove something from the primate config
  68. bluenvm
  69. blueI'll fix it
  70. phalethok, so primate website is configured to listen on localhost instead of 0.0.0.0
  71. bluethe problem is, our manual deploy doesn't inject HOST=0.0.0.0
  72. phalethyeah
  73. bluerepopack does that, maybe I'll just see how it does that and see if I can backport it
  74. phalethrepopack website has env file
  75. blueno no
  76. blueI mean
  77. bluewhen repopack deploys stuff, it injects HOST=0.0.0.0
  78. blueso on repopack, when I deploy the primate web, it just works
  79. blueI removed that code from primate website too early
  80. blueI'll put it back, the explicit { http: { host: "0.0.0.0" } }, for now
  81. bluedone, redeploying wiht website.sh
  82. phalethno hurry https://primate.run/
  83. phalethI deployed old image
  84. bluehttps://primate.run/blog/primate-040
  85. bluehere we go
  86. skillnews12Primate 0.40: Route pages, store enums, async schemas and events - https://primate.run/blog/primate-040
  87. bluedreamreal: ^
  88. bot[Primate Blog] Primate 0.40: Route pages, store enums, async schemas and events - https://primate.run/blog/primate-040
  89. phalethlooks like I can combine freebsd and linux images in one Containerfile
  90. blueLOL
  91. phalethnode gets stuck in infinite loop when container is running from linux image
  92. phalethsame for bun
  93. phalethok, so the thing is that repopack website only runs on bun
  94. phaleththe huge error I posted earlier was node specific, not freebsd specific
  95. blueoh ok, interesting
  96. bluebut yeah, repopack itself runs on bun currently
  97. phalethI've redeployed the repopack website to the rust based bun and it seems to work fine
  98. phaleththe date on the blogpost for primate 0.40 should be today's 12th July