Submit

Back to the channels

#repopack

  1. phaleth something is hammering repopack website since yesterday morning https://i.imageupload.app/70da58ab6eda2f139b5a.png
  2. phaleth rebooting the VPS
  3. phaleth all the traffic goes from 156.67.128.150 and actually is properly authenticated and so getting responses with 200 status
  4. phaleth I prolly shouldn't IP ban that
  5. phaleth hi blue
  6. blue hi phaleth
  7. phaleth there's some hammering going on from rp CLI from IP 156.67.128.150, is that something you know about?
  8. blue yes
  9. phaleth ok, cool
  10. phaleth I only rebooted the VPS to see if keeps going
  11. phaleth if it keeps*
  12. blue makes sense
  13. stagas you mean you turned it off and on again :P
  14. phaleth yeah, first thing to do, always
  15. stagas heh
  16. stagas https://textlog.cc/post/3267
  17. nevet @stagas wrote on textlog
  18. phaleth nice
  19. phaleth difficult problems solved easily
  20. blue https://repopack.com/project/repopack/tasks/991
  21. phaleth well, at least it shows that nodejs is easy to overload
  22. phaleth and maybe also that the repopack API is putting too much load on the server
  23. phaleth not that the server cannot handle
  24. blue that's not the problem, the problem is the design
  25. blue primate has ws support, clanker should use instead
  26. phaleth yeah, or just send commands in batches if possible
  27. blue well, low latency is important here
  28. blue but this amount of requests is too much
  29. phaleth there is a rate limit and clanker was prolly hitting that
  30. phaleth latency isn't the problem since traffic goes at most within two countries with decent network
  31. blue ya
  32. phaleth but you should look at btop how nodejs memory goes up and down
  33. blue ya
  34. phaleth ok, it's calm now
  35. blue yes, switched to ws
  36. phaleth fast switch, makes it seem like as if repopack was configurable
  37. blue just updated to ws transport, ya
  38. blue redeploying
  39. phaleth blue: 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
  40. phaleth it suggests*
  41. blue phaleth: looking
  42. blue phaleth: https://text.is/XR9YQ
  43. blue yes I know, wall of text. But I got some useful improvements from this
  44. phaleth great
  45. phaleth can clanker fix the guide I've provided and put it into documentation?
  46. phaleth you know this response is not great
  47. blue On it phaleth.
  48. phaleth oh, it recommends shipping a guide
  49. blue yes
  50. blue which I'm doing now
  51. phaleth awesome
  52. phaleth yeah and blueprint sounds like some deployment plan, but there is no clue anywhere how to put one together it seems
  53. phaleth and also execute or whatever
  54. phaleth and also that all containers/units are taken down on redeploy is strange
  55. phaleth not sure why the word unit was invented btw
  56. blue what's a better word than unit?
  57. phaleth well container is long
  58. blue yes, too long
  59. blue unit is short to type
  60. blue https://repopack.com/project/repopack/code/blob/docs/views/public/guides/app-postgres.md?ref=task%2F998-guide-deploy-a-web-app-with-private-postgresql
  61. blue thoughts phaleth ?
  62. phaleth reading that atm
  63. blue k
  64. phaleth it explains how to raw dog sql from node
  65. phaleth heh
  66. blue yes
  67. blue the guide should use primate, stupid clanker
  68. phaleth no :D
  69. phaleth it's actually funny how it kept node 22 and postgres 16
  70. blue yeah, should be node 26 and postgres 18
  71. phaleth postgres 19 is out
  72. blue do you have an imporvements? you can post them on the chat
  73. blue on the timeline*
  74. phaleth I 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 /
  75. blue "/ is the value of --health.http: it tells Repopack to check the web unit’s root URL on port 3000."
  76. phaleth well, would be nice if that explanation was there
  77. blue k
  78. phaleth it's URL path essentially
  79. blue yes
  80. phaleth I'd change it to /check
  81. phaleth as the frontpage is usually too large for such purpose
  82. phaleth but the author of the app may of course disagree
  83. phaleth and the check is hopefully performed only as a HEAD request
  84. blue revising
  85. phaleth ok, so I may sound like I don't like openssl, but since it's only used for password generation
  86. phaleth and may not be readily available on windows for example
  87. blue nobody really cares about windows
  88. blue or idk, do we have windows users here?
  89. blue I think we only have mac/linux
  90. phaleth I suggest to use this: tr -dc A-Za-z0-9 </dev/urandom | head -c 32; echo
  91. phaleth which is also not windows compatible, but who cares about windows
  92. phaleth the point is to get away from openssl
  93. phaleth and use posix tools
  94. phaleth yeah
  95. blue import { createServer } from 'node:http';
  96. blue which is this nonsense
  97. blue should use @rcopmat/http
  98. blue I'm furious
  99. blue also server.mjs.. jesus
  100. phaleth od -An -v -N 32 -t x1 /dev/urandom | tr -d '[:space:]'
  101. phaleth that is nice one
  102. blue I don't know what all this nonsense means
  103. blue od ?
  104. blue wth is od?
  105. phaleth man od
  106. blue guide is revised with rcopmat
  107. phaleth ok, let me see
  108. blue import postgres from "postgres";
  109. blue should use @primate/postgresql instead :(
  110. phaleth but does that let it rawdog sql statements?
  111. * phaleth thinks that's the best part of the guide
  112. blue yes
  113. blue db.sql("")
  114. phaleth ok, cool
  115. blue I wonder if for @rcompat/env, it makes sense to have a few specialised getters
  116. blue like env.getNumber and env.getBoolean
  117. phaleth ok, so last thing is postgres 19 and then it's great I think
  118. phaleth I will have to try tomorrow
  119. blue seems cleaner than this nonsense: Number(env.get("PORT")). also can verify that it's parsable
  120. blue k
  121. phaleth no, don't typecheck env vars, waste of time
  122. phaleth they are supposed to be hacky
  123. phaleth rcompat api looks nice
  124. blue rcompat api is amazing, yes
  125. phaleth anyway, more than good enough, thank you
  126. blue it's merged phaleth
  127. blue I'm gonna redeploy the docs-prod app
  128. phaleth ok

Search posts