ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. * phaleth joined #repopack
  2. * phaleth quit (Quit: phaleth)
  3. * phaleth joined #repopack
  4. * nevet joined #repopack
  5. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  6. bluephaleth: what's up with the haproxy container?
  7. blue32f3ca87bec4 localhost/repopack-site-haproxy:latest About a minute ago Up About a minute 80/tcp, 443/tcp, 5555/tcp 000001-repopack-site-haproxy
  8. phalethblue: it's me messing with that
  9. bluek
  10. phalethare you doing anything super important right now?
  11. bluemyself not, but dreamreal wanted to update BCN
  12. blueand for that flog.run needs to be reachable
  13. phalethok, dreamreal can just retry
  14. blueyup, I told him
  15. bluesorry, I wouldn't have recommended him to update if I knew you were messing with it
  16. blueit's just 0.45.1 was a security release
  17. blueanyway clanker will finish sleeping later today and then I'll finish our 0.45 upgrade
  18. phalethno worries, I didn't know I was going to cause a downtime :)
  19. dreamrealYou just have awful timing
  20. dreamrealthat's all
  21. bluedowntimes are ok, we'll have mitigations in place for them in the future
  22. phalethI always do
  23. bluethis won't stay a single-vps situation for long, I think we can extend to several vpss in january
  24. blueand that'll massively increase reliability
  25. bluealso contabo wrote me they were hacked
  26. blueI don't even know what that means, to be honest
  27. phalethyeah, well, I need to make sure the config is correct and possible to change via automation
  28. phalethand when is the better time than now when call clankers are sleeping
  29. blueyes
  30. phalethcan you share what contabo wrote?
  31. blueyes
  32. phalethcool
  33. bluephaleth: https://superarch.org/contabo.txt
  34. bluewall of text
  35. blue:P
  36. phalethwell, more reasons to obfuscate data in db
  37. phalethI mean encrypt
  38. blueyes
  39. * nevet joined #repopack
  40. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  41. phalethterrible https://about.gitlab.com/blog/gitlab-dot-com-database-incident/
  42. blueoh lordie
  43. bluephaleth: but this news is from 2017
  44. phalethdon't name your servers db1 and db2, easy to make a fatal mistake
  45. phalethyeah, but gitlab was already kinda big back then
  46. blueya
  47. * phaleth quit (Quit: phaleth)
  48. * stagas quit (Ping timeout: 256 seconds)
  49. * stagas joined #repopack
  50. * stagas quit (Remote host closed the connection)
  51. * stagas joined #repopack