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

Rename rp script to rosenpass vpn #44

Open
tranzystorekk opened this issue Apr 10, 2023 · 4 comments
Open

Rename rp script to rosenpass vpn #44

tranzystorekk opened this issue Apr 10, 2023 · 4 comments

Comments

@tranzystorekk
Copy link

rtags also installs a rp binary to the bin folder, this can result in a cross-package name conflict on linux distributions.

@wucke13
Copy link

wucke13 commented Apr 15, 2023

Thank you for letting us know! Probably we will eventually move all the server sided codebase into something called rosenpassd, and then we could name the frontend CLI and configuration tool (kind of what rp is today combined with the CLI parser etc.) rosenpass, or rosenpassctl or something alike. @koraa what do you think?

@koraa
Copy link
Member

koraa commented Apr 16, 2023

I think rosenpassctl and rosenpassd are great names; only roadblock is we should probably bundle all the breaking changes in one release.

More reasons to add a staging branch

@koraa
Copy link
Member

koraa commented May 23, 2023

I changed my mind. I think it would be more preferable to have an rosenpass vpn command take the role of the rp script.

Similar to how in the git project there are multiple executables and the main executable just calls the others (i.e. calls rosenpass-vpn).

@koraa koraa changed the title rp script name clash with rtags project Rename rp script to rosenpass vpn May 23, 2023
@wucke13
Copy link

wucke13 commented Jun 9, 2023

So what would be the commands? Will there still be a client server architecture, where the server is configured by the client?

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

3 participants