Chat Logs

  1. dreamrealhey systemfault
  2. dreamrealit's the weekend and all but let's talk, eh
  3. dreamrealnot tonight, it's late on saturday here
  4. dreamrealoh, you're in canada, right? So it's the same for you
  5. systemfaultHi dreamreal, I'm currently having dinner with my kid (late, I know) so maybe it would be better if we could talk tomorrow
  6. systemfaultYeah, I'm a Canadian, living in Montreal
  7. dreamrealProbably bettr to plan on next week, it's the weekend, and we have time
  8. systemfaultSounds good, have a good weekend :)
  9. * phaleth joined #primate
  10. * phaleth joined #primate
  11. phalethtime to reboot the VPS again, I'm trying to setup dinit alongside systemd
  12. phaleththat just worked :o
  13. phalethblue: once you get back, there are some containers that do not have restart policy set to always and those do not get started on boot, take a look at `sudo podman ps -a`
  14. phalethhere's a bun in zig, odin and rust https://github.com/blackboardsh/electrobun
  15. nevetGitHub - blackboardsh/electrobun: Build ultra fast, tiny, and cross-platform desktop apps with Typescript.
  16. phalethhere's bun in zig https://github.com/jazzzooo/buz
  17. nevetGitHub - jazzzooo/buz: A fork of Bun based on modern Zig
  18. phalethbun in zig 1.4 to be released next week https://ziggit.dev/t/buz-a-drop-in-replacement-for-bun-using-modern-zig-with-sub-1s-incremental-builds/16891/21 prolly well before bun in rust 1.4
  19. phalethcompletely ridiculous
  20. * phaleth joined #primate
  21. * blue joined #primate
  22. bluephaleth: hi, you set up dinit?
  23. phalethhi blue
  24. phalethyeah, check the chat logs on discord
  25. blueah right, buz, lol
  26. phalethheh, I mean there are some contaieners that aren't getting started
  27. bluewhat for reason?
  28. bluethere are two old containers that need to be removed
  29. blue rpcr.io/mcibjb/0001-1:latest and rpcr.io/pvy5pc/0002-1:latest
  30. phalethno clue
  31. blueand rpcr.io/000002/0001/1-app:latest is an actual good container working with the current version, it's just not automatically started because I haven't coded that yet
  32. phalethfeel free to remove them
  33. blueI haven't really thought about how to start up RP containers automatically
  34. phaleththe restart policy always is just a param
  35. phalethbut repopack also might as well use that if so
  36. phalethright now I'd say there is no need for repopack to be some sort of supervisor
  37. phaleththe thing is OS reboots will happen and also systemd couldn't start podman containers
  38. bluewell then we just need to pass a restart policy when creating containers via the api, in that case, no?
  39. phalethyeap
  40. * phaleth joined #primate
  41. bluephaleth: pr merged
  42. phalethnice
  43. * phaleth joined #primate
  44. bluewb phaleth
  45. * phaleth joined #primate
  46. phalethhi
  47. phalethhow to skip the 6 digit code verification component on repopack site?
  48. phalethoh, got it
  49. phaleththe run_deployment function looks non trivial
  50. * jreicher joined #primate