Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New domain names for Test Network #1327

Closed
Tymmmy opened this issue Apr 25, 2024 · 12 comments
Closed

New domain names for Test Network #1327

Tymmmy opened this issue Apr 25, 2024 · 12 comments
Assignees

Comments

@Tymmmy
Copy link
Contributor

Tymmmy commented Apr 25, 2024

EDIT -
wallet.interledger-test.dev. ---> rafiki.money
boutique.interledger-test.dev ---> rafiki.boutique

We want to make a clear difference between Rafiki and Test Network.
In doing so we will have new domain name for the following

@github-project-automation github-project-automation bot moved this to Backlog in Testnet Apr 25, 2024
@Tymmmy Tymmmy assigned golobitch and unassigned golobitch Apr 25, 2024
@golobitch golobitch moved this from Backlog to In Progress in Testnet May 11, 2024
@golobitch
Copy link
Contributor

@Tymmmy I need more info here:

  • What should be the connector address?
    • connector.interledger.tech ?
  • 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)
    • Proposed: auth.interledger.tech
  • What should be the ILP address? (current ilp.rafiki.money)
    • Proposed: ilp.interledger.tech
  • What should be the URL for admin (current admin.rafiki.money)

@dragosp1011
Copy link
Contributor

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.

@golobitch
Copy link
Contributor

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

@dragosp1011
Copy link
Contributor

What should be the connector address?

  • connector.try.interledger.tech

What should be the API url for try.interledger.tech/wallet ?

  • api.wallet.try.interledger.tech

What should be the API url for try.interledger.tech/shop ?

  • api.shop.try.interledger.tech

What should be the URL for autopeer?

  • autopeer.try.interledger.tech

What should be the URL for auth (current is auth.rafiki.money)

  • auth.try.interledger.tech

What should be the ILP address? (current ilp.rafiki.money)

  • ilp.try.interledger.tech

What should be the URL for admin (current admin.rafiki.money)

  • admin.try.interledger.tech

This is what I think. @raducristianpopa @beniaminmunteanu do you agree?

@golobitch
Copy link
Contributor

@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.

@Tymmmy
Copy link
Contributor Author

Tymmmy commented May 16, 2024

@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.

@raducristianpopa
Copy link
Member

raducristianpopa commented May 16, 2024

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 or rafiki - 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 backend

Can we have separate Nginx conf files for each location or everything will need to be in a single conf file? @golobitch

@dragosp1011
Copy link
Contributor

@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

@Tymmmy
Copy link
Contributor Author

Tymmmy commented May 17, 2024

@dragosp1011 Yes, email templated will all be updated also with new design in the near future

@golobitch
Copy link
Contributor

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 or rafiki - 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 backend

Can 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.

@Tymmmy
Copy link
Contributor Author

Tymmmy commented Sep 24, 2024

@golobitch it has finaly been decided to have:

wallet.interledger-test.dev
boutique.interledger-test.dev

@Tymmmy
Copy link
Contributor Author

Tymmmy commented Nov 5, 2024

Done

@Tymmmy Tymmmy closed this as completed Nov 5, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Testnet Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants