This container automatically checks for scripts in `/config/init` and runs them at startup. This could be useful if you need to install additional applications into a worker container so it can execute jobs.
Note that any scripts will be run as `root` before permissions are altered in `/app` and `/config`. Anything that an init script does in either of these folders will be owned by `cronicle` when the container continues.
## Reverse Proxying
For a single manager behind a reverse proxy, you may need to specify a specific route for the web-socket connections.
#Importing and running additional scripts placed in /config/init
if[ -d /config/init ]
then
if["$(ls -A /config/init)"]
then
echo"Running additional startup scripts."
bash /config/init/*
else
echo"/config/init is empty - no additional startup scripts detected."
fi
else
echo"Directory /config/init not found. Creating."
mkdir /config/init
fi
if[ ! -d /config/cronicle ]
then
@ -80,8 +103,10 @@ then
then
echo"No config found. Copy config.json from the manager server and place it in /config/cronicle/conf dir."
cp -R /app/cronicle/conf /config/cronicle/conf
cp -r /app/cronicle/conf /config/cronicle/conf
rm -rf /config/cronicle/conf/config.json
rm -rf /app/cronicle/conf
ln -s /config/cronicle/conf /app/cronicle/conf
echo''
echo''
echo'*************************************'
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.