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
On the "nix-shell --command "rails new . --force --skip-bundle; bundler lock"" Nix siezes up and logs me out. #1
Comments
And thanks, btw, for posting this repository! It's the most helpful thing in all of my searching trying to get nixos set up for Ruby! |
Got to thinking and thought it might be useful to share the gemset.nix file my system is producing, in case there are variances with what is expected
|
And I did change the version of ruby, in my experimenting, but I was getting the same problem with the 5.0.1 |
The first Gemfile.lock as well, again I know the version is 5.1.0, but the same thing was happening when I had it at 5.0.1. If you want I could clone a fresh one and do it again and show you the state of each file if you think that would be useful. ' PLATFORMS DEPENDENCIES BUNDLED WITH |
Acaba de ver que eres de Espana. Mi esposa es de Peru, asi que hablamos Espanol en la casa. |
I'm still a bit of a NixOS / Nix noob. So apologies in advance for my ignorance on display.
I've tried going about this with both the script/init file as well as manually and I've narrowed it down to the
nix-shell --command "rails new . --force --skip-bundle; bundler lock"
line. It reaches
and then logs out my nixos user. The accompanying log is 'unexpected Nix daemon error: interrupted by the user"
I'm using
NixOS 17.09pre106230.e89343dc08 (Hummingbird) 64-bit
Any help, even if just pointing me in a general direction, would be greatly appreciated!
The text was updated successfully, but these errors were encountered: