Forum Discussion
AST Configuration Assistance
Thanks, Mikesisav.
The umask value of 0027 ends with a 7, which will strip away all permissions for user "other". This will continue to happen even if you reinstall AST. To solve this, you need to either change the umask (by running a command like "umask 0022", which removes write permissions from users, "group" and "other", but leaves read and execute permissions intact) or manually add read (and execute, where appropriate) permissions to all files, recursively, in the directory after cloning the repo.
Running the umask command is the cleanest way to overcome this (but would require a fresh clone of the Git repo), but you might not have permissions to run that command. If you don't, or would prefer to preserve the configuration you've already done, you'll need to modify the permissions in your existing repo clone.
Hope that makes sense. Let me know if anything is unclear and, if you run through this, let me know how it goes.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com