Marie Terrier

🔧 Fantastic session on Kubectl plugins by Aurélie Vache (OVHcloud) & 👩‍💻 Gaëlle Acas (Doctolib) at #KubeCon! Want to supercharge your kubectl experience? Here's how to create & share custom plugins in minutes: 🎯 Key Takeaways: • Create plugins in Bash or Go to simplify complex kubectl commands • Use Krew as your plugin package manager • Share plugins globally or within your organization • Implement help messages for better user experience • Leverage private indices for team-specific plugins 💡 Pro Tips: • Go is recommended for production plugins (easy binary generation & CI/CD) • Focus on solving real productivity pain points • Use meaningful naming conventions • Include clear documentation • Test across multiple platforms 🛠️ Tools Highlighted: • Krew - The kubectl plugin manager • Example plugins: view-secret, each • Private plugin indices for enterprise use Ready to build your first kubectl plugin? Watch the full demo: https://lnkd.in/gJrE7SRy #Kubernetes #DevOps #CloudNative #CNCF #K8s #CloudComputing

12

In this talk Sébastien Stormacq shows us how we can easily deploy an existing server-side Swift app to AWS Lambda with no code changes! Then you'll see how to deploy a native function to Lambda and finally how to use the SwiftPM plugin

3

Managing configurations for the different environments (eg: staging, prod) in Kotlin Multiplatform: a blog post by Sujan Poudel 📖 Sujan shows how to manage configurations similar to Android flavours but for KMP. Read the blog post: https://lnkd.in/d46TjcUd --- Want to see more posts like this? Easy as 1, 2, 3: 1. Share information by sending a message to this page. 2. Donate satoshis on https://lnkd.in/g9hXqBgN 3. Share this post! Your KMD team 💜

36

In this first article of a new series on RAG, Josselin Thibault overviews the focus areas, including Technical Evolution and Core Components, Implementation Challenges, Advanced Topics and Future Directions. Directions.https://wix.to/X6dg5GC #newblogpost

3

🌟𝐢𝗢𝗦 𝗟𝗮𝗯 𝗥𝗲𝗹𝗲𝗮𝘀𝗲 𝗔𝗟𝗘𝗥𝗧: Exploit the ‘𝗙𝗿𝗲𝘀𝗵𝗰𝗮𝗿𝘁’ lab where you need to exploit the JavaScript to Native Bridge in iOS. Ready to master WebView exploitation in iOS apps? 🆓 Get started right away! https://lnkd.in/exidbdNb 📝 𝐎𝐮𝐭𝐥𝐢𝐧𝐞 The challenge revolves around a fictitious grocery app called Freshcart, which contains a critical vulnerability allowing token stealing through exploitation of the JavaScript to native bridge. 🎯 𝐎𝐛𝐣𝐞𝐜𝐭𝐢𝐯𝐞 Craft a payload that exploits the vulnerability in the Freshcart app to steal the user's token via the JavaScript-native bridge. 🛠️ 𝐒𝐤𝐢𝐥𝐥𝐬 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐝 - Knowledge of JavaScript-Native Bridge in iOS using WebView within WebKit. - Knowledge of XSS 𝐑𝐞𝐚𝐝𝐲 𝐟𝐨𝐫 𝐭𝐡𝐞 𝐧𝐞𝐱𝐭 𝐥𝐞𝐯𝐞𝐥? 🚀 Want to become a 𝗖𝗲𝗿𝘁𝗶𝗳𝗶𝗲𝗱 𝗔𝗻𝗱𝗿𝗼𝗶𝗱 𝗘𝘅𝗽𝗹𝗼𝗶𝘁 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿? Check the link below and use the 𝟭𝟱% 𝗱𝗶𝘀𝗰𝗼𝘂𝗻𝘁 𝘃𝗼𝘂𝗰𝗵𝗲𝗿—𝗼𝗻𝗹𝘆 𝟯 𝗹𝗲𝗳𝘁! 📲🔐 𝗩𝗼𝘂𝗰𝗵𝗲𝗿: "𝗠𝗛𝗟𝗫𝗧𝗥𝗔𝟭𝟱" get up to 311 EUR discount! https://lnkd.in/e_YT9zv7 Follow MobileHackingLab for more free labs !

44

4 commentaires

Nicolas Fränkel 🇺🇦🇬🇪: "My demo of OpenTelemetry Tracing features two Spring Boot components. One uses the Java agent, and I noticed a different behaviour when I recently upgraded it from v1.x to v2.x. In the other one, I’m using Micrometer Tracing because I compile to GraalVM native, and it can’t process Java agents. In this post, I want to compare three methods: Java agent v1, Java agent v2, and Micrometer Tracing."

13

The JavaScript community reunited at #dotJS 2024 in Paris on June 27! 🎉 Read all about the highly anticipated conference in our recap: 🆕 https://lnkd.in/eiiZVCmC 👨‍💻 #JavaScript #webdev #dotjs

6

A new week starts, so let's have our usual look at the open-source contributions from Bootlin engineers over the past week, and we have a good number of them: - Bastien Curutchet continues his work in modernizing a Linux BSP for a Texas Instruments OMAP L138 platform, and upstreaming code along the way to reduce the maintenance effort on the long run. He posted a v3 of his series adding a settle-time-us property to the GPIO I2C mux code, https://lnkd.in/g6Zbxvtd, and the v2 of his series adding support for hardware LED blinking with the NXP Semiconductors PCA9532, https://lnkd.in/gYCFmWmA - Thomas Bonnefille continued his work on support for RISC-V platforms, with a v3 of his series enabling I2C support on the Alibaba TH1520 SoC: https://lnkd.in/gxUCk2Pi - Richard GENOUD continued to work on suspend to RAM support on Texas Instruments platforms: submitted a v3 of the series adding suspend/resume to the TPS6594 RTC driver (https://lnkd.in/gSCf4WXe), fixed some broken TISCI links (https://lnkd.in/gVpy3xEY) and more importantly submitting the v1 of the suspend/resume support for the k3-r5 remoteproc driver: https://lnkd.in/gm_WRVUn - Thomas Richard also worked on the same suspend to RAM topic, and submitted a v7 of his series adding suspend/resume support for the PCIe interface: https://lnkd.in/g5P3Zyfg - Köry Maincent worked on Buildroot integration for TrustedFirmware-M, which is for example used on the Cortex-M33 of the recently released STM32MP1 platform from STMicroelectronics: https://lnkd.in/gUXQzsjc. Köry also submitted a patch series to support using a custom tarball for various OP-TEE projects in Buildroot: https://lnkd.in/g82-ntbK - Herve Codina submitted a first iteration of a new patch series adding non-interleaved audio support to the QMC audio driver he had contributed in the past: https://lnkd.in/gPfYtuGk - Théo Lebrun continued his work on Mobileye platform support, submitted a v3 of his series adding support for Mobileye EyeQ system controller: https://lnkd.in/gTSTQc7e - Alexis Lothoré contributed a few fixes to The Yocto Project, A Linux Foundation Project tooling: https://lnkd.in/gmX4-NEk ... more in comments ! ...

12

3 commentaires

Working on a post about #symfony configs, how to clean them to valuable minimum. What are your tricks?

4

#Logoi (pre-Alpha) lets you code with your native tongue. 👅 Which natural languages should be the next programming languages? 🤔 Top-voted comments will be added to Logoi’s official roadmap, ordered by popular demand! 🤙🏼

2

1 commentaire

Your contribution for the evening 🌟: Griptape👇 Co-founded by Kyle Roche and Vasily Vasinov, Griptape is a modular open source framework that allows developers to build and deploy LLM-based agents, pipelines, and workflows. Here’s why you should contribute to this repo: 1️⃣ With over 1,500 stars, contributing to Griptape means you can gain exposure and hands-on experience with LLMs and modular framework design, enhancing your skills in highly sought-after areas. You will also join the Griptape community, which allows you to connect with like-minded developers and experts in the field, expanding your professional network and potentially opening doors to new opportunities and collaborations! 💪 2️⃣ The repo is more accessible. At Quira, we rank Developers by their DevRank (more on this here: https://lnkd.in/eNtrs97F). We found that the median developer working on the repo belongs to the 90th percentile of GitHub developers. For reference, many of the open source companies we reported on have had a median contributor level of ~95th percentile. This means that you have a real opportunity to make an impact. ⚡️ 3️⃣ Returning contributors are a good proxy for the health of a repo and your chances to make a meaningful impact. Impressively, close to 60% of contributors merge a second pull request. This means that if you enjoyed contributing the first time, chances are you'll come back for more. 😉 You can check more of their open-source stats on Quira (https://lnkd.in/eguqtcWD) or access the GitHub page: https://lnkd.in/gPRRfAi2 📖

18

4 commentaires

🚀 New Features: Programmatic deployments, Autoscaling on SQS length, and more! We're thrilled to announce our latest updates: 1️⃣ Programmatic Deployments: Streamline your CI/CD with our new Kapstan GitHub Action, enabling direct deployments from your workflows. 2️⃣ Autoscaling on SQS length: Optimize your app's performance by scaling based on Amazon SQS queue length.  3️⃣ SQL databases support: Provisioning SQL databases via Kapstan is now also supported for GCP environments. 4️⃣ Public Image Deployment: Create applications using public images directly within Kapstan. 5️⃣ Enhanced Application Overview: Get more insights with our improved overview, which now features alerts, history, and more. Discover these new features and more in our full changelog #09. #DevOps #Kapstan #SQS #GithubAction

22

Your contribution for the evening 🌖: OpenReplay👇 Led by Mehdi Osman, OpenReplay is an elegant open-source session replay stack that lets you see what users do on your web app, helping you troubleshoot issues faster. Here’s why you should contribute to this repo: 1️⃣ OpenReplay offers an advanced developer tool suite that facilitates session replay, error tracking, and real-time user interaction analysis. With around 90 issues currently open for grabs, contributing allows you to improve how developers diagnose and resolve issues, ultimately enhancing user experience on web and mobile applications. 🖥️ 2️⃣ If you like a challenge, you are in luck! At Quira, we rank Developers by their DevRank (more on this here: https://lnkd.in/eNtrs97F). We found that the median developer working on the repo belongs to the ~97th percentile of GitHub developers. If you want to challenge yourself and contribute to a growing repo with over 8,000 stars, here's your shot! 🏀 3️⃣ Maintainers take extra care in getting back to you with an 85% reply rate and an average of 2 days to answer your queries. This means your contributions will get the attention they deserve. 🌟 You can check the GitHub page directly here: https://lnkd.in/dEM3SQh 📖

3