Open Tymmmy opened 5 months ago
@Tymmmy I need more info here:
auth.interledger.tech
ilp.interledger.tech
How about we use wallet.try.interledger.tech
for wallet related stuff and shop.try.interledger.tech
.
So for api we will have api.wallet.try.interledger.tech
and api.shop.try.interledger.tech
respectively.
Maybe it make sense to remove try
subdomain on this level to have the urls a bit shorter if this won't add confusion.
My personal preference would be without try ... so basically just wallet.interledger.tech
and shop.interledger.tech
For now, I will use following domains:
wallet.try.interledger.tech
shop.try.interledger.tech
What should be the connector address?
What should be the API url for try.interledger.tech/wallet ?
What should be the API url for try.interledger.tech/shop ?
What should be the URL for autopeer?
What should be the URL for auth (current is auth.rafiki.money)
What should be the ILP address? (current ilp.rafiki.money)
What should be the URL for admin (current admin.rafiki.money)
This is what I think. @raducristianpopa @beniaminmunteanu do you agree?
@dragosp1011 we have a little bit of a problem here. In order to have both rafiki.money and rafiki.boutique running simultenously with try.interledger.tech we would need to spawn new containers due to some URLs that are defined in the env right?
for example, every frontend app has env variable that points to backend and they are set to api.rafiki.money and api.rafiki.boutique ... they will need to point now to api.wallet.try.interledger.tech and api.shop.try.interledger.tech
But also rafiki auth container would need to be new due to rafiki auth server domain, and ofc also backend.
Please advise on how to proceed.
@dragosp1011 @golobitch we do need both to be running for now, the new site will be launched together with the new design. So not in the very near future, at least 2 months from now.
My proposal would be:
Wallet:
try.interledger.tech/wallet/*
- Wallet frontendtry.interledger.tech/wallet/api
- Wallet frontendtry.interledger.tech/wallet/ilp
- Rafiki backendtry.interledger.tech/wallet/gnap
- Rafiki authtry.interledger.tech/wallet/admin
or rafiki
- Rafiki frontendtry.interledger.tech/wallet/connector
- Connectorrafiki.money
Shop:
try.interledger.tech/shop/*
- Shop frontendtry.interledger.tech/shop/api
- Shop backendCan we have separate Nginx conf files for each location or everything will need to be in a single conf file? @golobitch
@golobitch everything is in env variables so we will ned to update them.
@Tymmmy we will need to update the email templates as well to point to env variables as there are some hardcoded links
@dragosp1011 Yes, email templated will all be updated also with new design in the near future
My proposal would be:
Wallet:
try.interledger.tech/wallet/*
- Wallet frontend
try.interledger.tech/wallet/api
- Wallet frontend
try.interledger.tech/wallet/ilp
- Rafiki backend
try.interledger.tech/wallet/gnap
- Rafiki auth
try.interledger.tech/wallet/admin
orrafiki
- Rafiki frontend
try.interledger.tech/wallet/connector
- Connector... every other sub-domain that we were using with
rafiki.money
Shop:
try.interledger.tech/shop/*
- Shop frontend
try.interledger.tech/shop/api
- Shop backendCan we have separate Nginx conf files for each location or everything will need to be in a single conf file? @golobitch
I like this one proposal.
We can have everything in separate conf files and then just do an include on main path.
@golobitch it has finaly been decided to have:
wallet.interledger-test.dev boutique.interledger-test.dev
EDIT - wallet.interledger-test.dev boutique.interledger-test.dev
We want to make a clear difference between Rafiki and Test Network. In doing so we will have new domain name for the following
rafiki.money - try.interledger.tech/wallet rafiki.boutique - try.interledger.tech/shop