NGINX has grown and changed significantly over the past few years. Since becoming a part of F5, we've been hard at work evolving our offerings to better serve the needs of the diverse global community of NGINX users. As a part of this evolution, we're re-imagining how we deliver content to our valued users and contributors. We're excited to announce that starting on May 15th, 2024, we will be migrating the NGINX blog from its current home on nginx.com to f5.com. This strategic realignment of our content will make it easier to find the information and resources you need.
A New Chapter for NGINX Content
After the migration, the most important technical enablement blogs, tutorials, customer stories, and thought leadership blogs on topics like application delivery and security that are currently on NGINX.com will migrate to f5.com, while nginx.org will become a technical-focused hub for all things related to our thriving NGINX community. With this migration, we set out to make your interactions with NGINX content more intuitive and rewarding. Expect a refreshed design, better navigation, and other new features that can help you access the content you need quickly. While the experience on our blog evolves, we’re committed to ensuring that the unique technical depth and community spirit you’ve come to expect from NGINX content doesn’t change.
Our Commitment to Open Source
We know that these changes may raise questions, especially within our open source community. Let us be clear: our commitment to open source is unwavering. That’s why we’re elevating and centralizing community-focused content with a dedicated home on nginx.org. Expect more content on open source tools, technical guides, and community initiatives. Your voices and contributions remain key in shaping the future of NGINX.
Join Us on This Journey
We’d like to invite you to be a part of this transition. On May 15th please take the time to familiarize yourself with NGINX content on f5.com. Update your bookmarks, and explore the new design. Be aware, the occasional glitch can happen with web migrations like this. If you spot anything, please let us know via X or LinkedIn. We’d also love to hear any suggestions you have for our content — your feedback is invaluable.
About the Author
Related Blog Posts
Secure Your API Gateway with NGINX App Protect WAF
As monoliths move to microservices, applications are developed faster than ever. Speed is necessary to stay competitive and APIs sit at the front of these rapid modernization efforts. But the popularity of APIs for application modernization has significant implications for app security.
How Do I Choose? API Gateway vs. Ingress Controller vs. Service Mesh
When you need an API gateway in Kubernetes, how do you choose among API gateway vs. Ingress controller vs. service mesh? We guide you through the decision, with sample scenarios for north-south and east-west API traffic, plus use cases where an API gateway is the right tool.
Deploying NGINX as an API Gateway, Part 2: Protecting Backend Services
In the second post in our API gateway series, Liam shows you how to batten down the hatches on your API services. You can use rate limiting, access restrictions, request size limits, and request body validation to frustrate illegitimate or overly burdensome requests.
New Joomla Exploit CVE-2015-8562
Read about the new zero day exploit in Joomla and see the NGINX configuration for how to apply a fix in NGINX or NGINX Plus.
Why Do I See “Welcome to nginx!” on My Favorite Website?
The ‘Welcome to NGINX!’ page is presented when NGINX web server software is installed on a computer but has not finished configuring