I like to show you today, how I update the style of the Network Configuration Generator using the UIkit CSS framework. As mentioned in my last post, the (most) functional requirements are already satisfied, but plain HTML is not the best look and feel for a Web service.
I’ll like to discuss the Mako Template Engine and the integration to the Network Configuration Generator in this post. The initial Use Case for the Web service includes the following requirements: dynamically detection of configuration variables, control structures within the templates and the bulk generation of configuration data.
I’ll like to provide a quick overview about the Flask microframework and the associated modules and libraries that I used during the development of the Network Configuration Generator. There are many tutorials out there on “how to develop a Flask application”, therefore I will limit the code examples to a minimum in this post. I’ll focus on the resources that I’ve used for learning.
Today I like to describe the target Use Case, functionality and structure of the Network Configuration Generator. Furthermore, I like to describe the Integration and API capabilities that should be implemented. At the end of this post, I discuss some limitations and functionalities that are considered out-of-scope for the first version.
I decide to create my first blog post series, which should provide a practical guideline to create your own web based Network Configuration Generator. I’ll like to focus on the overall approach and the tools/frameworks that I used during the creation of this tool. At the end of the series, you'll get a full configuration generator running as a Web service.