Repository navigation
README: the web UI in screenshots, 0.8.0 throughout, the scattered merge text put back - #5
Merged
Merged
Conversation
…(the page, 24 of demo 30's flows pasted with L7 on, the two policies, /download by id, /health, a refusal); versions to 0.8.0 (spec table, fork note with the OCI chart, binaries URL); the merge paragraphs back under 1b (they had scattered under fromCIDR with a duplicate and an empty fence); serve's --allowed-origins and --auth-token, /generate's query parameters; the output examples as 0.8.0 writes them (names, managed-by labels, the description, DNS on ANY/53); the download and health panels wrap long lines like the generate result (one CSS selector, one test)
…g-test-captures paragraph go (they were already on develop — the fork's own page carries them now), the clone URL and the binaries URL name the project with the version a placeholder, the web UI section names no lab
ephico2real2
force-pushed
the
docs/readme-0.8.0-web-ui
branch
from
September 16, 2026 07:00
c80694c to
a1a9dee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Screenshots of the deployed 0.8.0 page in a new The web UI section: the page, 24 HTTP flows pasted with layer-7 on, the two policies generated,
/download/{id}by the filled-in id,/health, and a refusal (a policy name can only be set when the flows produce a single policy: got 2).This README is the project's —
developis offered upstream as onzack#3, so nothing on it is the fork's. The second commit removes what claimed otherwise, including two pieces that were already ondevelopbefore this PR (the Fork note with the fork's Helm repo and image, the Running-test captures paragraph): the clone URL and the binaries URL name the project (the version a placeholder), the web UI section names no lab. The fork's own artefacts — the Helm repo, the OCI chart, the image, the binaries, the lab's captures — now live on the fork's gh-pages page: https://github.com/ephico2real2/cf2cnp/tree/gh-pages#testing-the-fork.The rest of the review:
serve's--allowed-originsand--auth-tokenwere missing from the flags table;/generate's?l7,?dnsVisibility,?dnsProfile,?dnsResolver,?excludefrom the endpoints tabledestination-service-destination-component, addsmanaged-bylabels, writes the description from the rules and the DNS rule asANY/53— replaced with what the 0.8.0 binary wrote for the README's own input<pre>scrolled a long description line sideways while the generate result wraps — one selector, one testStill on
developand worth a decision before upstream sees it:CHANGELOG.mdis titled "the fork's releases", and the spec table's version rows (0.5.0 – 0.8.0) are the fork's numbering; upstream is at chart 0.4.0 / app 0.3.1.