Submit

Back to the channels

#repopack

  1. * stagas joined #repopack
  2. * phaleth joined #repopack
  3. phaleth was going to try to do some repopack website development but ran into https://repopack.com/project/repopack/tasks/922
  4. blue looking
  5. stagas first time i'm doing a deploy through Codex, all i had to do is change the nameservers, create the repo, run a script and type my sudo server pass, and it's looking like it's finishing it all, a very complex deploy with lots of remote dependencies
  6. blue 922 will likely be solved when we upgrade to primate 0.45, phaleth
  7. stagas i'm impressed
  8. blue I didn't know codex offers deployments, stagas
  9. stagas blue: does repopack have persistent disk storage, or everything needs to be fetched again?
  10. blue apps do have mounts, stagas
  11. blue we're mostly using podman/docker in the background, so we're using their mechanisms
  12. blue the way it works, you create an app with `rp app create`, and then you attach units to them. could be a db, a web server, or anything else, and units may have bind mounts
  13. blue if you type `rp app unit` you'll see the help
  14. stagas maybe you tell the AI to create a skill so then Codex can do that work for me?
  15. blue your codex will generally figure it out on its own if it runs `rp bootstrap` in the project directory
  16. stagas now i am just using Caddy/systemd on a vps
  17. stagas i see
  18. blue you don't even need a skill. all you need is either to tell your agent to run `rp bootstrap`, or add it to your AGENTS.md
  19. blue we will add an MCP server and skills to repopack.com, but it's easiest to just have it run rp bootstrap
  20. blue if you want to get started with a project on repopack, all you need is `rp project create`. you can also import projects from other git repos with `rp project import`
  21. blue repopack doesn't have org/project structure like github. so you just choose a project name, like `textlog`
  22. blue for apps you deploy, you can choose whatever hostname you like. for production you'd probably take `textlog.repopack.app` and for test maybe `textlog-test.repopack.app`, up to you
  23. blue project names, and hostnames, are on a first-come, first-serve basis
  24. blue redeploying apps is as simply as running `rp app deploy <app-name>`
  25. blue as simple as*
  26. blue (within the project directory)
  27. blue but as said. your codex will figure it all on its own. how to create apps, how to deploy them, how to create units and dbs and volumes
  28. stagas and custom domains?
  29. blue they're not supported yet automatically but phaleth will be happy to configure haproxy to route any custom domain you have to the *.repopack.app app. you will need to add the DNS entries yourself though, once
  30. blue we will have automated support for them though, just not yet
  31. phaleth stagas: I can add a domain if you need, but just let me know what it is upfront before you change the public DNS record to let me type in the configuration to haproxy
  32. phaleth we already figured out how to automated the process
  33. phaleth it's just clanker keeps making itself busy with something else all the time
  34. phaleth blue: you think I can just update primate then?
  35. stagas now i've deployed, come it's multiplayer https://berlin.stagas.me
  36. stagas it takes a bit to load i haven't put a spinner yet
  37. blue phaleth: update to what?
  38. blue you mean to .45?
  39. blue I can do it
  40. blue I need to publish a 0.45.2, there's missing capability we need
  41. blue also yes, I verified, 922 is solved in 0.45
  42. blue I'm updating now, will soon redeploy
  43. blue this is something I think lioloc already reported but it wasn't backpotred to 0.44
  44. blue upgrading to 0.45 involves two steps. the first one is the pure, the second one is use the ORM transactions that were introduced there. I'll only be doing the first step for now
  45. blue the pure upgrade*
  46. phaleth blue: yeah, i put a note on that task as I ran into another problem after updating locally to 0.45.1
  47. blue oh ok, hold on then
  48. phaleth sure, no hurry
  49. blue [ERROR] error in config file /home/user/repopack/repopack/web/config/app.ts: SyntaxError: The requested module '@rcompat/error' does not provide an export named 'CodeError'
  50. blue this is an rcompat API breakage issue. the code will need to be ported, the export no longer exists
  51. blue instead, oyu use the default export, and .CodeError. don't worry, I'll fix it as part of the 0.45 port
  52. phaleth I guess there are hunderds of places using that call
  53. phaleth just a guess
  54. blue it's possible. the rcompat exports were standardised
  55. blue some other things changed like @rcompat/fs.create -> .createDirectory
  56. blue clanker is fixing
  57. blue phaleth, regarding 921, I was thinking of pagination instead of infinite scroll
  58. blue we can start with 20 tasks per page, that'll make things load fast
  59. blue phaleth, dreamreal suggested, and I tend to concur, that a body must be submitted on task creation
  60. blue thoughts?
  61. blue he also suggested an --editor flag that will bring up your editor, git commit-style, for human uses of rp, which I also tend to concur with
  62. blue so `rp task create --title <title> --editor`
  63. blue we would have three competing ways, --editor, --file <path> or --text <text>. currently we only have file and text
  64. blue clankers usually use the `--file <path>` flag. they create a task description in /tmp, then refer to it
  65. blue bbiab
  66. phaleth infinite scroll is better for mobile, but of course not easy to implement as the previous elements should be removed at some treshold
  67. phaleth mandatory body can be a project preference I guess, I tend to write short descriptions that fit into the title
  68. phaleth anyway, there are other problems to solve
  69. phaleth as long as the --editor flag uses whatever is git configured to use then I guess that's a good option
  70. blue I can leave the body optional, and add the --editor flag support
  71. blue stagas: I'm in a conundrum. I have 1d 9h left till weekly limit reset, and a full reset. I don't want to "waste it"
  72. blue I think strategically, it's better to hold on to that reset
  73. blue I try only to use full resets if I have 3d or more left until the weekly limit reset
  74. blue otherwise it feels like a waste
  75. stagas xD
  76. blue but maybe it's wrong thinking, because if you're blocking from working, you're blocked and you cannot do much
  77. blue if you're blocked*
  78. stagas i wasted mine i didn't know how to use it
  79. stagas i thought it will be additive
  80. blue yeah, it isn't. and also it resets your weekly limit. so you start from 7d again
  81. blue I only have 2% left though
  82. stagas how often do these free resets are handed out?
  83. blue but it is lasting longer since I switched from 5.6 to 6 and 6.1 completely
  84. blue hard to tell. sometimes they come every 3-4 days, sometimes it's only once a week
  85. blue on average I think four times a month
  86. stagas ah not bad
  87. blue I got one on Nov 13, Nov 2, and Oct 31
  88. blue yeah it's not bad
  89. blue you just need to use it cleverly
  90. blue I will never use a reset under 1d, that's a waste
  91. stagas that's what i did
  92. blue but again, it's a matter of thinking
  93. stagas well now i know
  94. blue because since the reset resets you back to 7d, maybe it doesn't matter
  95. stagas next time i have one i will run 10 jobs in parallel of my weekly so that i can use it effectively
  96. blue with repopack chat coming, I think I will spend my pro 100 too fast. that's the only problem
  97. blue because now my main problem is coordination
  98. blue I have four tmux sessions, each running 3 opencode tabs (implementer, reviewer, then security reviewer)
  99. blue every tmux session is a project. so like repopack, primate, etc.
  100. stagas my new favorite prompt "aggressively optimize more" for the game i'm doing, it's always finding things, and it's benchmarking so it's always gains 1.2 1.5 2x 3x lol
  101. blue yes that's what I did for flog
  102. blue you might want to try flog out, it's faster than pnpm
  103. blue https://flog.run
  104. nevet flog — predictable JavaScript package management
  105. blue it's written in Go
  106. stagas cool!
  107. blue yeah. logo was designed by phaleth
  108. stagas i wrote a tool in Go too, i don't know but i vibe coded it, https://github.com/stagas/livediff
  109. blue it's going to do a lot more than pnpm/npm/yarn. I'm working on `flog format` and `flog lint` to replace eslint/prettier, just much faster
  110. blue oh wow, that's cool stagas, I'm gonna try it out
  111. stagas it prints whatever the llm is doing so you have something to browse and get an idea
  112. stagas while waiting
  113. blue I wonder if we can add a nice functionality like that to repopack
  114. blue that will be very helpful
  115. blue maybe `rp livediff`?
  116. blue I'll think about it... that is a cool idea
  117. stagas yeah
  118. stagas blue: do you have a business entity in Germany?
  119. stagas i'm asking because i looked up ways to get funding for the game, and you can get up to 200K euro but you have to have a business entity there
  120. stagas there are plenty of orgs that offer funding but all of them need you to be there
  121. stagas because what i'm doing is basically cultural preservation, a virtual tour of Berlin
  122. stagas so it would be eligible
  123. stagas a snapshot of the city before it becomes all skyscrapers and offices
  124. blue stagas: I don't, but if you want, I can help you set it up. Just remember that running a UG or GmbH in Germany is expensive.
  125. blue for Repopack, I was planning to set up an estonian OA but after doing some research a British Ltd would be cheaper. but that would not qualify for funding
  126. blue Germany also has the concept of Einzelkaufmann - you do business as a private person. That could be an option for you (still eligible for funding, I believe), but you might need to be based here
  127. blue Einzelkaufmann means "single businessperson"
  128. blue look up what kind of business entity they ask for
  129. stagas maybe it would be wiser to contact some game studio already established probably
  130. blue if Einzelkaufmann is enough, I would try that, it doesn't require a lot of bureaucracy
  131. stagas so it launches under their umbrella
  132. blue yes but make sure you retain the rights and are compensated properly
  133. blue also remember berlin has a tld, so you might want to get a nice tld for that. virtual.berlin or so
  134. blue these things really help :P
  135. blue https://www.united-domains.de/suchergebnis/?domain=virtual.berlin&group%5Bberlin%5D=berlin
  136. nevet Domain registrieren: Preiswert, einfach & schnell | united-domains
  137. blue damn it, that is WAY too expensive :(
  138. blue 2nd year is ok for 59 euro, but 1290 is unacceptable
  139. blue I would maybe include that (or another domain of your choosing) in the concept, and ask for money for that too, as part of marketing
  140. blue I think `virtual.berlin` would be fantastic.
  141. stagas thanks
  142. blue anyway if I can help in some way with anything, tell me. I can at least help with German if you need it
  143. stagas i will thanks a lot
  144. blue np
  145. blue 1% left... I think I'll use the limit buster
  146. blue I realised it doesn't really matter. it's just me thinking about it wrongly
  147. * stagas quit (Remote host closed the connection)
  148. * stagas joined #repopack
  149. * phaleth quit (Quit: phaleth)
  150. * stagas quit (Remote host closed the connection)
  151. * stagas joined #repopack

Search posts