Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create tool that translates Nginx configs to River configs #5

Open
bdaehlie opened this issue Mar 7, 2024 · 3 comments
Open

Create tool that translates Nginx configs to River configs #5

bdaehlie opened this issue Mar 7, 2024 · 3 comments
Labels
F-Tooling Functionality relating to tooling outside of River itself
Milestone

Comments

@bdaehlie
Copy link
Contributor

bdaehlie commented Mar 7, 2024

To make it easy for folks to move from Nginx to River we should create a tool that translates Nginx configs to River configs.

@jamesmunns jamesmunns added the F-Tooling Functionality relating to tooling outside of River itself label Mar 25, 2024
@jamesmunns jamesmunns added this to the Backlog milestone Mar 25, 2024
@jamesmunns
Copy link
Collaborator

Seems reasonable to me! I think this will come later after we have more config infra up and going, but I think it's a very reasonable tool to have, either inside or outside of River.

If anyone is aware of an existing NGINX configuration file parser in Rust, or a good reference to writing one, please feel free to share.

@jamesmunns
Copy link
Collaborator

Tagging the first RFC regarding config here: #13

It's likely that a text-only format (like TOML) will not be able to express all options that NGINX configs do.

We may need to select a specific subset, or wait for the "more complex" config option to be developed later.

@zackarychapple
Copy link

Just discovered this project and it is the first issue I looked for. Huge thumbs up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-Tooling Functionality relating to tooling outside of River itself
Projects
None yet
Development

No branches or pull requests

3 participants