Community
Chat Logs
Saturday, November 21, 2026 (America/New_York)
- * phaleth joined #repopack
- phalethsomething is hammering repopack website since yesterday morning https://i.imageupload.app/70da58ab6eda2f139b5a.png
- * blue quit (Remote host closed the connection)
- phalethrebooting the VPS
- phalethall the traffic goes from 156.67.128.150 and actually is properly authenticated and so getting responses with 200 status
- phalethI prolly shouldn't IP ban that
- * blue joined #repopack
- phalethhi blue
- bluehi phaleth
- phaleththere's some hammering going on from rp CLI from IP 156.67.128.150, is that something you know about?
- blueyes
- phalethok, cool
- phalethI only rebooted the VPS to see if keeps going
- phalethif it keeps*
- bluemakes sense
- stagasyou mean you turned it off and on again :P
- phalethyeah, first thing to do, always
- stagasheh
- stagashttps://textlog.cc/post/3267
- nevet@stagas wrote on textlog
- phalethnice
- phalethdifficult problems solved easily
- bluehttps://repopack.com/project/repopack/tasks/991
- phalethwell, at least it shows that nodejs is easy to overload
- phalethand maybe also that the repopack API is putting too much load on the server
- phalethnot that the server cannot handle
- bluethat's not the problem, the problem is the design
- blueprimate has ws support, clanker should use instead
- phalethyeah, or just send commands in batches if possible
- bluewell, low latency is important here
- bluebut this amount of requests is too much
- phaleththere is a rate limit and clanker was prolly hitting that
- phalethlatency isn't the problem since traffic goes at most within two countries with decent network
- blueya
- phalethbut you should look at btop how nodejs memory goes up and down
- blueya
- phalethok, it's calm now
- blueyes, switched to ws
- phalethfast switch, makes it seem like as if repopack was configurable
- bluejust updated to ws transport, ya
- blueredeploying
- * stagas quit (Remote host closed the connection)
- * stagas joined #repopack
- phalethblue: I've asked clanker how to deploy app with a db on repopack, can you tell if what is suggests is about right? https://text.is/4VR4J
- phalethit suggests*
- bluephaleth: looking
- bluephaleth: https://text.is/XR9YQ
- blueyes I know, wall of text. But I got some useful improvements from this
- phalethgreat
- phalethcan clanker fix the guide I've provided and put it into documentation?
- phalethyou know this response is not great
- blueOn it phaleth.
- phalethoh, it recommends shipping a guide
- blueyes
- bluewhich I'm doing now
- phalethawesome
- phalethyeah and blueprint sounds like some deployment plan, but there is no clue anywhere how to put one together it seems
- phalethand also execute or whatever
- phalethand also that all containers/units are taken down on redeploy is strange
- phalethnot sure why the word unit was invented btw
- bluewhat's a better word than unit?
- phalethwell container is long
- blueyes, too long
- blueunit is short to type
- bluehttps://repopack.com/project/repopack/code/blob/docs/views/public/guides/app-postgres.md?ref=task%2F998-guide-deploy-a-web-app-with-private-postgresql
- bluethoughts phaleth ?
- phalethreading that atm
- bluek
- phalethit explains how to raw dog sql from node
- phalethheh
- blueyes
- bluethe guide should use primate, stupid clanker
- phalethno :D
- phalethit's actually funny how it kept node 22 and postgres 16
- blueyeah, should be node 26 and postgres 18
- phalethpostgres 19 is out
- bluedo you have an imporvements? you can post them on the chat
- blueon the timeline*
- phalethI don't seem to see what's the ending slash here supposed to do: rp app unit add myapp web --type runner --context web --containerfile Containerfile --http 3000 --public --depends db --health.http /
- blue"/ is the value of --health.http: it tells Repopack to check the web unit’s root URL on port 3000."
- phalethwell, would be nice if that explanation was there
- bluek
- phalethit's URL path essentially
- blueyes
- phalethI'd change it to /check
- phalethas the frontpage is usually too large for such purpose
- phalethbut the author of the app may of course disagree
- phalethand the check is hopefully performed only as a HEAD request
- bluerevising
- phalethok, so I may sound like I don't like openssl, but since it's only used for password generation
- phalethand may not be readily available on windows for example
- bluenobody really cares about windows
- blueor idk, do we have windows users here?
- blueI think we only have mac/linux
- phalethI suggest to use this: tr -dc A-Za-z0-9 </dev/urandom | head -c 32; echo
- phalethwhich is also not windows compatible, but who cares about windows
- phaleththe point is to get away from openssl
- phalethand use posix tools
- phalethyeah
- blueimport { createServer } from 'node:http';
- bluewhich is this nonsense
- blueshould use @rcopmat/http
- blueI'm furious
- bluealso server.mjs.. jesus
- phalethod -An -v -N 32 -t x1 /dev/urandom | tr -d '[:space:]'
- phaleththat is nice one
- blueI don't know what all this nonsense means
- blueod ?
- bluewth is od?
- phalethman od
- blueguide is revised with rcopmat
- phalethok, let me see
- blueimport postgres from "postgres";
- blueshould use @primate/postgresql instead :(
- phalethbut does that let it rawdog sql statements?
- * phaleth thinks that's the best part of the guide
- blueyes
- bluedb.sql("")
- phalethok, cool
- blueI wonder if for @rcompat/env, it makes sense to have a few specialised getters
- bluelike env.getNumber and env.getBoolean
- phalethok, so last thing is postgres 19 and then it's great I think
- phalethI will have to try tomorrow
- blueseems cleaner than this nonsense: Number(env.get("PORT")). also can verify that it's parsable
- bluek
- phalethno, don't typecheck env vars, waste of time
- phaleththey are supposed to be hacky
- phalethrcompat api looks nice
- bluercompat api is amazing, yes
- phalethanyway, more than good enough, thank you
- blueit's merged phaleth
- blueI'm gonna redeploy the docs-prod app
- phalethok
- * phaleth quit (Quit: phaleth)