Commit 9e0caea9 authored by okhin's avatar okhin 🚴

Removing openshift artifacts and updating the CI to remove egg-info before setup

parent bedba356
Pipeline #1105 passed with stage
in 10 minutes and 12 seconds
......@@ -48,6 +48,7 @@ django deploy:
- git fetch origin
- git reset --hard origin/master
- find . -name '*.pyc' -delete
- rm -r src/*.egg-info
- pip install -Ue .
- src/memopol/bin/
- memopol migrate --noinput
The OpenShift `python` cartridge documentation can be found at:
For information about .openshift directory, consult the documentation:
For information about action hooks, consult the documentation:
# This deploy hook gets executed after dependencies are resolved and the
# build hook has been run but before the application has been started back
# up again. This script gets executed directly, so it could be python, php,
# ruby, etc.
set -xe
source ${OPENSHIFT_HOMEDIR}app-root/runtime/dependencies/python/virtenv/bin/activate
pip2 install --no-cache-dir -U pip
pip2 install --no-cache-dir -Ue ${OPENSHIFT_REPO_DIR}
mkdir -p ${OPENSHIFT_DATA_DIR}media
if [ -f ${OPENSHIFT_DATA_DIR}sentry ]; then
pip2 --no-cache-dir install raven
mkdir -p wsgi/static
[ -f src/memopol/ ] && rm src/memopol/
cp .openshift/ src/memopol/
memopol migrate --noinput
memopol collectstatic --noinput
ln -sf ${OPENSHIFT_DATA_DIR}media wsgi/static/media
ln -sf ${OPENSHIFT_DATA_DIR}compress/CACHE wsgi/static/collected/CACHE
Run scripts or jobs on a periodic basis
Any scripts or jobs added to the minutely, hourly, daily, weekly or monthly
directories will be run on a scheduled basis (frequency is as indicated by the
name of the directory) using run-parts.
run-parts ignores any files that are hidden or dotfiles (.*) or backup
files (*~ or *,) or named *.{rpmsave,rpmorig,rpmnew,swp,cfsaved}
The presence of two specially named files jobs.deny and jobs.allow controls
how run-parts executes your scripts/jobs.
jobs.deny ===> Prevents specific scripts or jobs from being executed.
jobs.allow ===> Only execute the named scripts or jobs (all other/non-named
scripts that exist in this directory are ignored).
The principles of jobs.deny and jobs.allow are the same as those of cron.deny
and cron.allow and are described in detail at:
See: man crontab or above link for more details and see the the weekly/
directory for an example.
PLEASE NOTE: The Cron cartridge must be installed in order to run the configured jobs.
For more information about cron, consult the documentation:
set -x
export CLEAN=1
nohup bin/update_all > $OPENSHIFT_LOG_DIR/update_all.log 2>&1 &
Run scripts or jobs on a weekly basis
Any scripts or jobs added to this directory will be run on a scheduled basis
(weekly) using run-parts.
run-parts ignores any files that are hidden or dotfiles (.*) or backup
files (*~ or *,) or named *.{rpmsave,rpmorig,rpmnew,swp,cfsaved} and handles
the files named jobs.deny and jobs.allow specially.
In this specific example, the chronograph script is the only script or job file
executed on a weekly basis (due to white-listing it in jobs.allow). And the
README and chrono.dat file are ignored either as a result of being black-listed
in jobs.deny or because they are NOT white-listed in the jobs.allow file.
For more details, please see ../README.cron file.
Time And Relative D...n In Execution (Open)Shift!
echo "`date`: `cat $(dirname \"$0\")/chrono.dat`"
# Script or job files listed in here (one entry per line) will be
# executed on a weekly-basis.
# Example: The chronograph script will be executed weekly but the README
# and chrono.dat files in this directory will be ignored.
# The README file is actually ignored due to the entry in the
# jobs.deny which is checked before jobs.allow (this file).
# Any script or job files listed in here (one entry per line) will NOT be
# executed (read as ignored by run-parts).
Memopol local settings for Openshift.
import os
PUBLIC_DIR = os.path.join(os.environ['OPENSHIFT_REPO_DIR'], 'wsgi/static')
'default': {
'NAME': os.environ['OPENSHIFT_APP_NAME'],
'ENGINE': 'django.db.backends.postgresql_psycopg2',
SITE_NAME = 'Memopol'
For information about markers, consult the documentation:
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment