-
Notifications
You must be signed in to change notification settings - Fork 289
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
Provide arm64 builds for shiny-server #532
Comments
I wrote down some notes a while back, they can still be valid https://github.com/lvalnegri/workshops-setup_cloud_analytics_machine/blob/master/raspberry-pi_jetson-nano.md |
@lvalnegri Thanks but I know how to compile shiny-server for arm, I even have blog posts about it, the idea behind this request is to make the installation process easier and less time-consuming. I thought since other RStudio development team already has a workflow for compiling for arm, they could implement it as well. |
It's a good idea, thank you for the suggestion. |
I'm curious if there's been any further discussion about, or planning for, pre-built ARM64 Shiny Server binaries. |
@mmuurr can you please explain / point me in the direction of the emulation you mentioned? |
@James-G-Hill AFAIK, only UTM allows to emulate x86_64 on macOS, though you're probably going to have very poor performance. In my case, I'm running aarch64 Linux virtual machines on macOS to automate the deployment of Shiny Server in a production environment. The lack of packages makes it very difficult to mirror our x86_64 production environment. A lot of cloud providers offer aarch64 VMs and it could be first step towards supporting them as well. It's great to have aaarch64 builds for RStudio-Server - even if they're experimental - and I would love to see the same thing for Shiny-Server. |
Can you consider providing arm64 builds for shiny-server the same way the RStudio IDE is providing experimental builds for arm64? If they already have the workflow in place I guess it would be simple to borrow from them?
The text was updated successfully, but these errors were encountered: