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

Add instruction to fix permissions for yarn home config dir #167

Open
natuk opened this issue Dec 18, 2019 · 4 comments
Open

Add instruction to fix permissions for yarn home config dir #167

natuk opened this issue Dec 18, 2019 · 4 comments

Comments

@natuk
Copy link

natuk commented Dec 18, 2019

describe the issue

The dependency installation script for Ubuntu 18.04 installs yarn under sudo. This creates a ~/.config directory with root permissions. When I execute arches-project create my_project during installation I get a permission error. If I fix the permissions to my user and run it again, it works OK. I suggest adding a line to instruct the user to check that the permissions are correct before creating the project.

please add links to existing docs or code (if relevant)

New instructions should be added here:
https://arches.readthedocs.io/en/stable/installation/

which release does this issue concern?

stable

@natuk
Copy link
Author

natuk commented Dec 19, 2019

Just noticed that the permissions for the ~/.config dir are set to the user (not root) on Ubuntu 18.04 desktop. So this issue only applies to Ubuntu 18.04 server.

@mradamcox
Copy link
Member

@chiatt If you are able to fix the ubuntu setup script (best case scenario), then we won't actually need to change the documentation.

@chiatt
Copy link
Member

chiatt commented Oct 28, 2020

@mradamcox I briefly took a swing at fixing this in the install script. I tried installing without sudo, but ran into errors. I'm sure there's a solution, but a bit more time needs to be spent on it. I created an issue in Arches to address it there if we can: archesproject/arches#6805

@mradamcox
Copy link
Member

I put some thoughts in that other ticket.

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

No branches or pull requests

4 participants