Would love to have a declarative way to manage this application for portability and robustness.
Take github CI workflows, you're using YAML as the final source for how the workflow should behave and act. If you change that file, and make it known to the servers, then how the workflows are executed will change in that way as well. What I'm wanting is an option to do the same with passepartout, where all of the internal options, and especially the profiles and server setups, can be defined entirely in a YAML/TOML/Plist.
So on load, we would check that plist, and ensure that the state of the application matches what is configured, if there is a file in that location. That way if you have your own VPN hosts, you can define their locations in that text file, and any time you're setting up a new machine, it'll be configured automatically.
Would love to get the PR done for this, if the direction is good.
Would love to have a declarative way to manage this application for portability and robustness.
Take github CI workflows, you're using YAML as the final source for how the workflow should behave and act. If you change that file, and make it known to the servers, then how the workflows are executed will change in that way as well. What I'm wanting is an option to do the same with passepartout, where all of the internal options, and especially the profiles and server setups, can be defined entirely in a YAML/TOML/Plist.
So on load, we would check that plist, and ensure that the state of the application matches what is configured, if there is a file in that location. That way if you have your own VPN hosts, you can define their locations in that text file, and any time you're setting up a new machine, it'll be configured automatically.
Would love to get the PR done for this, if the direction is good.