ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Sunday, July 12, 2026

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