The proposed scheme, developed by Dmitry Volodin of Gufo Labs, is designed for software publishers distributing software for EVALUATION PURPOSES and requiring a valid SSL certificate to allow users access to the web interface.
The proposed scheme offers a streamlined process for users by redirecting their browsers to a well-known entry point like https://go.example.com:<port>/ immediately after installation. It eliminates the need for additional user steps and ensures the private key remains secure and is not shared with any external parties.
At NOC, we are excited to announce a significant update to our official Telegram group! Our dedicated team has been hard at work, revamping the group to provide you with an even better experience. We are proud to present a brand new thematic group, now available in both English and Russian languages.
As part of our commitment to our community, we wanted to create a more inclusive and engaging space for NOC enthusiasts around the world. While our original group served as a hub for networking and discussions, we saw an opportunity to make it even better.
Creating exceptional software documentation is a pivotal ingredient for product success. The NOC Team has been on a relentless journey with Project Aegeus to make our documentation truly shine. While top-notch content is essential, the delivery process plays a crucial role in shaping the user experience. In this post, we're shifting our focus to delivery, where we'll reveal some tricks that can take your documentation from good to great.
Mkdocs, especially when adorned with the stylish mkdocs-material theme, is an outstanding tool for crafting project documentation. The outcome is a directory brimming with polished HTML files and static assets. Unlike popular CMS platforms like Joomla or WordPress, your output is a self-contained directory that doesn't rely on additional runtime services or databases. This independence makes it incredibly easy to serve your documentation directly to your audience. While services like "GitHub Pages" and "Read the Docs" have their allure, there's a compelling case for hosting your documentation independently. We, for instance, rely on the rock-solid Nginx web server. In the following sections, we'll offer you a glimpse into our setup and share some simple yet highly effective tweaks to enhance performance.
Previously, our documentation was split into English and Russian sections, which were not consistent with each other and had excessively complex structures. Worse, a large part of the documentation was still hosted on the old Confluence system. As a result, it was hard for users to get the required information, and hard for developers to keep documentation in tune.