Core UW Scope components, including:

• Provider registry web client in web_registry.
• Server components:
  • Application server in server_flask.

With prerequisites:

• System dependencies installed (as in Installation of System Dependencies).
• Within an activated Pipenv shell (as in Initializing and Using Pipenv).
• Secrets provided (as in Providing Secrets).

A typical registry development environment then:

• Runs a registry web client locally, with hot reloading.
• Runs a Flask application server locally, with hot reloading.

invoke depend.install.all        # Install all dependencies.
invoke dev.registry.serve        # Serve the registry client, listening on `localhost:3000`, including hot reloading.
invoke dev.server.flask.serve    # Start Flask, listening on `localhost:4000`, including hot reloading.

The registry web client will then be accessible at http://localhost:3000/.

This project uses Invoke for task execution.

invoke -l

For example:

Available tasks:

  database.forward          Forward the database cluster, listening on `localhost:5000`.
  depend.install.all        Install all dependencies.
  depend.install.celery     Install celery dependencies.
  depend.install.flask      Install flask dependencies.
  depend.install.registry   Install registry dependencies.
  depend.install.tasks      Install tasks dependencies.
  depend.update.all         Update all dependencies.
  depend.update.celery      Update celery dependencies.
  depend.update.flask       Update flask dependencies.
  depend.update.registry    Update registry dependencies.
  depend.update.tasks       Update tasks dependencies.
  dev.registry.serve        Serve the registry client, listening on `localhost:3000`, including hot reloading.
  dev.server.flask.serve    Start Flask, listening on `localhost:4000`, including hot reloading.
  prod.registry.build       Build a bundle of the registry client.
  prod.registry.serve       Serve a bundle of the registry client, listening on `0.0.0.0:3000`.
  prod.server.flask.serve   Start Flask, listening on `0.0.0.0:4000`.

Runtime secrets are expected in the secrets directory.

• secrets/configuration/database_dev.yaml
• secrets/configuration/flask_dev_local.yaml
• secrets/configuration/documentdb.yaml
• secrets/configuration/instance_ssh.yaml

Contents of the database cluster can be directly inspected using:

• MongoDB Compass

  Free and open source. To establish a connection:

  • Obtain a connection string from Invoke task database.forward.
  • Paste the connection string in a new connection.
  • Select 'Fill in connection fields individually'.
  • Select 'More Options'.
  • Select SSL value 'Unvalidated'.

• Studio 3T

  Offers a non-commercial license. To establish a connection:

  • Obtain a connection string from Invoke task database.forward.
  • Paste the connection string via 'From URI...' in a new connection.

Requires availability of Git, of Javascript dependencies, and of Python dependencies.

Requires a Git executable on the path.

• On Windows, development has used Git for Windows.

For Javascript components, requires Node.js and the Yarn package manager.

• Node.js

  Installers: https://nodejs.org/en/download/

  Development has used version 14.x.

• Yarn

  npm install --global yarn
  

For Python components, requires Python and the Pipenv package manager.

• Python

  Development uses version 3.9.x.

  On Windows, specific versions can be installed: https://www.python.org/downloads/

  On Mac, specific versions are managed using pyenv: https://github.com/pyenv/pyenv

• Pipenv

  Pipenv manages creation of a Python virtual environment and pip installation of dependencies in that environment.

  Pipenv must be installed in an existing Python installation, typically a global installation:

  pip install pipenv
  

  The pipenv command is then available in that Python installation. For example:

  pipenv --version
  

  or as a module:

  python -m pipenv --version
  

  Depending on how a machine manages specific versions of Python, possibilities for accessing Pipenv include:

  • On Windows, install a specific version of Python in a known directory.
    Then use a full path to that installation:

    C:\Python39\Scripts\pip install pipenv
    C:\Python39\Scripts\pipenv --version
    

  • On a Mac:

    • Install pyenv using Homebrew or pyenv-installer.
    • Install Pipenv in any Python environment, such as the global environment.

    Pipenv will detect a Pipfile's desired version of Python and use pyenv to create an appropriate virtual environment.

    pip install pipenv
    pipenv --version
    

  With Pipenv installed and access to the pipenv command, see Initializing and Using Pipenv.

Pipenv creates a Python virtual environment that includes the dependencies in a Pipfile.lock. You must first initialize the virtual environment, then activate a shell within the virtual environment.

Ensure Pipenv is installed and the pipenv command is accessible, as in Installation of System Dependencies:

pipenv --version

Initialize a virtual environment by using the pipenv command to install the Pipfile.lock dependencies:

pipenv sync

Then activate a shell inside the created virtual environment.

On Windows:

• The pipenv shell implementation has issues (e.g., lacks command history). You may prefer:

  pipenv run cmd
  

• As a convenience, this project includes:

  pipenv_activate.bat
  

• When Pipenv is activated, the cmd environment will display (Pipenv):

  C:\devel\scope-web (Pipenv)>
  

On a Mac:

• The default pipenv shell works well.

  pipenv shell
  

Within a Pipenv shell, all commands benefit from dependencies in Pipfile and Pipfile.lock. See examples in Development Environment and in Using Invoke.

This project's development dependencies also include Pipenv, so the pipenv command is available locally (e.g., without a need to reference a specific global installation).

• To ensure all dependencies are current (i.e., match all Pipfile.lock and all yarn.lock):

  invoke depend.install.all
  

• To install a new dependency, update versions of all dependencies, and update Pipfile and Pipfile.lock, first change into the project directory and then issue use pipenv install:

  cd <directory>
  pipenv install <package>
  cd ..
  

• To install a new development dependency, update versions of all dependencies, and update Pipfile and Pipfile.lock, first change into the project directory and then issue use pipenv install --dev:

  cd <directory>
  pipenv install --dev <package>
  cd ..