Skip to content

Add veil-proxy as separate command line tool.#46

Merged
NullHypothesis merged 10 commits intomasterfrom
add-veil-proxy
Dec 25, 2024
Merged

Add veil-proxy as separate command line tool.#46
NullHypothesis merged 10 commits intomasterfrom
add-veil-proxy

Conversation

@NullHypothesis
Copy link
Copy Markdown
Contributor

This has several advantages:

  • There's no need to worry about moving shared code to a pkg/ directory.

  • Having a single version is much easier to keep track of than several versions that evolve independently.

  • A single directory is easier to keep track of than multiple.

This has several advantages:

* There's no need to worry about moving shared code to a `pkg/`
  directory.

* Having a single version is much easier to keep track of than several
  versions that increas independently.

* A single directory is easier to keep track of than multiple.
In particular:

* Move veil's, veil-verify's, and veil-proxy's configuration to the
  `config` package.

* Add `validate.Object`, which validates a given object and turns
  validation errors into joined errors.

* Unify the way we handle configuration across our three command line
  tools.
...and make both veil and veil-proxy use the same default port.
@NullHypothesis NullHypothesis merged commit 2a706d6 into master Dec 25, 2024
@NullHypothesis NullHypothesis deleted the add-veil-proxy branch December 25, 2024 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant