Currently we only have one API which is being used for production and test purposes (twitch-extension.danielheart.dev) and our goal is to make it easier for staging tests.
Proposal
Use Nginx to make a proxy for maintain the current api and create two new ones for the v1 development/production:
- twitch-extension.danielheart.dev (deprecate after 1 month after release the 1.0)
- consumer.newdomain(?).dev (production)
- consumer-dev.newdomain.dev (staging)
The service today is running under Rust Actix and would be good to have a auto-deployment on this tooling.
Maybe @gvieira18 can bring some ideas or if anyone wants to implement it, please ping me so I can provide a VPS for you to work with.
Currently we only have one API which is being used for production and test purposes (twitch-extension.danielheart.dev) and our goal is to make it easier for staging tests.
Proposal
Use Nginx to make a proxy for maintain the current api and create two new ones for the v1 development/production:
The service today is running under Rust Actix and would be good to have a auto-deployment on this tooling.
Maybe @gvieira18 can bring some ideas or if anyone wants to implement it, please ping me so I can provide a VPS for you to work with.