Currently, the CI service that deploys each branch to a live URL spins up Publish and API from this repo: https://github.com/dadi/publish-dev. However, the Publish repo already includes an API at test/api. It would be useful if the CI service used this one instead, rather than having to maintain a set of collections and configurations in two different places.
eduardoboucas
commented
5 years ago
Currently, the CI service that deploys each branch to a live URL spins up Publish and API from this repo: https://github.com/dadi/publish-dev. However, the Publish repo already includes an API at
test/api. It would be useful if the CI service used this one instead, rather than having to maintain a set of collections and configurations in two different places.