Skip to content

Rebrand to Proxima #210

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

Closed
in03 opened this issue Aug 15, 2022 · 2 comments · Fixed by #211
Closed

Rebrand to Proxima #210

in03 opened this issue Aug 15, 2022 · 2 comments · Fixed by #211

Comments

@in03
Copy link
Owner

in03 commented Aug 15, 2022

It's time for a rebrand! Resolve Proxy Encoder is a mouthful, so we're going to call this thing "Proxima".
We'll also change the CLI entrypoint. We may refactor the subcommands or save that for another PR, but there will be breaking changes in the way commands are invoked.
No changes in application behaviour beyond that is planned for this PR at this point.

@in03
Copy link
Owner Author

in03 commented Aug 15, 2022

/cib

@github-actions
Copy link
Contributor

Branch feature/issue-210-Rebrand-to-Proxima created!

github-actions bot pushed a commit that referenced this issue Aug 15, 2022
@in03 in03 closed this as completed in #211 Aug 16, 2022
in03 pushed a commit that referenced this issue Aug 16, 2022
* Create draft PR for #210

* feat(cli): Major app changes

- Rebranded "Resolve Proxy Encoder" as "Proxima"
- Changed CLI entrypoint from "rprox" to "proxima"
- Added full Celery sub command support

* refactor(figlet): Delete unused figlet font

* refactor: Rename all old names across files

* refactor: Update version_constraint_key

* docs(README): New features

- Cross off completed features
- Add features and enhancements to roadmap
- Reflect name change
- Warn dropped support for brokers other than Redis

* refactor: Update version_constraint_key

* docs(README): Grammar

* refactor: Update version_constraint_key
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant