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

Multiple Networks #27

Closed
1 task
faboweb opened this issue Oct 30, 2017 · 8 comments
Closed
1 task

Multiple Networks #27

faboweb opened this issue Oct 30, 2017 · 8 comments
Assignees
Labels
design-work-needed 🎨 issues that require design work before development stale

Comments

@faboweb
Copy link
Collaborator

faboweb commented Oct 30, 2017

As a user
I want to be able to select a blockchain-network
So I am able switch between production- and test-networks.

AC:

  • The user is able to select a network and persist that decision

Note:

  • What is the use case?
@faboweb
Copy link
Collaborator Author

faboweb commented Nov 2, 2017

Duplicate of #5

@faboweb faboweb marked this as a duplicate of #5 Nov 2, 2017
@faboweb
Copy link
Collaborator Author

faboweb commented Nov 7, 2017

For developers to use the test-net

@faboweb faboweb added the low priority has been discussed, will be addressed later label Nov 7, 2017
@jbibla
Copy link
Collaborator

jbibla commented Nov 27, 2017

ideally, i think this would be part of the welcome screen flow. but i believe the decision was to leave this until after launch.

@jbibla
Copy link
Collaborator

jbibla commented Jan 2, 2018

related to #372

@jbibla jbibla added this to the Post Launch milestone Aug 2, 2018
@NodeGuy NodeGuy removed this from the Post Launch milestone Aug 9, 2018
@faboweb faboweb removed the feature label Oct 17, 2018
@jbibla
Copy link
Collaborator

jbibla commented Mar 13, 2019

Nov 27, 2017
i believe the decision was to leave this until after launch.

wow. and so it is.

i think this is very important to consider as mainnet comes online. we should provide the option to switch from voyager testnet to mainnet and vice versa.

they should be running the same version of Gaia anyways, so hopefully this won't be too painful?

@faboweb

@faboweb
Copy link
Collaborator Author

faboweb commented Mar 13, 2019

👍 I think this is not that hard as we have dynamic backends already in place. If you come up with a design for it, I think we can make this happen.

@faboweb faboweb added the design-work-needed 🎨 issues that require design work before development label Mar 13, 2019
@jbibla
Copy link
Collaborator

jbibla commented Mar 13, 2019

@faboweb faboweb removed the low priority has been discussed, will be addressed later label Apr 5, 2019
@jbibla jbibla self-assigned this Jun 7, 2019
@stale
Copy link

stale bot commented Aug 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 23, 2019
@stale stale bot closed this as completed Aug 30, 2019
faboweb added a commit that referenced this issue Jun 2, 2020
Deploy production-api to test current setup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-work-needed 🎨 issues that require design work before development stale
Projects
None yet
Development

No branches or pull requests

3 participants