ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

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