Any chance of getting BSD support?
Closed this issue · 2 comments
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Network project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe your problem
I am running FreeBSD with Bash and the latest version of Go installed. I would very much like to use the cli but the install script states "ory/ crit platform freebsd/amd64 is not supported. Make sure this script is up-to-date and file request at https://github.com/ory//issues/new". Is there any chance of getting FreeBSD support added to the installer and the cli if it also lacks it?
Also, in the error message from the install script, it says to file a request at https://github.com/ory//issues/new. That page doesn't exist. I'm hoping it meant this repository.
Whether there's a possibility of adding support or not, thank you for your work.
Describe your ideal solution
Ideally, I would like to be able to use the exact same commands under FreeBSD that I can on Linux. Most *NIXs aren't terribly different so I am hoping adding BSD support wouldn't be much extra work.
Workarounds or alternatives
I've considered pulling down the cli code and manually compiling it but the fact that the installer specifically states it isn't compatible with FreeBSD makes me leery to try it.
Version
https://raw.githubusercontent.com/ory/meta/master/install.sh
Additional Context
No response
We'd love to have FreeBSD supported! We disabled FreeBSD builds a while ago due to cross compile issues. Maybe they're resolved now? Fix would need to go into https://github.com/ory/xgoreleaser
Hello contributors!
I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue
- open a PR referencing and resolving the issue;
- leave a comment on it and discuss ideas on how you could contribute towards resolving it;
- leave a comment and describe in detail why this issue is critical for your use case;
- open a new issue with updated details and a plan for resolving the issue.
Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.
Unfortunately, burnout has become a topic of concern amongst open-source projects.
It can lead to severe personal and health issues as well as opening catastrophic attack vectors.
The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.
If this issue was marked as stale erroneously you can exempt it by adding the backlog
label, assigning someone, or setting a milestone for it.
Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!
Thank you 🙏✌️