Skip to main content
This page guides you through setting up a virtual environment for developing and debugging a global application. It is the third section of the tutorial. In this section, you will set up a demo CockroachDB cluster, initialize the database, and set up a virtual development environment.

Before you begin

  1. Complete the previous sections of the tutorial, ending with .
  2. On your local machine:

Set up a demo multi-region CockroachDB cluster

For debugging and development purposes, you can use the command. This command starts up a secure, nine-node demo cluster.
  1. To set up the demo multi-region cluster, run cockroach demo, with the --nodes and --demo-locality flags. The localities specified below assume GCP region names.
    Keep this terminal window open. Closing it will shut down the demo cluster.
  2. In a new terminal, load the dbinit.sql script to the demo database. This file contains the movr database schema that we covered in .
  3. Verify that the database schema loaded:
A production deployment should ideally have nodes on machines located in different areas of the world. You will deploy a multi-region CockroachDB cluster for this application using CockroachDB Standard in the final section of this tutorial series, .

Set up a virtual development environment

For debugging, use pipenv, a tool that manages dependencies with pip and creates virtual environments with virtualenv.
  1. Initialize the project’s virtual environment:
    pipenv creates a Pipfile in the current directory, with the requirements needed for the app.
  2. Install the packages listed in the Pipfile:
  3. Activate the virtual environment:
    From this shell, you can run any Python 3 application with the required dependencies that you listed in the Pipfile, and the environment variables that you listed in the .env file. You can exit the shell subprocess at any time with a simple exit command.
  4. To test out the application, you can run the server file:
    To run Python commands within the virtual environment, you do not need to add 3 to the end of the command. For example, running python3 server.py instead of the above command results in an error.
  5. Navigate to the application’s test URL, which defaults to http://127.0.0.1:5000/.
In production, it is often recommended to containerize your application and deploy it with a deployment orchestration tool like Kubernetes or with a serverless deployment service like Google Cloud Run. You will learn to deploy the application with Google Cloud Run in the final section of this tutorial series, .

Next steps

Now that you’ve set up a development environment, you can learn about .

See also