ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

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