My understanding is that you want to run nodes in a container, with a pre-existing network to connect to.
If you want to do that right now, you’ll have to setup your own network, as Maidsafe don’t have one running publicly. That can be on Digital Ocean, or AWS, or wherever you want to run one. However, for the time being, you need to roll it yourself.
We have a tool that we use for launching testnets on Digital Ocean, and that’s what David is referring to. If you have some technical knowledge, it’s not too hard to use that tool to roll your own network, it’s just that you need to have your own Digital Ocean account. The tool is here.
It’s my assumption that team maidsafe would come with one, but I’m happy to do the “start 11 nodes on one raspberry pi and have other people join me” thing again.
Especially since I still prefer IPv6 over IPv4. I’m not sure if that has changed over the past months/years.
And why would I want to start one on Digital Ocean or Amazon?
I thought the whole idea of maidsafe was not to be reliant on monopolies and olipolies?
I suspect the script they use to create it works with DO, so it was a suggestion to make it easy, as otherwise you’ll have to do more work to set it up.
Yeah, although I think it’s just worth saying that there’s a distinction between being reliant on a service like DO or just using it. The network won’t rely on any given cloud provider for its existence, but I don’t think people would necessarily be opposed to nodes that happened to run on DO, AWS, Azure or whatever. I can only speak for myself, but I wouldn’t be.
We use DO just now because it’s a really useful testing mechanism for the rapid development lifecycle. The same could be said for any cloud provider.
I don’t quite understand your question…do you mean if you’re using the testnet tool?
I’m not sure what you mean when you’re referring to a “project” here either? If this is in relation to your project from the other thread, perhaps we should pick it up in there?
The genesis node may well run on a DO-hosted instance to begin with. There are many pragmatic reasons why this is A Good Thing.
The genesis node could run on an AWS node or YOUR hosting, if you could provide the bandwidth and reliability that DO or AWS offer.
We USE Digital Ocean, we are not dependent on them.
DO will NOT have “decision-making” powers. All DO can do is shut down that node if the bills are not paid. In which case another Elder is promoted. No big deal and its my understanding that the use of DO is most likely temporary Also it is likely that the oldest (eldest?) of Elders will at some time fairly soon into the life of the network be hosted on a non-DO instance due to natural churn.
Are one of you trying to use the testnet tool? Not exactly sure, but I’m happy to help you get something running if you need any.
There should be a new sn_cli and sn_api version 0.37.0 released tomorrow and the CLI test suite is passing with those using safe_network 0.32.0. Version 0.36.0 of sn_cli/sn_api has a problem with NRS in it, but it’s otherwise usable. Worth just waiting until my PRs are merged tomorrow though to fix NRS.
This may get long winded and need a thread all unto itself but lets hope not
My first roadblock is
Initializing the backend...
Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Error refreshing state: AccessDenied: Access Denied
status code: 403, request id: WCEKQVPSNBMAKE75, host id: MQPPMTwgpbKa5pl
