search

warp-contracts / warp-dre-node

A Delegated Resolution Environment for Warp Contracts.
3 stars 4 forks source link

fix: 'sync' endpoint does not work #15

Closed ppedziwiatr closed 1 year ago

ppedziwiatr commented 1 year ago

e.g. https://dre-1.warp.cc/sync?id=KT45jaf8n9UwgkEareWxPgLJk4oMWpI5NODgYVIF1fY readGwPubSubConfig is not a function

..probably after recent changes in env/configuration options handling.

  1. Fix the scheduleSync.js endpoint implementation
  2. update the readme and add info about the sync endpoint in the https://github.com/warp-contracts/warp-dre-node#5-endpoints section
koonopek commented 1 year ago

So I have pick up this issue, cause I wanted to get better understanding of DRE codebase.

As far as I understand we resigned from using configuration files, and switched to env variables with dotenv. The fix is pretty easy, however to test functionality, I need this configuration:

GW_PORT=''
GW_HOST=''
GW_USERNAME=default
GW_PASSWORD=''
GW_TLS=true
GW_ENABLE_OFFLINE_QUEUE=true
GW_LAZY_CONNECT=true
koonopek commented 1 year ago

Thanks @asiaziola !

koonopek commented 1 year ago

Waiting for merge #18

ppedziwiatr commented 1 year ago

So I have pick up this issue, cause I wanted to get better understanding of DRE codebase.

As far as I understand we resigned from using configuration files, and switched to env variables with dotenv. The fix is pretty easy, however to test functionality, I need this configuration:

GW_PORT=''
GW_HOST=''
GW_USERNAME=default
GW_PASSWORD=''
GW_TLS=true
GW_ENABLE_OFFLINE_QUEUE=true
GW_LAZY_CONNECT=true

Yeah, since the version in main branch is using the the same instance and credentials for both publish and subscribe - we cannot share them in public repo. That's why a separate - 'sub-only' account has been created (with a dedicated read-only Redis replica) - it is being developed within https://github.com/warp-contracts/warp-dre-node/pull/16 - but we need few more days to verify whether the new mechanism works stable (plus I believe there are still some issues with TLS - @Max-Levitskiy ?)

As far as I understand - Asia has already shared with you the credentials.

Max-Levitskiy commented 1 year ago

@ppedziwiatr more or less I have a solution. But not sure yet about the trust to the certificate. Need to solve this issue and we'll be able to enable TLS.