Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
3 tasks
idiom-bytes opened this issue Aug 11, 2023 · 0 comments
Open
3 tasks
Labels
Type: Enhancement New feature or request

Comments

@idiom-bytes
Copy link
Member

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.
@idiom-bytes idiom-bytes added the Type: Enhancement New feature or request label Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant