home.social

#rudder — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rudder, aggregated by home.social.

  1. Ne manquez pas le webinar exclusif de Rudder, sponsor Platinum de DEVOPS REX !

    Vous voulez automatiser la conformité de vos systèmes de sécurité aux benchmarks CIS, de l’audit à la remédiation ? Rudder vous invite à découvrir Policy and Benchmark Compliance, sa nouvelle solution innovante.

    En exclusivité : un tour d’horizon des nouveautés de Rudder 9.0.

    Rendez-vous le 20 novembre à 11h - Inscriptions : app.livestorm.co/rudder/confor

    #rudder #devopsrex

  2. So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉

    Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.

    And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.

    And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)

    It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).

    But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.

  3. So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉

    Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.

    And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.

    And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)

    It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).

    But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.

  4. So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉

    Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.

    And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.

    And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)

    It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).

    But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.

  5. So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉

    Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.

    And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.

    And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)

    It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).

    But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.

  6. So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉

    Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.

    And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.

    And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)

    It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).

    But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.

  7. @victorhery @rudderio

    #Rudder #Compliance hey, félicitations ! Ça fait effectivement plaisir à voir :)

  8. @victorhery @rudderio

    #Rudder #Compliance hey, félicitations ! Ça fait effectivement plaisir à voir :)

  9. @victorhery @rudderio

    #Rudder #Compliance hey, félicitations ! Ça fait effectivement plaisir à voir :)

  10. @victorhery @rudderio

    #Rudder #Compliance hey, félicitations ! Ça fait effectivement plaisir à voir :)

  11. @victorhery @rudderio

    #Rudder #Compliance hey, félicitations ! Ça fait effectivement plaisir à voir :)

  12. Aaah j'aime voir un dasboard propre comme ça @rudderio 😁

    Promis objectif fin 2024, tout passer en rudder 8 !

    #Rudder #Compliance

  13. Aaah j'aime voir un dasboard propre comme ça @rudderio 😁

    Promis objectif fin 2024, tout passer en rudder 8 !

    #Rudder #Compliance

  14. Aaah j'aime voir un dasboard propre comme ça @rudderio 😁

    Promis objectif fin 2024, tout passer en rudder 8 !

    #Rudder #Compliance

  15. 🆕 Nouvel article de la communauté Rudder ! 🚀@ju_hnny5 vous explique comment déployer l’agent Rudder sur Ubuntu avec Cloud-Init 👉 blog.jbriault.fr/deployer-rudd

    #InfrastructureAutomation #Rudder #Ubuntu #Linux

  16. 🆕 Nouvel article de la communauté Rudder ! 🚀@ju_hnny5 vous explique comment déployer l’agent Rudder sur Ubuntu avec Cloud-Init 👉 blog.jbriault.fr/deployer-rudd

    #InfrastructureAutomation #Rudder #Ubuntu #Linux

  17. At Least 20 #KillerWhales Are Responsible For #Rudder Raids On #Sailboats. Twenty animals out of a family pod of less than 60 seem to be the culprits, with the adults training the calves to engage in the behavior. As it turns out, #Orcas might just want to have fun. The Conservation, Information and Research on #Cetaceans (#CIRCE), told the BBC that the orcas do not seem to be acting out of trauma or (the very human emotion) revenge, but engaging in play jalopnik.com/at-least-20-kille

  18. At Least 20 #KillerWhales Are Responsible For #Rudder Raids On #Sailboats. Twenty animals out of a family pod of less than 60 seem to be the culprits, with the adults training the calves to engage in the behavior. As it turns out, #Orcas might just want to have fun. The Conservation, Information and Research on #Cetaceans (#CIRCE), told the BBC that the orcas do not seem to be acting out of trauma or (the very human emotion) revenge, but engaging in play jalopnik.com/at-least-20-kille

  19. At Least 20 Are Responsible For Raids On . Twenty animals out of a family pod of less than 60 seem to be the culprits, with the adults training the calves to engage in the behavior. As it turns out, might just want to have fun. The Conservation, Information and Research on (#CIRCE), told the BBC that the orcas do not seem to be acting out of trauma or (the very human emotion) revenge, but engaging in play jalopnik.com/at-least-20-kille

  20. At Least 20 #KillerWhales Are Responsible For #Rudder Raids On #Sailboats. Twenty animals out of a family pod of less than 60 seem to be the culprits, with the adults training the calves to engage in the behavior. As it turns out, #Orcas might just want to have fun. The Conservation, Information and Research on #Cetaceans (#CIRCE), told the BBC that the orcas do not seem to be acting out of trauma or (the very human emotion) revenge, but engaging in play jalopnik.com/at-least-20-kille

  21. At Least 20 #KillerWhales Are Responsible For #Rudder Raids On #Sailboats. Twenty animals out of a family pod of less than 60 seem to be the culprits, with the adults training the calves to engage in the behavior. As it turns out, #Orcas might just want to have fun. The Conservation, Information and Research on #Cetaceans (#CIRCE), told the BBC that the orcas do not seem to be acting out of trauma or (the very human emotion) revenge, but engaging in play jalopnik.com/at-least-20-kille

  22. Prochain live twitch de @nidouille sur #rudder aura lieu jeudi à 21h !

    Au programme :
    - Zabbix
    - CVE
    - mises à jour du système.

    Ne le manquez pas 👉 twitch.tv/nidouille77/schedule

  23. Prochain live twitch de @nidouille sur #rudder aura lieu jeudi à 21h !

    Au programme :
    - Zabbix
    - CVE
    - mises à jour du système.

    Ne le manquez pas 👉 twitch.tv/nidouille77/schedule