Warning
We're happy to announce the latest update of Portway. This release introduces our highly anticipated Web UI and contains significant structural changes. We strongly recommend making a full backup of your application folder before upgrading and following the migration steps below.
We've made the following changes in this version:
Fixes in v1.5.0:
- fix(security): encrypt connection strings after app start and sanitize HTTP methods and markdown fields
- fix(api): standardize HTTP responses for token auth and UI paths, resolve blocking calls, and centralize content type handling
- fix(network): use
SocketsHttpHandlerfor NTLM proxy auth and resolve CSP issues specific to IIS - fix(ui): correct login button alignment, fix font loading for nonstandard routing, and allow light mode on the logs console
- fix(core): replace empty catch blocks with proper error logging and decrease standard log verbosity
New features in v1.5.0:
- Web UI Implementation. We have rolled out a comprehensive web-based user interface, featuring a dedicated selection pane and control over environments and endpoints.
- .NET Project Structure Refactor. We have overhauled the repository to adopt .NET project structure best practices and moved remote scripts to local dependencies for better reliability.
- Token Management Enhancements. You can now edit token descriptions, and we've added logic to prevent duplicate token names.
- Empty Composite Requests. Added backend support for handling empty composite requests.
- Expanded Examples. We've added new configuration examples, including specific guides for Caddy reverse proxies.
Migration guide
Please follow the following steps for a safe upgrade path:
- Update Docker configurations. If you are running Portway in a container, please check the updated documentation regarding the ASP.NET port mappings, as these have changed.
- Review your repository structure. The old
.slnfile has been removed following the migration, andsettings.jsonhas been added to the.gitignore. Ensure your deployment scripts or workflows are updated accordingly. - Configure Web UI access. If you plan to access the admin console externally, ensure you explicitly enable external traffic routing in your settings.
Please make sure to check out our documentation first, it'll guide you through the most common pitfalls in setting up the application. Also, if you're running into issues, please make sure to create a new Issue! We'd be happy to help.
Full Changelog: v1.4.2...v1.5.0