Submit

Back to the channels

#repopack

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

Search posts