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

docs: add remote host docs #505

Closed
wants to merge 1 commit into from

Conversation

squidboylan
Copy link
Contributor

fixes #144

Signed-off-by: Caleb Boylan <[email protected]>
Copy link
Collaborator

@nabuskey nabuskey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know the issue is opened in this repo but the main documentation site is at https://github.com/cnoe-io/website

I'd say it should go to: https://cnoe.io/docs/reference-implementation/installations/idpbuilder/usage

Comment on lines +45 to +47
```shell
user@server:~/$ idpbuilder create --host SERVER.DOMAIN.NAME.HERE --use-path-routing
```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am a bit confused here. Is this for the path routing configuration only? As long as the ingress port is forward to the local machine, the host bit isn't needed? e.g.

ssh -L 8443:server:8443

This works for use with the --use-path-routing flag.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I decided to add a second option that avoids the need for port forwarding, that's what this option is. With this option you only change the ingress host and access the ingress over the network rather than a port forward to localhost, path routing is used to avoid the need for argocd.SERVER.DOMAIN and gitea.SERVER.DOMAIN dns records. If you think this option is unnecessary I can take it out, I only decided to document it because I had used it in my homelab. Lets continue discussion over on the other repo: cnoe-io/website#101

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see. Yea let's continue this and get it merged in the other repo.

@nabuskey
Copy link
Collaborator

We will get this done in cnoe-io/website#101

@nabuskey nabuskey closed this Mar 20, 2025
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.

A guide for running it in a remote machine
2 participants