oceandao icon indicating copy to clipboard operation
oceandao copied to clipboard

Port - Deploy staging server/environment.

Open idiom-bytes opened this issue 3 years ago • 0 comments

Problem:

Right now we have a need to test in staging, however some of our services/products overlap. A staging category inside Port for an example, may introduce a lot of noise in an already-noisy and verbose area.

Participants/Contributors/Testers may feel additional friction due to these elements, and we may experience adverse side effects.

Towards a solution:

One option is to make the category private, as it is now. However, this requires us to manually add members to a testing group so they can view what's happening inside of Staging-Port.

Another option is do deploy a 2nd version of Port, inside of test-port.oceandao.org This is simply another Port, so we can close that loop.

There is nothing else in here, except for the underlying discourse server/service, which is what we rely on as part our grants stack.

DoD:

  • [ ] Deploy a Discourse Staging Server/Service.
  • [ ] Update DNS @ test-port.oceandao.org
  • [ ] Update DNS @ port.oceandao.org
  • [ ] Delete "Staging" Category from https://port.oceanprotocol.com/
  • [ ] Update Staging Server + Airtable to point to staging port & discourse category IDs.

idiom-bytes avatar Mar 25 '22 18:03 idiom-bytes