test_or_die "chown apache2 and bind to developer"
group_perm /etc/apache2 /etc/bind
test_or_die "group perms on apache2 and bind"
+chown -R developer:developer /opt/feistymeow.org
+test_or_die "chown feisty meow to developer"
+group_perm /opt/feistymeow.org
+test_or_die "group perms on feisty meow"
##############
test_or_die "group perms on fred's apps"
harsh_perm /home/fred/.ssh
test_or_die "harsh_perm setting on fred .ssh"
-chown -R fred:fred /opt/feistymeow.org
-test_or_die "chown feisty meow to fred"
-group_perm /opt/feistymeow.org
-test_or_die "group perms on feisty meow"
group_perm /home/fred/apps/mapsdemo
test_or_die "group perms on mapsdemo app"
# install a better editor app.
-sep
+#sep
-echo "The script is about to install the bluefish editor and some dependencies.
-If the app is not already installed, then this process takes about one minute
-on a slow home DSL internet connection..."
+#echo "The script is about to install the bluefish editor and some dependencies.
+#If the app is not already installed, then this process takes about one minute
+#on a slow home DSL internet connection..."
-apt-get install -y bluefish &> "/tmp/install_bluefish-$(logname).log"
-test_or_continue "installing bluefish editor"
+#apt-get install -y bluefish &> "/tmp/install_bluefish-$(logname).log"
+#test_or_continue "installing bluefish editor"
##############
replacement="read only = no"
# we just always do the replacement now, after realizing the sentinel pattern
-# was acutally already in the file... too much subtlety can get one into trouble.
+# was actually already in the file... too much subtlety can get one into trouble.
sed -i "0,/$pattern/{s/$pattern/$replacement/}" /etc/samba/smb.conf
test_or_die "patching samba configuration to enable write acccess on user home dirs"
# sweet, looks like that worked...
echo Adding site avenger packages to composer.
# add in site avenger dependencies so we can build avcore properly.
-composer config -g repositories.siteavenger composer https://packages.siteavenger.com/
+pushd ~ &>/dev/null
+sudo -u $(logname) composer config -g repositories.siteavenger composer https://packages.siteavenger.com/
+popd &>/dev/null
+
+##############
+
+# make the apache umask set group permissions automatically, so we stop having weird
+# permission issues on temp dirs.
+
+sep
+
+grep -q "umask" /etc/apache2/envvars
+if [ $? -eq 0 ]; then
+ # already present.
+ echo the umask configuration for apache already appears to be set.
+else
+ echo "
+
+# set umask to enable group read/write on files and directories.
+umask 002
+
+" >> /etc/apache2/envvars
+ restart_apache
+ echo "successfully changed apache umask configuration to enable group read/write"
+fi
##############
##############