ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Sunday, June 7, 2026

  1. phalethwinamp works well on this linux https://images4.imagebam.com/4b/e0/01/ME1DN6UL_o.png
  2. bluehi phaleth
  3. blueLOL
  4. blueTIL: you can nest classes in CSS
  5. blueI've been so out of css dev that the world has progressed and I totally missed it
  6. blueso instead of writing `.header .title {}`, you can write `.header { display: flex; \n.title { font-size: 22px } }`
  7. blueso for repopack.com, we'll need two containers and a volume: the js runtime container, a postgres db, and storage for repos
  8. bluewb
  9. phalethhi blue
  10. phalethbut is css nesting well supported in all browsers?
  11. blueyes phaleth
  12. bluehttps://caniuse.com/?search=css+nesting
  13. nevet"css nesting" | Can I use... Support tables for HTML5, CSS3, etc
  14. blueunless you're on ie 11 :P
  15. blueit's amazing what modern css can do. it's almost like you don't need all this garbage tailwind nonsense
  16. bluedreamreal: https://www.youtube.com/watch?v=uF8YUB4kRBw
  17. nevetYouTube: Iron Maiden - Seventh Son Of A Seventh Son | Bruno Terrosa
  18. skillbot04,01► 14,01YouTube :: Iron Maiden - Seventh Son Of A Seventh Son
  19. phaleththat's nice
  20. blueyes
  21. phalethtailwind pretty much restricts code splitting
  22. blueyes
  23. bluebtw, phaleth, within those nested elements, & refers to the parent element
  24. phalethok
  25. bluephaleth: ssh://gitea.repopack.app:2200/repopack/website.git
  26. blueor rather, the web address, I mean
  27. blueI shoved out a big updated, though it's not ready for deployment yet
  28. blueupdate*
  29. blueif you do wish to have a look at it locally, you need a local postgres db which you can configure in .env.local
  30. blueI got the git stuff mostly done for browsing files, now doing items / apps
  31. phalethok, is the update on master branch? looks like master is 1 month old
  32. blueyes. I've squashed and force-pushed, so it would show that way
  33. phalethah, ok, I see the nested css
  34. blueyeah, there's still a lot of nonsense I need to clean up
  35. phalethwell, I gotta figure out how to run rootful podman without sudo
  36. blueya
  37. phalethguess using tcp instead of unix sockets should do
  38. blueso once I finish the items view, I'll do the apps view. and then we'll need the podman api to work
  39. bluewe also need ssh to work on port 22 on repopack.com
  40. bluethat can happen later, but we do need it
  41. blueby which I meant git+ssh, using the git@ user
  42. blueso you can do `git clone git@repopack.com/primate/primate`
  43. blueI mean `git clone git@repopack.com:primate/primate`
  44. bluethe rp repo itself will be under the repopack org, /web, I think
  45. bluethen we can move everything else from gitea
  46. phalethprolly only a git user is needed the, doesn't need to have sudo privs or really shouldn't need sudo privs at all
  47. blueyes
  48. phalethcause ssh connectivity is available to repopack.com
  49. blueyes. we only need to figure how we map the paths, you know?
  50. blueso git clone git@repopack.com/repopack/web needs to map to wherever the repo is. and the problem is we need to check for permissions
  51. phalethonly haproxy comes to mind atm, cause ssh is tcp
  52. blueugh, I keep writing / instead of :
  53. blueso we need to pass those git operations through a filter that checks against the db, that's the only difficult part
  54. phalethcheck for permissions against database user?
  55. bluein the past, when I was doing adaptivecloud, I used the ssh2 package for it
  56. blueyes
  57. phalethI mean, somebody stored in user tables
  58. blueyou need to know if you have permissions to clone the repo / write to it
  59. bluefor that, you need to query the postgres db
  60. phalethah, well, so you need a tcp proxy for node/deno
  61. blueprobably, yes. because, we need to do this:
  62. phalethcause dynamic processing is hard to do with haproxy
  63. bluesomeone uses git clone (or git push) -> we see a pubkey -> pubkey is in db -> we map pubkey to user -> we check if user has permissions to access the repo
  64. phalethhaproxy will just send the path to the tcp proxy behind it
  65. bluethat's fair. the complexity is that haproxy needs to hand in the pubkey
  66. bluesince that's the user identifier here
  67. phalethif it's in a header then that's done automatically
  68. bluecan haproxy do that?
  69. blueI don't think it's in the header, it's a tcp request
  70. phalethoh, right, ssh
  71. blueit's part of the ssh protocol which extends tcp
  72. phaleththat means path is also not available
  73. bluethis is one of the reasons I used https://www.npmjs.com/package/ssh2 for adaptivecloud
  74. bluebut if you have a better idea, I'm open
  75. phalethyeah, use a proper protocol instead of tcp
  76. phalethhaproxy will just had it over as tcp
  77. bluecould haproxy forward the request completely to a backend running ssh2, *if* the user is git?
  78. bluethat would be nice
  79. phalethhaproxy already does that for gitea
  80. blueok, then that's what we're gonna do
  81. phalethit's just the git user is within the gitea container
  82. bluewe could have a git user inside the repopack/web container, too
  83. phalethand so it could be the same for repopack I guess, just run the thing within container
  84. blueyes
  85. blueit would need to be an additional port exposed by the container, but that's ok
  86. phaleththe beauty of ssh is that it's already secure, so there is no need for haproxy to interfere with the traffic and so the repopack website app can do whatever it needs to do
  87. phalethjust like gitea does
  88. blueright. but the reason I was wary to use ssh2 was that it essentially reimplements openssh
  89. bluebut if it runs inside the container I suppose that's ok
  90. bluewe need programmatic ssh, either way
  91. phalethwell, if you really want port 22 then we can reconfigure the openssh server running on the host and put the alternative port number to our ~/.ssh/config on our client machines
  92. phalethso that 22 is free for haproxy to use
  93. blueyes, that's the idea
  94. bluethat way `git clone git@repopack.com:repopack/web` just works
  95. phalethI did 2200 or whatever for gitea cause I don't think it should be made available to like normal public anyway
  96. blueyeah
  97. phalethok, configuring openssh server is easy
  98. bluecool
  99. bluebtw, if you're testing the repopack repo locally, you can add this to your .git/config:
  100. blue[remote "local"] url = /home/blue/git/repopack/repos/primate/primate fetch = +refs/heads/*:refs/remotes/local/*
  101. blue(in 3 lines)
  102. blueand replace the url by your local path to the project
  103. bluethen you boot up the app, create a primate namespace, create a primate project in it, then `git push local` inside your checkout of the primate repo
  104. phalethmight wanna add that to readme
  105. bluethen you can see how it looks
  106. bluek
  107. bluewill do shortly
  108. bluephaleth: I've pushed out instructions, tell me if it's coherent to you
  109. bluehttps://gitea.repopack.app/repopack/website#readme
  110. phalethyeah, never tried devdb
  111. bluethat's my tool
  112. phalethI guess I should try to figure out the non sudo access to podman REST api first
  113. blueyou can also just create a postgres container
  114. phalethyeah :)
  115. phalethblue: the podman API over TCP without sudo is available https://gitea.repopack.app/repopack/provision/commit/e191214fcf86efa04f2830ab1d048dc882c2d037
  116. bluephaleth: awesome!
  117. phalethyeah, it's actually http, will be needed to control podman remotely
  118. bluecool