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

.gitlab-ci.yml

@@ -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/install_client_deps.sh
         - memopol migrate --noinput

.openshift/README.md

-The OpenShift `python` cartridge documentation can be found at:
-http://openshift.github.io/documentation/oo_cartridge_guide.html#python
-
-For information about .openshift directory, consult the documentation:
-http://openshift.github.io/documentation/oo_user_guide.html#the-openshift-directory

.openshift/action_hooks/README.md

-For information about action hooks, consult the documentation:
-
-http://openshift.github.io/documentation/oo_user_guide.html#action-hooks

.openshift/action_hooks/build

-export OPENSHIFT_PYTHON_WSGI_APPLICATION=src/memopol/wsgi.py

.openshift/action_hooks/deploy

-#!/bin/bash
-# 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
-
-pushd ${OPENSHIFT_REPO_DIR}
-	if [ -f ${OPENSHIFT_DATA_DIR}sentry ]; then
-	    pip2 --no-cache-dir install raven
-	fi
-
-	src/memopol/bin/install_client_deps.sh
-
-	mkdir -p wsgi/static
-
-	[ -f src/memopol/local_settings.py ] && rm src/memopol/local_settings.py
-	cp .openshift/local_settings.py src/memopol/local_settings.py
-
-	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
-popd

.openshift/cron/README.cron

-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: 
-   http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Automating_System_Tasks.html#s2-autotasks-cron-access
-
-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:
-http://openshift.github.io/documentation/oo_cartridge_guide.html#cron
-http://openshift.github.io/documentation/oo_user_guide.html#cron

.openshift/cron/daily/update_database

-#!/bin/bash
-set -x
-
-cd $OPENSHIFT_REPO_DIR
-export CLEAN=1
-nohup bin/update_all > $OPENSHIFT_LOG_DIR/update_all.log 2>&1 &

.openshift/cron/weekly/README

-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.
-

.openshift/cron/weekly/chrono.dat

-Time And Relative D...n In Execution (Open)Shift!

.openshift/cron/weekly/chronograph

-#!/bin/bash
-
-echo "`date`: `cat $(dirname \"$0\")/chrono.dat`"

.openshift/cron/weekly/jobs.allow

-#
-#  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).
-#
-chronograph
-

.openshift/cron/weekly/jobs.deny

-#
-#  Any script or job files listed in here (one entry per line) will NOT be
-#  executed (read as ignored by run-parts).
-#
-
-README
-

.openshift/local_settings.py

-"""
-Memopol local settings for Openshift.
-"""
-
-import os
-
-
-DATA_DIR = os.environ['OPENSHIFT_DATA_DIR']
-LOG_DIR = os.environ['OPENSHIFT_LOG_DIR']
-PUBLIC_DIR = os.path.join(os.environ['OPENSHIFT_REPO_DIR'], 'wsgi/static')
-
-
-DATABASES = {
-    'default': {
-        'NAME': os.environ['OPENSHIFT_APP_NAME'],
-        'USER': os.environ['OPENSHIFT_POSTGRESQL_DB_USERNAME'],
-        'PASSWORD': os.environ['OPENSHIFT_POSTGRESQL_DB_PASSWORD'],
-        'HOST': os.environ['OPENSHIFT_POSTGRESQL_DB_HOST'],
-        'PORT': os.environ['OPENSHIFT_POSTGRESQL_DB_PORT'],
-        'ENGINE': 'django.db.backends.postgresql_psycopg2',
-    }
-}
-
-
-ALLOWED_HOSTS = [
-    os.environ['OPENSHIFT_APP_DNS'],
-]
-
-
-SITE_ID = 1
-SITE_NAME = 'Memopol'
-SITE_DOMAIN = os.environ['OPENSHIFT_APP_DNS']
-
-ORGANIZATION_NAME = 'Memopol'

.openshift/markers/README.md

-For information about markers, consult the documentation:
-
-http://openshift.github.io/documentation/oo_user_guide.html#markers