Community
Chat Logs
Tuesday, February 17, 2026
- chovysurrealdb just launched 3.0. or as i like to call it "Fuck The Developer 2"
- bluechovy: then it's good I dropped support for surrealdb in the last version :)
- chovyhonestly, i don't know anything but us who used it
- chovydo you support supabase? everyone i see is using it now
- bluechovy: not that I know of. I don't even know what supabase is
- bluesupabase sounds more like an api than a db
- chovyits a firebase-like layer ontop of postgres
- chovyits awesome. i have like 19 projects on it right now
- chovywould definitely add official support for primate if i were you
- chovyyou can either self host it or use their cloud version for $10/db
- blueprimate already supports postgres. if it's just a matter of connecting to a remote server, that's already doable
- bluealso, calling a db over an API sounds like a version of hell
- * dreamreal glares at dynamodb
- bluedreamreal: wth is THAT
- bluedreamreal: https://github.com/primate-run/primate/issues/248
- 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")
- dreamrealdynamodb
- 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
- dreamreal... also worth noting: it's acceptable that a READ takes place a month after being issued.
- phalethhi blue, was the deployment website process all the same as usual?
- phalethdeployment of website*
- bluephaleth: yes
- bluealso hi
- bluephaleth: https://github.com/primate-run/primate/issues/248
- 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")
- phalethok, at least that
- phalethanyway, I redeployed the website to use node as runtime again, bun was taking too much memory
- blueright
- blueI need to set up a script for openapi.primate.run
- blueI don't have the docker file anymore, and the docs different from what's deployed :(
- phaleththe openapi source is not buildable, been that way for quite some time
- phalethnot sure which dockerfile you mean
- phalethyou can take a look at nspawn/containers/openapi.md in the provision repo
- phalethhmm, for some reason the openapi container has a wrong ip address
- blueyes. it refers to /app, and currently the openapi container is from /var/www
- blueI think I need to create it completely anew
- phalethwhat is the url for the json? https://openapi.primate.run/manifest.json?
- phalethyeah, it's broken
- bluehm? it wored just earlier today
- bluedid you change anything
- phalethnope, but now it has wrong IP
- phalethtrying to fix that
- blueoh
- phalethhmm, it's not really an nginx container
- phalethit looks like primate repo is deployed in that openapi container, weird
- phalethlooks like the only option is to rebuild the container, which should fail
- blueya
- blueit should be a static container that serves `generated` from that repo
- blueI'm not sure why the git repo is actually inside the container
- phalethactually, it works https://openapi.primate.run/manifest.json
- bluenice, how to redeploy?
- bluedreamreal: https://openapi.primate.run/spec/bytenews.json
- phalethyeah, well, sometimes it does not build so need to retry
- phalethweird
- bluedo you have a script for it?
- blueI got many containers scripted, but not this one
- phalethto redeploy you gotta follow all the steps in nspawn/containers/openapi.md in provision repo in our gitea
- phalethI've just updated the container file, if the build fails then simply retry
- blueah, where is the containerfile?
- phalethin nspawn/containers/openapi.md in provision repo in our gitea
- blueah ok
- blueif you're not updating the gh one, can I delete it?
- bluethat way I don't accidentally go there and see old stuff
- phalethyeah, sure
- phaleththat one is too old by now
- bluedone, deleted
- blueanything else I need to delete?
- blueprovisor-cli-wrapper, docs, website, orglist, provisor-zig-fail, nginx-old-cfg
- blueif you don't need anything, I'll delete all of them
- blueI'll leave the repopack org to retain the name, but not have any repos there
- blueI mean I'll leave it in place and not delete it
- phalethnginx-old-cfg can still be useful, but the rest can be wiped out from the face of the earth
- phalethI think the map cache trick in that nginx config is really cool and confusing at the same time, but it works
- bluedone, all deleted aside from that one
- phalethnode 25 is still not LTS, that is strange
- phalethI think they still consider odd number versions not be well just odd and not LTS