Wordpress & Git, urgent permissions issues, need help...


 
Thread Tools Search this Thread
Operating Systems OS X (Apple) Wordpress & Git, urgent permissions issues, need help...
# 1  
Old 02-22-2011
Wordpress & Git, urgent permissions issues, need help...

Heya,
So I recently upgraded my MacBook to a solid state drive, during the re-install of Snow Leopard I chose to abandon MAMP and use the built in Apache & PHP and in doing so moved my ~/Sites to /Library/WebServer/Documents from a Time Machine backup. During this transition the permissions were changed (I expected that but didn't change them directly).
All of the sudden Wordpress couldn't write to various places such as .htaccess, wp-content/uploads, wp-content/plugins, etc... So I changed the user and group to _www:_www correcting that issue, but then Git couldn't write to it's own directory.

At this point my permissions are spencerhill:staff 755 for folders and 644 for all files. And I'm completely confused as to how to untangle everything so it's set it the appropriate default user, group and symbolic privileges preventing me from doing any work. Please help!

Thank you!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Xalan & Xerces issues for Oracle Linux 6.6 & Solarisstudio12.3 C++ compiler for Linux

Hi Team, I am facing issue while using Xalan & Xerces for my application. Below are my environment details i am using :- Platform:- Oracle Linux 6.6 Compiler :- solarisstudio12.3 C++ compiler for Linux Below are the versions of Xalan & Xerces source code used to build the shared object... (0 Replies)
Discussion started by: agrachirag
0 Replies

2. UNIX Desktop Questions & Answers

Web Server/Permissions issues.

I do not know if this is the correct place to post this, and I have tried to trawl through relevant articles to fix the issue, but I am stumped. I have a server, log as root. var/www is root:root var/www/website-one is root:root var/www/website-one/neosmart-stream is root:root This... (10 Replies)
Discussion started by: LightCastle
10 Replies

3. UNIX for Dummies Questions & Answers

Permissions Issues FTP server

Hi all, Quick question, im going to find this a bit hard to explain but ill give it a go. Basically i have an admin account on an FTP server that i want to be able to control ALL files without having to use sudo (as i need to run cron scripts to move files that are owned by a number of... (2 Replies)
Discussion started by: mokachoka
2 Replies

4. Red Hat

Issues with LDAP user/group permissions on NFS share

I can't seem to make sense of this. $ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.2 Beta (Tikanga) $ $ mount /dev/sda2 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on... (6 Replies)
Discussion started by: dfinn
6 Replies

5. UNIX for Dummies Questions & Answers

Permissions & Webhosting

I just setup a Fedora10 box. I used yum to install : httpd php mysql mysql-server php-mysql Then I went out to wordpress (blogging software) and installed wordpress in /etc/httpd/wordpress I imported my wordpress database into mysql and its all working. Except for a few things. When I... (2 Replies)
Discussion started by: flood
2 Replies

6. Solaris

nslookup issues urgent

bwadmin@as1$ nslookup as2.synapse.com *** Can't find server name for address 192.168.0.16: No response from server *** Can't find server name for address 192.168.0.17: No response from server *** Default servers are not available /etc/resolv.conf have already 192.168.0.16/17 defined. I... (2 Replies)
Discussion started by: sandeepsudeep
2 Replies

7. HP-UX

To give the "unzip" permissions & "create" file permissions

Hi, I am a Unix Admin. I have to give the permissions to a user for creating new file in a directory in HP-Ux 11.11 system since he cannot able to create a new file in the directory. Thanks in advance. Mike (3 Replies)
Discussion started by: Mike1234
3 Replies

8. Shell Programming and Scripting

shell script performance issues --Urgent

I need help in awk please help immediatly. This below function is taking lot of time Please help me to fine tune it so that it runs faster. The file count is around 3million records # Process Body processbody() { #set -x while read line do ... (18 Replies)
Discussion started by: icefish
18 Replies

9. UNIX for Dummies Questions & Answers

problem with rdist & permissions

I have a .rdist & .sh files. shell script contains code like this rdist -h -f <rdist file> when this script executed i am getting the following error. rdist:<full path of files>: Permission denied. I verified the folder on the other system by connecting FTP.It doesn't has write... (0 Replies)
Discussion started by: Mar1006
0 Replies

10. UNIX for Dummies Questions & Answers

Permissions issues

I'm hoping this is a pretty simple question. I have a problem were memebers of a group can't delete or overwrite a file. The box is setup several users all part of the same group. Now default umask is 002. The problem I run into is there are processes that add to, del, and over write files. ... (3 Replies)
Discussion started by: lightspd
3 Replies
Login or Register to Ask a Question
GIT-INIT(1)							    Git Manual							       GIT-INIT(1)

NAME
git-init - Create an empty Git repository or reinitialize an existing one SYNOPSIS
git init [-q | --quiet] [--bare] [--template=<template_directory>] [--separate-git-dir <git dir>] [--shared[=<permissions>]] [directory] DESCRIPTION
This command creates an empty Git repository - basically a .git directory with subdirectories for objects, refs/heads, refs/tags, and template files. An initial HEAD file that references the HEAD of the master branch is also created. If the $GIT_DIR environment variable is set then it specifies a path to use instead of ./.git for the base of the repository. If the object storage directory is specified via the $GIT_OBJECT_DIRECTORY environment variable then the sha1 directories are created underneath - otherwise the default $GIT_DIR/objects directory is used. Running git init in an existing repository is safe. It will not overwrite things that are already there. The primary reason for rerunning git init is to pick up newly added templates (or to move the repository to another place if --separate-git-dir is given). OPTIONS
-q, --quiet Only print error and warning messages, all other output will be suppressed. --bare Create a bare repository. If GIT_DIR environment is not set, it is set to the current working directory. --template=<template_directory> Specify the directory from which templates will be used. (See the "TEMPLATE DIRECTORY" section below.) --separate-git-dir=<git dir> Instead of initializing the repository where it is supposed to be, place a filesytem-agnostic Git symbolic link there, pointing to the specified path, and initialize a Git repository at the path. The result is Git repository can be separated from working tree. If this is reinitialization, the repository will be moved to the specified path. --shared[=(false|true|umask|group|all|world|everybody|0xxx)] Specify that the Git repository is to be shared amongst several users. This allows users belonging to the same group to push into that repository. When specified, the config variable "core.sharedRepository" is set so that files and directories under $GIT_DIR are created with the requested permissions. When not specified, Git will use permissions reported by umask(2). The option can have the following values, defaulting to group if no value is given: o umask (or false): Use permissions reported by umask(2). The default, when --shared is not specified. o group (or true): Make the repository group-writable, (and g+sx, since the git group may be not the primary group of all users). This is used to loosen the permissions of an otherwise safe umask(2) value. Note that the umask still applies to the other permission bits (e.g. if umask is 0022, using group will not remove read privileges from other (non-group) users). See 0xxx for how to exactly specify the repository permissions. o all (or world or everybody): Same as group, but make the repository readable by all users. o 0xxx: 0xxx is an octal number and each file will have mode 0xxx. 0xxx will override users' umask(2) value (and not only loosen permissions as group and all does). 0640 will create a repository which is group-readable, but not group-writable or accessible to others. 0660 will create a repo that is readable and writable to the current user and group, but inaccessible to others. By default, the configuration flag receive.denyNonFastForwards is enabled in shared repositories, so that you cannot force a non fast-forwarding push into it. If you name a (possibly non-existent) directory at the end of the command line, the command is run inside the directory (possibly after creating it). TEMPLATE DIRECTORY
The template directory contains files and directories that will be copied to the $GIT_DIR after it is created. The template directory used will (in order): o The argument given with the --template option. o The contents of the $GIT_TEMPLATE_DIR environment variable. o The init.templatedir configuration variable. o The default template directory: /usr/share/git-core/templates. The default template directory includes some directory structure, some suggested "exclude patterns", and copies of sample "hook" files. The suggested patterns and hook files are all modifiable and extensible. EXAMPLES
Start a new Git repository for an existing code base $ cd /path/to/my/codebase $ git init (1) $ git add . (2) 1. prepare /path/to/my/codebase/.git directory 2. add all existing file to the index GIT
Part of the git(1) suite Git 1.8.5.3 01/14/2014 GIT-INIT(1)