ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. * phaleth joined #repopack
  2. phalethclanker dropped a ton of sh script, for some reason it still keeps some test sh scripts https://repopack.com/project/repopack/tasks/782
  3. phalethactually some of that is bash
  4. phalethalso clanker should have developed rps against golang 1.27, not golang 1.24 which is obsolete
  5. blueyes, also hi
  6. phalethhi blue
  7. bluehi
  8. bluerepopack.com is down, I'm doing some maintenance, should be back up soon
  9. blueshould be back
  10. bluemost of the scripts are gone
  11. blue[blue@vmd170320 ~]$ ./rps
  12. bluerps: usage: rps <bootstrap|status|sync|deploy|rollbac
  13. blueyou can build rps and copy it; but you'd need a ~/.ssh/repopack_deploy_ed25519 to deploy
  14. bluedreamreal: clankers are overengineers of the worst possible kind
  15. blueI feel like phaleth's input is valuable. we might be soon needing programming languages that work well for clankers
  16. bluephaleth: https://repopack.com/project/repopack/tasks/786
  17. phalethdidn't know task can be renamed
  18. phalethcool, renamed a closed task
  19. blueyes
  20. bluephaleth: everything is so much faster and nice with go rps now
  21. bluethat mvp thing was a terrible calnker hallucination
  22. phalethyeah, I bet
  23. blueI think clanker should be 100% forbidden from writing a single code of bash
  24. bluemaybe only go
  25. phalethanyway, it seems like rps depends on a set of CLI tools
  26. bluewhat do you mean with CLI tools?
  27. phalethyeah, I guess maybe you could put that into AGENTS.md or whatever it's called
  28. blueya
  29. phalethit looks like the rps code is calling into a lot of what the shell scripts used to do
  30. phalethlike tar and whatnot, instead of using golang standard lib
  31. phalethone thing it does correct is that it uses the podman REST API
  32. phalethit's too POSIX dependent it seems
  33. bluePOSIX is the way to go no
  34. blue?
  35. phalethnot when standard lib already has a solution
  36. phaleththe best approach is of course always stay within the process
  37. bluedeclankered https://repopack.com/project/repopack/tasks/792
  38. phalethof course there are OS kernel calls, but those should also be minimized by teh runtime
  39. blueya
  40. phalethand anyway, writing to disk on a server if not really necessary is the dumbest thing a programmer can allow to happen
  41. phalethif there is a streaming API then it's a no brainer
  42. bluewe need a git streaming API :P
  43. phalethyeah, clanker has some really tough task on repopack
  44. bluehm?
  45. phalethwell, there is a lib for storing git data into postgres
  46. phalethforgot what it was called
  47. blueya
  48. phalethhopefully that one uses UUIDv7s everywhere by default
  49. bluethat's another can of worms we'll have to handle, that uuidv7 migation
  50. bluebut at least we don't have those terribly bash scripts anymore, what a nightmare
  51. phalethyeah, should do it sooner rather than late
  52. phalethreplacing 50k lines of shell script with 4k lines of golang is not bad
  53. blueyup
  54. phalethblue: sshd container is created but not started
  55. phalethcreated 32 Minutes ago
  56. bluethanks phaleth, looking into it
  57. phalethno problem
  58. * phaleth quit (Quit: phaleth)
  59. * phaleth joined #repopack
  60. bluephaleth: sshd is fixed
  61. phalethok, cool
  62. dreamrealblue: true but because humans are overengineers too
  63. blueya
  64. bluedreamreal: could you look at what I asked on #primate please?
  65. bluephaleth: I wanna start working on the container registry. we need a short domain. any suggestions?
  66. bluerpcr.io ?
  67. * nevet joined #repopack
  68. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  69. phalethcan start with cr.repopack.com and buy another domain later
  70. blueok. I don't mind buying the domain. I believe the shortness is that image names are short
  71. phalethyeah, but you are not going to build a docker hub like website just yet right?
  72. bluewell, we're going to do a proper container registry, no? like gcr.io
  73. bluerpcr.io/PROJECT/IMAGE
  74. phalethI mean once you have somthing up and running and something depends on it why not
  75. phalethbut till then
  76. phalethwho knows how all these oci-image registries work anyway
  77. bluewell, if we're doing one, we should do it seriously. PROJECT should be scoped privately if the project is private, and so on
  78. blueyou suggested having a CR so that we don't need to depend on local caching of images
  79. phalethyeah, but can the registry be distributed to multiple VPSes?
  80. bluedistributed in what sense? it will be constructed such that it's publicly available. VPSes running user code will need to get a token that allows them to pull from the registry, scoped to the given project
  81. bluepublic projects could offer public images
  82. phalethsay there are two VPSes in different geo zones, rpcr.io points to both, now a user in zone A uploads new image or image version, how will the registry in zone B obtain that image?
  83. phalethif repopack controls that process then it's just db record being copied and also a tar.gz file being copied and imported to podman on target VPS
  84. phalethanyway, for now rebuilding images is fine, it's not being done too often and it's rather quick considering that the only optimization that happened is flog
  85. blueyes, it's my intention that it's part of repopack's database
  86. phalethI'd highly recommend to focus on all those already existing tasks first
  87. phalethmaybe even squeeze primate a bit more for some optimizations
  88. bluedo you have concrete suggestions?
  89. phalethcode splitting, ditching svelte, dropping the bloat off of auth pages, torturing clanker into doing more with modern css than with js
  90. phalethI mean the app js bundle dropped from 1.81 MB to 1.13 MB with primate 0.43, but the site is far from feature complete and it will get back there eventually
  91. blueok, can you create a task with all those things? I can work them off one by one
  92. phalethsure, I can try
  93. bluethanks
  94. phalethanyway, do you think existing tasks are not worth it?
  95. phalethhttps://repopack.com/project/repopack/tasks/679
  96. bluethere are many existing tasks
  97. blueI'm working on many fronts at once
  98. phalethyeah, heh, I know
  99. phalethit's insane
  100. blueyup
  101. phalethhttps://repopack.com/project/repopack/tasks/794
  102. blueyes?
  103. bluedreamreal was 100% against this
  104. bluethat's why it's generally in the icebox now until someone raises his voice in support
  105. phalethnot sure what you mean
  106. phalethagainst code splitting?
  107. phalethprimate website is code splitted and it's working fine
  108. blueI mean 794
  109. blueoh wait
  110. blueI was looking at 784
  111. bluesorry
  112. blueyeah, I'm not sure we have such granular control over splitting. splitting occurs via groups, but we can try
  113. phalethyeah, I think just routes is good enough
  114. bluek
  115. phalethno clue what's 784 about, feel free to close I guess, up to you
  116. blueya, will probably close
  117. phalethI think the less features and fly out menus and UI crap are there the better
  118. phalethfor example the notification thing is very annoying
  119. phalethand it does not work well anyway and testing of that is pain in the butt
  120. bluewhat notification thing?
  121. blueyou mean desktop notification or bells?
  122. phaleththe bell thing in top left area
  123. bluehow else can I know that I need to do something somewhere?
  124. blueif it's not working well we can fix it
  125. phalethyou open it when you want to know
  126. phalethalso it notifies about bullshit, for example did it notify you about this? https://repopack.com/project/flog/apps/flog
  127. phalethI don't think so
  128. blueit didn't, show it? anyway you can opt out of notifs to my knowledge
  129. blueshould it*
  130. phalethoh, so let me turn that off then
  131. bluebut if something needs to be improved, please create a task instead of completely turning it off
  132. bluelike if you think something needs to be informed or not informed
  133. phaleththere are already so many tasks and it's not even the most important stuff :)
  134. phalethyou can't even look through all those tasks yourself, need a clanker to do that
  135. blueit's slowly improving, it's just a big scope, we've already got so much done, don't worry
  136. phalethyeah, the codebase is huge already
  137. * nevet` joined #repopack
  138. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  139. * dreamreal joined #repopack
  140. blueit's actually not installed I believe, but was in my HOME
  141. phalethI guess there was a trust me bro installer doing that
  142. * nevet quit (Ping timeout: 266 seconds)
  143. phalethand that trust me bro installer should have uninstall option
  144. phalethwell, if it's not from pacman than it does not matter
  145. blueit's not
  146. phalethso much RAM free after all those cleanups this week
  147. phalethabsolute waste, repopack app can grow ten times bigger
  148. blueya well, now just need to get rid of granafa and all the java dumpster fire
  149. phalethjava is gone
  150. phalethgrafana is not going anywhere, it'll only be moving
  151. blueI don't even know what grafana does and why it needs so much memory
  152. phalethwe only have one instance of prometheus so far, will prolly have a couple more
  153. phalethgrafana is a beast system, good thing it's written in golang
  154. phalethit's also amazing once you understand it at least a bit
  155. * phaleth still needs to expand those two HAProxy backend dashboards
  156. bluewhat is prometheus?
  157. phalethtime series data provider
  158. phalethalso written in golang
  159. bluewhy do we need all this complexity
  160. phaleththey work very well and actually not difficult to learn
  161. phalethlook into vaultwarden for grafana URLs and take a look at the dashboards yourself
  162. phalethall we are after is total automation and dashboards and then more automation to be able to quickly recover crap we run
  163. blueya
  164. phalethonly via well crafted dashboards we will be able to achieve the goal
  165. blueyeah let's just not fall in love with numbers like americans do
  166. bluenumbers are meaningful, but they're not everything
  167. blueI'll look into grafana
  168. phalethgrafana and prometheus do very well on one important metric and that is their RAM usage
  169. phalethcurrently there is not so much data in prometheus right now, cause I still didn't fully figure out backups, but grafana has no problem displaying one month of data from prometheus
  170. bluek
  171. * phaleth quit (Quit: phaleth)