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

Wish: Describe a running warpgate #22

Closed
stappersg opened this issue Apr 15, 2022 · 2 comments
Closed

Wish: Describe a running warpgate #22

stappersg opened this issue Apr 15, 2022 · 2 comments

Comments

@stappersg
Copy link
Contributor

Hi,

Here a person that has heared about teleport (but never used it (due the "high corporate appearance")).

I, seasoned sysadmin, miss a description how warpgate looks like when it is running.

This are the things that I made up myself:

  • warpgate listens by default on port 2222 and can be configured to listen on the default ssh port ( port 22)
  • Configuration lives in a sql database, configuration can be live updated
  • There is a CLI user interface and a webbased UI, both use the same REST API that listens at configurable port
  • Session recordings are stored as files. Recording sessions is optional
@stappersg
Copy link
Contributor Author

Reading https://github.com/warp-tech/warpgate/wiki/Getting-started did inform me about --config /etc/warpgate.yaml and web (web only?) user interface.

Where and how the (optional) session recordings are stored is still unclear.

I hope that the toplevel README gets the what I missed information.

@Eugeny
Copy link
Member

Eugeny commented Apr 15, 2022

Thanks for the feedback! I've updated the README. Re session recordings: if enabled, they're stored in the data directory / recordings (default: /var/lib/warpgate/recordings), but aren't meant to be accessed directly. You can view/download them from the admin UI.

@Eugeny Eugeny closed this as completed Apr 15, 2022
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

No branches or pull requests

2 participants