configuration/crontabs/README
... ...
@@ -1,7 +1,6 @@
1 1
This is the crontab repo and it contains one line crontabs for all the different environments.
2 2
These files are concatenated by the build-crontab-and-cp-files script. Any time the crontab should contain
3
-a user's home directory, instead write PATH_OF_HOME_DIR_TO_REPLACE; if the crontab should
4
-contain the path to the git directory, instead write PATH_OF_GIT_HOME_DIR_TO_REPLACE.
3
+a user's home directory, instead write PATH_OF_HOME_DIR_TO_REPLACE.
5 4
These are replaced by the build-crontab-and-cp-files script found under
6 5
configuration/environments_scripts.
7 6
configuration/environments_scripts/build-crontab-and-cp-files
... ...
@@ -5,9 +5,8 @@
5 5
# file for each user. It also takes the name of the user containing a copy of the git repo as well as the name of the
6 6
# dir within that user to go to. The created crontab for each user go into that user's home dir and are installed for
7 7
# that user too.
8
-# Within these crontab stubs, are certain string literals, which are replaced: PATH_OF_GIT_HOME_DIR_TO_REPLACE becomes
9
-# the absolute path to the git home dir, and PATH_OF_HOME_DIR_TO_REPLACE is changed to the path of the home directory
10
-# in which the crontab will be installed (ie. that user's home).
8
+# Within these crontab stubs, are certain string literals, which are replaced: PATH_OF_HOME_DIR_TO_REPLACE is changed
9
+# to the path of the home directory in which the crontab will be installed (ie. that user's home).
11 10
# Furthermore, within the users folder optional uid, gid and groups files an exist. uid should store the user's uid,
12 11
# gid the group id and groups should have secondary groups (one per line). The user is added to the secondary groups
13 12
# after all users are created.
... ...
@@ -104,7 +103,6 @@ if [[ -d "users" ]]; then
104 103
echo "">> $HOME_DIR/crontab
105 104
done
106 105
chown "$USERNAME":"$USERNAME" $HOME_DIR/crontab
107
- sed -i "s|PATH_OF_GIT_HOME_DIR_TO_REPLACE|${GIT_PATH}|g" "$HOME_DIR"/crontab # Sets correct path to the git repo within the crontab.
108 106
sed -i "s|PATH_OF_HOME_DIR_TO_REPLACE|${HOME_DIR}|g" "$HOME_DIR"/crontab # Sets the correct path to the home dir of the user whose crontab will be installed.
109 107
sed -i '/^$/d' $HOME_DIR/crontab # purges random empty lines.
110 108
echo "">>$HOME_DIR/crontab # Adds a newline
wiki/info/landscape/amazon-ec2.md
... ...
@@ -495,7 +495,7 @@ This script has a couple of arguments and options. The most important are the ar
495 495
1. Environment type.
496 496
2. User with a checked out Git copy.
497 497
3. The relative path within $2 to the Git copy.
498
-Ideally, we would have only a single checked out Git copy across all instances: one on the wiki user of the central. However, some crontabs require references to specific users' files, so we have the strings PATH_OF_GIT_HOME_DIR_TO_REPLACE & PATH_OF_HOME_DIR_TO_REPLACE, in the crontabs, as placeholders for the paths the string itself describes, which the build-crontab-and-cp-files script replaces with the right path.
498
+Ideally, we would have only a single checked out Git copy across all instances: one on the wiki user of the central. However, some crontabs require references to specific users' files, so we have the string PATH_OF_HOME_DIR_TO_REPLACE, in the crontabs, as placeholders for the paths the string itself describes, which the build-crontab-and-cp-files script replaces with the right path.
499 499
Have a look at the script itself for more details on the options and arguments.
500 500
501 501
## Reverse proxy automation