A micro web framework for Windows PowerShell that creates standalone web servers with PowerShell code routing.
Flancy is a micro web framework for Windows PowerShell that creates standalone web servers with route-based request handling. It allows developers and system administrators to expose PowerShell commands and scripts through HTTP endpoints, solving the problem of easily making PowerShell functionality accessible via web interfaces.
Windows system administrators and PowerShell developers who need to quickly create web interfaces for their PowerShell scripts or expose automation tools as web services.
Developers choose Flancy because it provides the simplest way to create web servers in pure PowerShell with minimal boilerplate code, leveraging familiar PowerShell syntax while offering Flask-inspired routing patterns for rapid development.
A micro web framework for Windows PowerShell
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Routes HTTP requests directly to PowerShell code blocks, allowing developers to leverage existing scripts and commands without additional abstraction layers, as shown in the example with Get-Process.
Uses Flask-inspired syntax like Get '/' { ... } to define routes, enabling rapid setup of web servers with just a few lines of code, as demonstrated in the example script.
Includes native conversion of PowerShell objects to JSON using convertto-json, simplifying API response creation for data-heavy endpoints like processes listing.
Specifically designed for Windows PowerShell, making it ideal for sysadmins and developers in Windows environments who need to expose automation tools through web interfaces.
Due to Nancy's limitations, changes to routes or code require restarting the PowerShell session, hindering development workflow and dynamic updates, as admitted in the README.
Built for Windows PowerShell without cross-platform support, making it unsuitable for projects using PowerShell Core or requiring deployment on non-Windows systems.
The project acknowledges 'a ton of bugs' and has sparse documentation or community support, reducing reliability for production use compared to established frameworks.