Skip to content

Latest commit

 

History

History
88 lines (67 loc) · 3.83 KB

1d_BlenderCloud.md

File metadata and controls

88 lines (67 loc) · 3.83 KB
Raw

Blender Cloud - Part D

Step 1: Install Docker

In order to run Pillar, we need to make sure that we have some services available. MongoDB is a database. Redis is a caching system. RabbitMQ is a messenger. Fortunately, the default Docker images for both of these will result in a working system. Those interested in Docker should read the Docker Compose YAML file.

Follow the instructions here:
Install Docker
Post Install
Note: Make sure that you add your user to the docker group.

Step 2: Run Docker Images

Create a directory for your data storage and change the ownership to your user:

sudo mkdir -p /data/storage
sudo chown you:yourgroup /data/storage

Run the following docker containers, which should download automatically if they are not already on your machine:

docker run -d -v /data/db:/data/db -p 27017:27017 --name mongo mongo
docker run -d -p 6379:6379 --name redis redis
docker run -d -p 5672:5672 --name rabbit rabbitmq

Add the following to /etc/hosts:
127.0.0.1 localhost id.local cloud.local elastic kibana mongodb mongo redis

Step 3: Configure Blender_Cloud

Reference: Blender-Cloud and Pillar Configuration At this point in the installation process, we are ready to configure the application and run it. The first step involves copying an example configuration file. The following step sets up the server.

Copy the example config_local and edit the file as neccessary. cp config_local.example.py config_local.py

  • Change secret key (per Pillar installation tips)
  • Change port on cloud.local to 5000

You should also add JWT keys to your config_local. The following commands are from blender-cloud/jwtkeys/README.md:

openssl ecparam -genkey -name prime256v1 -noout -out es256-private.pem
openssl ec -in es256-private.pem -pubout -out es256-public.pem

At the end of config_local, set the location of these keys to these values:

import datetime
FLAMENCO_JWT_TOKEN_EXPIRY = datetime.timedelta(hours=4)
FLAMENCO_JWT_PRIVATE_KEY_PATH='/location/to/es256-private.pem'
FLAMENCO_JWT_PUBLIC_KEYS_PATH='/location/to/es256-public.pem'

Note: You may want to copy-paste the above. Note the singular/plural distinction in PRIVATE_KEY and PUBLIC_KEYS

In runserver.py, on the line app.run('::0', 5001, debug=True) change 5001 to 5000.

Run the initial setup, which will create the database. Note: MongoDB Docker must be running.
poetry run ./manage.py setup setup_db <email>

The output will end with something like:

Created user 6046325c854cf1f6ddcd1324
2021-03-08 14:19:08,816     INFO pillar.api.projects.utils Creating new project "Default Project" for user 6046325c854cf1f6ddcd1324
2021-03-08 14:19:08,912     INFO pillar.api.projects.utils Created project <project_id> for user 6046325c854cf1f6ddcd1324

When the output is finished, copy the value of <project_id> and assign it as value for MAIN_PROJECT_ID in config_local.py. The <project_id> will be the MongoDB ID, an umpteen-digit hex number.

Step 6: Run Blender-Cloud Server

You can now run the server. From the blender-cloud directory, issue the command:
poetry run ./manage.py runserver

To test the server:
curl cloud.local:5000

At this point you should get a welcome redirection.

To confirm the website is available:
curl cloud.local:5000/welcome Note: If you get template issues, make sure you ran gulp in all relevant directories.

You can also install py.test. In the blender-cloud directory, run:

poetry run pip install pytest    
poetry run pip install pytest-cov   
poetry run py.test

Note: Some tests will fail, but that should be okay at this point.