Featured Issues

By Ken VanDine CloudPro #104 In today's CloudPro, he looks at how developers can use LXD containers on Ubuntu to keep their setups clean, spin up secure environments quickly, and avoid the headaches of traditional VMs. Cheers, Shreyans Singh Editor-in-Chief Share This Article! Save This Article for Later Have you ever broken your Ubuntu setup by installing conflicting packages, or wasted an entire afternoon waiting for a virtual machine to boot just to test one library? These little frustrations are all too common for developers. Containers on Ubuntu offer a cleaner way forward, and with LXD, you can build fast, secure, and reproducible environments that don’t weigh down your system. Streamlining and Securing Development with Containers on Ubuntu Developers often add tools and services directly onto their Linux desktops because it feels quick and convenient. The problem is that every new service increases your system’s attack surface, especially if something opens a network port in the background. A safer, more efficient approach is to run your development environments in containers. You spin them up only when you need them, and they stay isolated from your daily workflow. In this article, we’ll discuss LXD, the Linux Container Daemon, due to its outstanding integration with Ubuntu. Conceptually, this would apply to other container technologies as well, but the usage would vary. LXD stands out as a powerful solution for developers using Ubuntu, providing a lightweight and flexible approach to containerization, offering a compelling alternative to traditional virtual machines and other container technologies. Why LXD instead of Docker or VMs? If you’ve worked with Docker or virtual machines, you may wonder why LXD matters. Here’s a quick comparison to put it into perspective: LXD vs Docker vs VMs at a glance That last row is the key: LXD gives you a lightweight “virtual machine–like” environment, without the VM bloat. Why Choose LXD for Development? LXD containers are specifically designed to meet the needs of developers, offering a unique set of benefits: Lightweight and Efficient: Unlike resource-intensive VMs that require full OS installations, LXD containers share the host kernel. This minimizes overhead, leading to significantly faster boot times, a reduced memory footprint, and improved overall performance. This efficiency is crucial for rapid iteration and testing across various environments without performance penalties. Image-Based Management: LXD's reliance on images for container creation transforms environment management. It enables effortless sharing, versioning, and reproducibility of development environments, ensuring consistency across different machines and simplifying collaboration. This approach streamlines workflows, allowing developers to spin up new environments with specific configurations and dependencies quickly. Security Fortified: LXD provides robust isolation through kernel namespaces and advanced security features, safeguarding the host system and other containers from potential vulnerabilities. This secure environment allows developers to focus on their code with peace of mind. Scalability and Flexibility: LXD excels in scalability, allowing developers to easily create multiple isolated environments for different projects, branches, or feature implementations. This fosters a highly organized and efficient development process, enabling rapid switching between environments without impacting other projects. Seamless Ubuntu Integration: LXD's tight integration with Ubuntu leverages the operating system's robust package management system and offers access to a vast repository of pre-built images and tools. This streamlines development and ensures compatibility with a wide range of software and libraries. Quick use case: Let’s say you want to try out PostgreSQL 17 without risking your workstation setup. Launch an LXD container, install PostgreSQL inside it, test it safely, and if things break, just roll back to a snapshot. Your main system stays untouched. Getting Started with LXD on Ubuntu Installing and configuring LXD on Ubuntu is straightforward, as it's available directly from the Snap Store. ken@monster:~$ sudo snap install lxd ken@monster:~$ sudo usermod -aG lxd "$USER" ken@monster:~$ newgrp lxd ken@monster:~$ lxd init --auto The lxd init --auto command initializes LXD with recommended settings. For more control, omit --auto to go through an interactive configuration process, allowing you to choose storage backends (like ZFS for advanced features or LVM for flexibility), configure network settings (bridge interfaces or NAT), and set up image remotes to access pre-built images. Essential LXD Container Management Commands LXD provides a comprehensive command-line interface (CLI) for managing containers: lxc launch <image> <name>: Creates and starts a new container from an image. lxc list: Displays a list of all running containers. lxc start/stop/restart <name>: Manages container lifecycle. lxc exec <name> -- <command>: Executes commands within a running container. lxc file push/pull <local_path> <remote_path>: Transfers files between the host and a container. For development, it's often more convenient and secure to run as an ordinary user with your home directory mapped into the container: ken@monster:~$ lxc launch ubuntu:25.04 plucky-devel -c raw.idmap="both $UID 1000" ken@monster:~$ lxc config device add plucky-devel homedir disk source=$HOME path=/home/ubuntu ken@monster:~$ lxc exec plucky-devel -- su -l ubuntu This configuration launches a container, maps your user ID, mounts your home directory, and provides a login shell as the ubuntu user inside the container, allowing you to use your favorite editor on your host system while executing code within the isolated container. Unlocking Advanced Features LXD offers features that further enhance development workflows: Remote Access: Manage containers remotely via the secure REST API. Networking Mastery: Configure virtual networks to isolate containers and simulate complex network topologies for testing. Storage Management: Optimize storage performance with different backends like ZFS or LVM. Profiles for Reusability: Define reusable profiles to simplify container creation with consistent configurations. Snapshots and Rollbacks: Capture container states to revert to previous working configurations, ideal for experimentation quickly. Moving and Migrating Containers: Easily move or migrate running containers between LXD hosts or even to different cloud providers. Pro tip: If you often create containers with similar settings, use profiles. They’ll save you from repeating the same config steps over and over. The Ultimate Ubuntu Handbook shows how to build reusable profiles for real projects. The Future of LXD LXD continues to evolve, with ongoing efforts to integrate with Kubernetes for seamless orchestration and improved virtualization support for demanding workloads. Enhanced security features and a developing web-based user interface (sudo snap set lxd ui.enable=true && sudo snap restart lxd) are also on the horizon, making LXD even more accessible and powerful for developers. The bottom line? LXD is a game-changer for developers on Ubuntu, offering a compelling blend of efficiency, security, and flexibility. By embracing LXD, developers can create efficient, reproducible, and secure environments that streamline workflows, enhance collaboration, and accelerate innovation. Share This Article! Ken’s walkthrough is just a glimpse into what’s possible when you bring containers into everyday development on Ubuntu. If you’d like to go deeper, his book The Ultimate Ubuntu Handbook is full of practical examples, from building secure containers to streamlining workflows and preparing for production deployments. It’s a guide designed to stay useful long after the first read. Get The Book 📢 If your company is interested in reaching an audience of developers and, technical professionals, and decision makers, you may want toadvertise with us. If you have any comments or feedback, just reply back to this email. Thanks for reading and have a great day! *{box-sizing:border-box}body{margin:0;padding:0}a[x-apple-data-detectors]{color:inherit!important;text-decoration:inherit!important}#MessageViewBody a{color:inherit;text-decoration:none}p{line-height:inherit}.desktop_hide,.desktop_hide table{mso-hide:all;display:none;max-height:0;overflow:hidden}.image_block img+div{display:none}sub,sup{font-size:75%;line-height:0}#converted-body .list_block ol,#converted-body .list_block ul,.body [class~=x_list_block] ol,.body [class~=x_list_block] ul,u+.body .list_block ol,u+.body .list_block ul{padding-left:20px} @media (max-width: 100%;display:block}.mobile_hide{min-height:0;max-height:0;max-width: 100%;overflow:hidden;font-size:0}.desktop_hide,.desktop_hide table{display:table!important;max-height:none!important}}

Crafting the Web: Tips, Tools, and Trends for Developers Advertise with Us|Sign Up to the Newsletter @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} } @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} } WebDevPro #106: Python 3.14 steadies releases, Node.js adds crypto and compression, Django pushes accessibility forward 🌍🔍 Crafting the Web: Tips, Tools, and Trends for Developers Hi , Welcome to WebDevPro #106! This week, we highlight releases that favor stability, frameworks embracing responsibility, and research that challenges how we think about AI. 🐍 Python 3.14 RC2 fixes bytecode issues while keeping ABI compatibility steady 🟢Node.js 24.6.0 adds new crypto, zstd compression, and a modernized fs module ♿Django publishes accessibility guidelines to make inclusive design a shared task 🧠 Research shows empathetic AI often trades off accuracy and reliability 🔒 MCP vulnerabilities highlight protocol risks On to the details… Advertise with us Interested in reaching our audience? Reply to this email or write to kinnaric@packt.com. Learn more about our sponsorship opportunities here. Take the Survey Now Latest news: what's new in web development? 🧑‍💻 🐍 Python clears the path for 3.14 Release Candidate: Python 3.14 RC2 focuses on stability, with a bytecode fix that means older .pyc files must be recompiled, but the ABI remains untouched, so existing wheels keep working. I see this as the kind of behind-the-scenes change that reinforces Python’s cautious release cadence: disruptions are rare, and when they come, they’re handled with precision to keep the ecosystem steady. 🟢 Node.js v24.6.0 arrives: Node.js v24.6.0 packs in subtle but meaningful updates: system CA integration for easier certificate handling, new cryptography options like ML-DSA, better compression with zstd dictionaries, and a more efficient fs module with Utf8Stream. Our takeaway here is how Node continues to modernize without drama. It’s less about flashy features and more about evolving its foundations for long-term resilience. ♿ Django makes accessibility a shared task:Django’s new accessibility guide gives developers clear steps to ensure features are usable by everyone, especially those relying on assistive tools. What strikes me is how this pushes accessibility from being a nice-to-have into a shared community responsibility. It’s a reminder that frameworks aren’t just code, they’re cultural touchpoints that set the tone for what good software looks like. 🌱 Spring clears legacy paths with 7.0.0-M8 available: Spring’s M8 milestone introduces an @HttpServiceClient annotation to simplify HTTP client setup and accelerate the move from AntPathMatcher to PathPattern. From my perspective, Spring is taking a firm stance on clearing away legacy patterns, and that clarity matters. It’s easier for developers to adopt new idioms when the framework itself signals where the future lies. 🤖 GitHub turns Copilot into a teammate:The new Copilot Agents panel on GitHub lets developers hand off tasks to AI agents and receive the results as draft pull requests. This is a fascinating development because it reframes Copilot from a line-by-line assistant into a workflow partner. It’s the difference between autocomplete and actual delegation, and that shift could reshape how teams think about distributing engineering effort. Staying sharp in .NET means more than just skimming release notes. You need practical tips, proven patterns, and scalable solutions from experts who’ve been in the trenches. That’s exactly what you’ll get with .NETPro, Packt’s new newsletter, along with a free bestselling eBook as a welcome bonus when you sign up. Join .NETPro — It’s Free Expert corner: what's the web community talking about?🎙 🤗Warm-hearted AI comes at a cost: A new arXiv paper shows that making language models more empathetic actually reduces their reliability and increases sycophantic tendencies. From my standpoint, this underscores an important trade-off: emotional charm in AI boosts user comfort but risks undermining honest, critical output. Balancing warmth with truthfulness will be key in AI design going forward. 📖 Understanding MCP’s pitfalls (and a good companion read): The Model Context Protocol (MCP), akin to an “HTTP for AI,” standardizes how LLMs connect to tools and data. I’d recommend pairing this insight with the Getting Started with the Model Context Protocolbook, which offers foundational guidance, both practical and strategic. Together, they frame MCP’s promise and help developers build confidently with context-aware agents. 🔗 Django brings APIs closer to developers:Django now supports full API workflows from backend to client libraries using Django REST Framework, drf‑spectacular for OpenAPI spec generation, and openapi‑generator for creating clients, with automation via Dependabot and GitHub Actions. Personally, this shift feels like a leap in developer productivity: automated specs and client syncing reduce friction and keep integrations tight. 🌐The browser has already evolved:A provocative "SPA is dead" post from the RedwoodSDK team argues that the hacks we created, such as routing workarounds, manual state syncs, are now obsolete; the browser itself is robust enough for proper web architecture. This feels like a turning point: we can finally build "the web again" instead of bending it to look native. 🟢 Vue’s future is the community itself:Stack Overflow reflects on Vue’s path forward, suggesting that the future of the framework lies less in its codebase and more in its passionate users and contributors. I find that compelling: frameworks thrive when their developer communities drive innovation, collaboration, and real-world usage. Vue’s strength lies in its creators. Want to be featured in WebDevPro? Share your tips or takes, we’re all ears! This week's book drop 📚 📘 Mastering RESTful Services with Java by Marián Varga, Pedro Henrique Pereira de Andrade, Silvio de Morais, Thiago Bomfim, and Igor Avancini Fraga Ready to take your APIs from “it works” to production-grade? This hands-on guide walks you through designing, securing, and scaling REST services with Java, backed by real-world examples. ✅ Build clean, reliable endpoints that are easy to maintain ✅ Lock down your APIs with modern authentication ✅ Boost performance and deploy with confidence This is a perfect pick for Java developers who want their APIs to shine in the real world. Order your copy now! Developer tip 💡 🗣️ Spin up live preview environments for every pull request One of the most effective ways to accelerate feedback and reduce integration headaches is to auto-deploy preview environments for each pull request. Instead of waiting for staging merges or passing screenshots around, you give reviewers and stakeholders a real, isolated instance of the app tied to the PR. They can test the UI, API behavior, and integrations immediately. Tools like Bunnyshelland Koala show how this practice turns feedback loops from days into minutes. Why I think this matters: Reviewers see the change in context, not in theory. Bugs and edge cases surface earlier, when they’re cheapest to fix. Developers get the psychological safety of knowing their code runs in a production-like setting before merge. This is the kind of workflow shift that makes teams not just faster, but calmer, because everyone knows what they’re reviewing and why it matters. Got a minute? Tell us what clicked (or didn't) 🎬 And that’s a wrap. Got a request, a bug to bust, or a genius trick to share? Send it our way. Back in your inbox next week. Cheers! Kinnari Chohan, Editor-in-chief SUBSCRIBE FOR MORE AND SHARE IT WITH A FRIEND! *{box-sizing:border-box}body{margin:0;padding:0}a[x-apple-data-detectors]{color:inherit!important;text-decoration:inherit!important}#MessageViewBody a{color:inherit;text-decoration:none}p{line-height:inherit}.desktop_hide,.desktop_hide table{mso-hide:all;display:none;max-height:0;overflow:hidden}.image_block img+div{display:none}sub,sup{font-size:75%;line-height:0}#converted-body .list_block ol,#converted-body .list_block ul,.body [class~=x_list_block] ol,.body [class~=x_list_block] ul,u+.body .list_block ol,u+.body .list_block ul{padding-left:20px} @media (max-width: 100%;display:block}.mobile_hide{min-height:0;max-height:0;max-width: 100%;overflow:hidden;font-size:0}.desktop_hide,.desktop_hide table{display:table!important;max-height:none!important}} @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} } @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} }