This repository is the base for the IBM Technical Leadership Council Brazil (TLC-BR) website. In order to facilitate the deployment, we've used Wagtail CMS and IBM Cloud (CIO) to host the application.
Access to this website is currently restricted to IBM'ers only, through the following link:
 |
 |
 |
 |
You can setup a local development environment on your own workstation using Vagrant, Docker or Python Virtualenv, as described on the sections below:
Once you've installed the necessary dependencies run the following commands:
git clone git@github.com:fsilveir/tlc-brazil.git
cd tlc-brazil
vagrant up
vagrant ssh
# then, within the SSH session:
./manage.py runserver 0.0.0.0:8000The site will now be accessible at http://localhost:8000/ and the Wagtail admin interface at http://localhost:8000/admin/.
Log into the admin with the credentials admin / changeme.
Use Ctrl+c to stop the local server. To stop the Vagrant environment, run exit then vagrant halt.
Run the following commands:
git clone git@github.com:fsilveir/tlc-brazil.git
cd tlc-brazil
docker-compose up --build -d
docker-compose run app /venv/bin/python manage.py load_initial_data
docker-compose upThe site will now be accessible at http://localhost:8000/ and the Wagtail admin interface at http://localhost:8000/admin/.
Log into the admin with the credentials admin / changeme.
Important: This docker-compose.yml is configured for local testing only, and is not intended for production use.
To tail the logs from the Docker containers in realtime, run:
docker-compose logs -fYou can run the site locally without setting up Vagrant or Docker and simply use Virtualenv, which is the recommended installation approach for Django itself.
- Python 3.4, 3.5 or 3.6
- Virtualenv
- VirtualenvWrapper (optional)
With PIP and virtualenvwrapper installed, run:
mkvirtualenv tlc-brazil
python --version
Confirm that this is showing a compatible version of Python 3.x. If not, and you have multiple versions of Python installed on your system, you may need to specify the appropriate version when creating the virtualenv:
deactivate
rmvirtualenv tlc-brazil
mkvirtualenv tlc-brazil --python=python3.6
python --version
Now we're ready to set up the project itself:
cd ~/dev [or your preferred dev directory]
git clone git@github.com:fsilveir/tlc-brazil.git
cd tlc-brazil
pip install -r requirements/base.txt
Next, we'll set up our local environment variables. We use django-dotenv
to help with this. It reads environment variables located in a file name .env in the top level directory of the project. The only variable we need to start is DJANGO_SETTINGS_MODULE:
$ cp tlcbr/settings/local.py.example tlcbr/settings/local.py
$ echo "DJANGO_SETTINGS_MODULE=tlcbr.settings.local" > .env
To set up your database and load initial data, run the following commands:
./manage.py migrate
./manage.py load_initial_data
./manage.py runserver
Log into the admin with the credentials admin / changeme.
- First you'll need an IBM Cloud account. Visit the following depending on your requirements:
- IBM Cloud (publicly available)
- IBM Cloud (CIO) (restricted to IBMer's)
- After creating an account, you'll need to install the IBM Cloud CLI, instructions can be found at the following:
- After successfully installing the IBM Cloud CLI, you'll need to configure it and perform the login with your credentials, as instructed at the following link:
- After successfully performing login, you must customize your manifest.yml file in order to successfully deploy the application to IBM Cloud, you can use the following as reference:
---
applications:
- name: tlcbr
memory: 256M
instances: 1
host: tlcbr
path: .
buildpack: python_buildpack
random-route: false
env:
DJANGO_DEBUG: off
DJANGO_SETTINGS_MODULE: tlcbr.settings.production
DJANGO_SECURE_SSL_REDIRECT: on
DJANGO_SECRET_KEY: changeme- After successfully preparing your manifest, you can push your application to IBM Cloud by using
ibmcloud cf push, if all steps were followed accordingly, you should see a similar output:
[fsilveir@fsilveir tlcbr]$ ibmcloud cf push
Invoking 'cf push'...
Pushing from manifest to org FELIPE_STUDY / space dev as fsilveir@br.ibm.com...
Using manifest file /home/fsilveir/git/tlcbr/manifest.yml
Creating app tlcbr in org FELIPE_STUDY / space dev as fsilveir@br.ibm.com...
OK
Using route tlcbr.w3ibm.mybluemix.net
Binding tlcbr.w3ibm.mybluemix.net to tlcbr...
OK
Uploading tlcbr...
Uploading app files from: /home/fsilveir/git/tlcbr
Uploading 10.1M, 378 files
Done uploading
OK
Starting app tlcbr in org FELIPE_STUDY / space dev as fsilveir@br.ibm.com...
Downloading python_buildpack...
Downloaded python_buildpack
Creating container
Successfully created container
Downloading app package...
Downloaded app package (15.9M)
Staging...
-------> Buildpack version 1.5.15
[ ... ]
Staging complete
Uploading droplet, build artifacts cache...
Uploading build artifacts cache...
Uploading droplet...
Uploaded build artifacts cache (78.6M)
Uploaded droplet (108.9M)
Uploading complete
Destroying container
Successfully destroyed container
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
1 of 1 instances running
App started
OK
App tlcbr was started using this command `uwsgi --http-socket=:$PORT --master --workers=2 --threads=8 --die-on-term --wsgi-file=tlcbr/wsgi_production.py --static-map /media/=/app/tlcbr/media/ --offload-threads 1`
Showing health and status for app tlcbr in org FELIPE_STUDY / space dev as fsilveir@br.ibm.com...
OK
requested state: started
instances: 1/1
usage: 256M x 1 instances
urls: tlcbr.w3ibm.mybluemix.net
last uploaded: Wed Dec 26 13:26:23 UTC 2018
stack: cflinuxfs2
buildpack: python_buildpack
state since cpu memory disk details
#0 running 2018-12-26 11:32:33 AM 0.0% 0 of 256M 0 of 1G
For more information on how to work with cloudfoundry manifests, check the following link: