ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Tuesday, February 17, 2026

  1. * nevet joined #primate
  2. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  3. chovysurrealdb just launched 3.0. or as i like to call it "Fuck The Developer 2"
  4. bluechovy: then it's good I dropped support for surrealdb in the last version :)
  5. chovyhonestly, i don't know anything but us who used it
  6. chovydo you support supabase? everyone i see is using it now
  7. bluechovy: not that I know of. I don't even know what supabase is
  8. bluesupabase sounds more like an api than a db
  9. chovyits a firebase-like layer ontop of postgres
  10. chovyits awesome. i have like 19 projects on it right now
  11. chovywould definitely add official support for primate if i were you
  12. chovyyou can either self host it or use their cloud version for $10/db
  13. blueprimate already supports postgres. if it's just a matter of connecting to a remote server, that's already doable
  14. bluealso, calling a db over an API sounds like a version of hell
  15. * dreamreal glares at dynamodb
  16. bluedreamreal: wth is THAT
  17. bluedreamreal: https://github.com/primate-run/primate/issues/248
  18. nevetblue mentioned url: https://github.com/primate-run/primate/issues/248 ("Proposal: route schema API for typed validation and OpenAPI generation 路 Issue #248 路 primate-run/primate")
  19. dreamrealdynamodb
  20. nevetDynamo is an AWS document database that guarantees eventual consistency. That means it usually responds within a short amount of time... but there are no guarantees. It's fully acceptable that a write takes place after a month of being issued. Good luck out there! URL: https://aws.amazon.com/dynamodb/ See also: virtually anything else
  21. dreamreal... also worth noting: it's acceptable that a READ takes place a month after being issued.
  22. * phaleth joined #primate
  23. * phaleth joined #primate
  24. phalethhi blue, was the deployment website process all the same as usual?
  25. phalethdeployment of website*
  26. bluephaleth: yes
  27. bluealso hi
  28. bluephaleth: https://github.com/primate-run/primate/issues/248
  29. nevetblue mentioned url: https://github.com/primate-run/primate/issues/248 ("Proposal: route schema API for typed validation and OpenAPI generation 路 Issue #248 路 primate-run/primate")
  30. phalethok, at least that
  31. phalethanyway, I redeployed the website to use node as runtime again, bun was taking too much memory
  32. blueright
  33. blueI need to set up a script for openapi.primate.run
  34. blueI don't have the docker file anymore, and the docs different from what's deployed :(
  35. phaleththe openapi source is not buildable, been that way for quite some time
  36. phalethnot sure which dockerfile you mean
  37. phalethyou can take a look at nspawn/containers/openapi.md in the provision repo
  38. phalethhmm, for some reason the openapi container has a wrong ip address
  39. blueyes. it refers to /app, and currently the openapi container is from /var/www
  40. blueI think I need to create it completely anew
  41. phalethwhat is the url for the json? https://openapi.primate.run/manifest.json?
  42. phalethyeah, it's broken
  43. bluehm? it wored just earlier today
  44. bluedid you change anything
  45. phalethnope, but now it has wrong IP
  46. phalethtrying to fix that
  47. blueoh
  48. phalethhmm, it's not really an nginx container
  49. phalethit looks like primate repo is deployed in that openapi container, weird
  50. phalethlooks like the only option is to rebuild the container, which should fail
  51. blueya
  52. blueit should be a static container that serves `generated` from that repo
  53. blueI'm not sure why the git repo is actually inside the container
  54. phalethactually, it works https://openapi.primate.run/manifest.json
  55. bluenice, how to redeploy?
  56. bluedreamreal: https://openapi.primate.run/spec/bytenews.json
  57. phalethyeah, well, sometimes it does not build so need to retry
  58. phalethweird
  59. bluedo you have a script for it?
  60. blueI got many containers scripted, but not this one
  61. phalethto redeploy you gotta follow all the steps in nspawn/containers/openapi.md in provision repo in our gitea
  62. phalethI've just updated the container file, if the build fails then simply retry
  63. blueah, where is the containerfile?
  64. phalethin nspawn/containers/openapi.md in provision repo in our gitea
  65. blueah ok
  66. blueif you're not updating the gh one, can I delete it?
  67. bluethat way I don't accidentally go there and see old stuff
  68. phalethyeah, sure
  69. phaleththat one is too old by now
  70. bluedone, deleted
  71. blueanything else I need to delete?
  72. blueprovisor-cli-wrapper, docs, website, orglist, provisor-zig-fail, nginx-old-cfg
  73. blueif you don't need anything, I'll delete all of them
  74. blueI'll leave the repopack org to retain the name, but not have any repos there
  75. blueI mean I'll leave it in place and not delete it
  76. phalethnginx-old-cfg can still be useful, but the rest can be wiped out from the face of the earth
  77. phalethI think the map cache trick in that nginx config is really cool and confusing at the same time, but it works
  78. bluedone, all deleted aside from that one
  79. phalethnode 25 is still not LTS, that is strange
  80. phalethI think they still consider odd number versions not be well just odd and not LTS