Skip to content

pdr-web and pdr-websocket can be easily deployed and tested on each environment #117

@idiom-bytes

Description

@idiom-bytes

Problem:

Right now there is quite a bit of configuration between these apps, depending on which environment they'll be built. The documents, config files, and any bootstrapping configuration should be easy to follow and execute.

The following environments are important for us:

Local:
- Uses local `barge`, `pdr-web`, and `pdr-websockets`. Everything `runs on my laptop`.

Staging
- Uses `oasis testnet`. `pdr-websockets` is deployed on `DevVM`. `pdr-web` runs `on my laptop` and `connects to oasis testnet + DevVM`.

Production
- Uses `oasis mainnet`. `pdr-websockets` is deployed on `ProdVM`. `pdr-web` runs `on my laptop` or `vercel App` and `connects to oasis testnet` + `ProdVM`.

DoD:

  • README - Local deployment is easy to follow on readme and can be executed flawlessly by just following it step-by-step.
  • README - Staging deployment is easy to follow on readme and can be executed flawlessly by just following it step-by-step.
  • README - Production deployment is easy to follow on readme and can be executed flawlessly by just following it step-by-step.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions