- Ecom is a django single page (SPA) web app running on apache as a web server.
- Apache proxies requests to the WSGI application which invokes the python application itself.
- The latest multiprocessing apache module is used to create parallel replicas of our app. Each apache "event_worker" is 1 process and 1 python app. 1 process launches multiple threads so that each app is concurrently accessed by multiple users. The big performance advantage of the "event_worker" over the regular worker is that once the connection is idle, the thread gives back the control of the socket to Apache.
- There is a full decoupling of the front end with React written in JSX which is then tranpiled to vanilla javascript through the dev and build scripts specified in the package.json file.
- React components live in the "ecom/frontend" django app. Redux is extensively used to manage state in order to guarantee a single source of truth and avoid having the multiple components managing state. Each component gets the state as props from the store.
- The continuous delivery pipeline is triggered by a git push to origin by any member that has write access to this repo.
- The git push triggers a webhook where both github and jenkins are listening on in order to build the jenkins pipeline.
- Specifications of the Jenkinsfile can be found above.
- Any push to origin will trigger both webhooks however jenkins will only build the source code located in the "master" branch.
- Secure emailing with analytics: sending emails with sendgrid's service using a Recaptcha secured form
- Feature 2
- Feature 3
virtualenv -p python3.8 .
source bin/activate
pip install -r requirements.txt
python manage.py runserver
npm i
npm run dev
echo '*' > .mypy_cache/.gitignore
pip freeze > requirements.txt
export LANG=en_US.UTF-8 unset PYTHONIOENCODING
- Any changes to the requirements file?
- Any changes to the .env file?
git rm -r --cached .