You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While doing some research into the project, I stumbled upon an issue (see #5) asking for a mechanism to translate a nginx configuration into a river configuration.
While quite a few things are easily translateable, I was thinking about features/directives that do not exist yet, such as ssl_engine that allows to use a custom provider for certificates, which could be used used to use an HSM as a key storage.
While the roadmap provides a neat overview of planned features, I was still wondering, if there are plans to reach somewhat of feature equivalency with certain proxy servers. I'm fully aware that a total feature equivalency is not really feasible but if getting somewhat close to, e.g. nginx's feature set is on the table.
The text was updated successfully, but these errors were encountered:
The initial development contract expired a few months ago and we are working on plans for further development. In the meantime there are no resources assigned.
That's really sad to hear. I didn't expect that funding was an issue, judging how well pingora was received and subsequently the idea of building a reverse proxy based on it.
While doing some research into the project, I stumbled upon an issue (see #5) asking for a mechanism to translate a nginx configuration into a river configuration.
While quite a few things are easily translateable, I was thinking about features/directives that do not exist yet, such as
ssl_engine
that allows to use a custom provider for certificates, which could be used used to use an HSM as a key storage.While the roadmap provides a neat overview of planned features, I was still wondering, if there are plans to reach somewhat of feature equivalency with certain proxy servers. I'm fully aware that a total feature equivalency is not really feasible but if getting somewhat close to, e.g. nginx's feature set is on the table.
The text was updated successfully, but these errors were encountered: