-
Notifications
You must be signed in to change notification settings - Fork 17
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
added hedgedoc guide #141
added hedgedoc guide #141
Conversation
✅ Deploy Preview for pomerium-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor change, and pointing out something that I'm not sure of.
Not sure why Netlify deploy didn't work.
- I am assuming the markdown worked for all the images
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Can we use relative links where possible (I commented on a few instances) pointing to the markdown documents directly?
- Style nit: we tend to just call "pomerium' pomerium, and not "pomerium proxy"
content/docs/guides/hedgedoc.md
Outdated
|
||
### Pomerium configuration | ||
|
||
Your Pomerium configuration file must include a [Cookie Secret](https://www.pomerium.com/docs/reference/cookie-secret) and a [Secret Key](https://www.pomerium.com/docs/reference/signing-key). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we could use relative urls here so docusaurus can detect any broken links.
content/docs/guides/hedgedoc.md
Outdated
- [Docker](https://www.docker.com/) | ||
- [Docker Compose](https://docs.docker.com/compose/install/) | ||
- A running Pomerium instance | ||
- A [preconfigured IdP](https://www.pomerium.com/docs/identity-providers) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use relative urls here and point to the markdown file so docusaurus can detect any broken inks?
content/docs/guides/hedgedoc.md
Outdated
|
||
## Integrate Pomerium with HedgeDoc | ||
|
||
HedgeDoc is open-source, self-hosted software that allows you to configure authentication and authorization with a [reverse proxy](https://docs.hedgedoc.org/guides/reverse-proxy/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HedgeDoc is open-source, self-hosted software that allows you to configure authentication and authorization with a [reverse proxy](https://docs.hedgedoc.org/guides/reverse-proxy/). | |
HedgeDoc is open-source, self-hosted software that allows you to configure authentication and authorization with a [reverse proxy](https://docs.hedgedoc.org/guides/reverse-proxy/). |
Not sure if the pre-pended spaces here are intentional.
content/docs/guides/hedgedoc.md
Outdated
|
||
![Pomerium IAP flow](../img/pom-auth-flow.png) | ||
|
||
### Set up your environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thoughts on linking to the docker-based quick start instead, and just referencing that we assume users have a completed version of the quick-start (docker based) as a starting point?
content/docs/guides/hedgedoc.md
Outdated
In your `docker-compose.yaml` file, add the following code under your Pomerium services: | ||
|
||
```yaml | ||
# verify: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems accidentally left behind?
content/docs/guides/hedgedoc.md
Outdated
Lastly, you must enable your Pomerium proxy to enable [Websocket Connections](https://www.pomerium.com/docs/reference/routes/websocket-connections): | ||
|
||
```yaml | ||
allow_websockets: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we could have a minimal but complete config.yaml that includes a route and policy pointing to hedgedoc here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we'd want a route:
routes:
- from: https://verify.localhost.pomerium.io
to: http://verify:8000
pass_identity_headers: true
allow_any_authenticated_user: true
- from: https://hedgedoc.localhost.pomerium.io
to: http://hedgedoc:3000
pass_identity_headers: true
allow_any_authenticated_user: true
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
Co-authored-by: cmo-pomerium <91488121+cmo-pomerium@users.noreply.github.com>
Co-authored-by: cmo-pomerium <91488121+cmo-pomerium@users.noreply.github.com>
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
content/docs/guides/hedgedoc.md
Outdated
environment: | ||
- CMD_DB_URL=postgres://hedgedoc:password@database:5432/hedgedoc | ||
- CMD_DOMAIN=localhost | ||
- CMD_URL_ADDPORT=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- CMD_URL_ADDPORT=true | |
- CMD_URL_ADDPORT=false |
content/docs/guides/hedgedoc.md
Outdated
Lastly, you must enable your Pomerium proxy to enable [Websocket Connections](https://www.pomerium.com/docs/reference/routes/websocket-connections): | ||
|
||
```yaml | ||
allow_websockets: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we'd want a route:
routes:
- from: https://verify.localhost.pomerium.io
to: http://verify:8000
pass_identity_headers: true
allow_any_authenticated_user: true
- from: https://hedgedoc.localhost.pomerium.io
to: http://hedgedoc:3000
pass_identity_headers: true
allow_any_authenticated_user: true
Co-authored-by: Caleb Doxsey <caleb@doxsey.net>
deleted hedgedoc img
deleted pomerium auth flow img for hedgedoc guide
deleted gh idp img for hedgedoc guide
deleted user details img for hedgedoc guide
deleted hedgedoc guide
deleted sign-in-prompt for hedgedoc guide
Added a HedgeDoc integration guide with screenshots and a diagram illustrating the auth flow with Pomerium's IAP services, the IdP, and the secured app.