-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix(readme): Enhance readme #113
Conversation
InversionSpaces
commented
Oct 12, 2023
•
edited
Loading
edited
- Separate command from outputs so it is easy to copy commands
- Update deployment guide
- Add warning about previous deployment info removal
5c0ed6e
to
66f71ee
Compare
66f71ee
to
b09fdb7
Compare
README.md
Outdated
@@ -58,7 +58,7 @@ If you don't have Fluence CLI installed, do: | |||
npm -g i @fluencelabs/cli@unstable | |||
``` | |||
|
|||
Before you proceed, you should have, say, three RPC endpoint urls, e.g., Infura, Alchemy and QuickNode, for the same EVM-based chain you are using in your dAPP. Update the `configs/quickstart_config.json` by providing your endpoint urls and ignore the rest of the parameters for now: | |||
Before you proceed, you should have, say, three RPC endpoint urls, e.g., Infura, Alchemy and QuickNode, for the same EVM-based chain you are using in your dAPP. Update the `configs/quickstart_config.json` by providing your endpoint urls and ignore the rest of the parameters for now: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before you proceed, you should have, say, three RPC endpoint urls, e.g., Infura, Alchemy and QuickNode, for the same EVM-based chain you are using in your dAPP. Update the `configs/quickstart_config.json` by providing your endpoint urls and ignore the rest of the parameters for now: | |
Before you proceed, you should have, say, three RPC endpoint urls, e.g., Infura, Alchemy and Ankr, for the same EVM-based chain you are using in your dAPP. Update the `configs/quickstart_config.json` by providing your endpoint urls and ignore the rest of the parameters for now: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the method selection should be addressed. currently, round-robin is suggested but it could be quorum, which requires specifying the quorumNumber.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why substitute QuickNode with Ankr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other algorithms are described later in the doc
Quickstart is about getting default thing working as fast as possible
Should we describe other algorithms right here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also quorum does not require quorumNumber
, it has a default of 2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why substitute QuickNode with Ankr?
they made the use of a free account very difficult with a lot of limitations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other algorithms are described later in the doc Quickstart is about getting default thing working as fast as possible Should we describe other algorithms right here?
up to you. i actually think the entire document should be redone and all your work is getting us there. so much appreciated. re algo descritions, yes, that could work. want to give it a try?
README.md
Outdated
@@ -58,7 +58,7 @@ If you don't have Fluence CLI installed, do: | |||
npm -g i @fluencelabs/cli@unstable | |||
``` | |||
|
|||
Before you proceed, you should have, say, three RPC endpoint urls, e.g., Infura, Alchemy and QuickNode, for the same EVM-based chain you are using in your dAPP. Update the `configs/quickstart_config.json` by providing your endpoint urls and ignore the rest of the parameters for now: | |||
Before you proceed, you should have, say, three RPC endpoint urls, e.g., Infura, Alchemy and QuickNode, for the same EVM-based chain you are using in your dAPP. Update the `configs/quickstart_config.json` by providing your endpoint urls and ignore the rest of the parameters for now: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the method selection should be addressed. currently, round-robin is suggested but it could be quorum, which requires specifying the quorumNumber.
![Sign TX](./images/sign_tx_metamask.png) | ||
* once you signed the transaction and the contract was successfully updated, we are done! (6) | ||
* once you sign transactions, the deal is created and the workers join the deal, deploying your services (5) | ||
* finally, deployment information is saved for future use in Aqua scripts (6) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be a good time to demonstrate the fluence workers log
command and output.
Co-authored-by: folex <0xdxdy@gmail.com>
|
||
To get rid of the demo project for now, use `fluence module remove` to unlink the module from the *fluence.yaml* and *service.yaml* files; the old *rm -r <path/demo>* gets rid of the code template. | ||
|
||
### Deploying A Service | ||
|
||
With a service, in this case the *eth-rpc* service, ready for deployment, we simply use the `fluence deal deploy` command: | ||
> :warning: **Warning**: For quickstart, services are already deployed for you. But if you want to deploy services in this repository yourself, you should remove old deployment information first: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
## Summary | ||
|
||
fRPC is a design pattern to efficiently mitigate risks inherent in centralized RPC providers for dApps using Fluence's decentralized serverless compute protocol. fRPC Substrate is a basic implementation of the fRPC design pattern that dApp users can use put of the box with no changes to their frontend. Moreover, Fluence is sponsoring hackathons, like EthDenver 2023, for developers to try the substrate and hack on and expand on the control algorithms provided to serve their needs and provide improvements to the community. | ||
fRPC is a design pattern to efficiently mitigate risks inherent in centralized RPC providers for dApps using Fluence's decentralized serverless compute protocol. fRPC Substrate is a basic implementation of the fRPC design pattern that dApp users can use out of the box with no changes to their frontend. Moreover, Fluence is sponsoring hackathons, like EthDenver 2023, for developers to try the substrate and hack on and expand on the control algorithms provided to serve their needs and provide improvements to the community. | ||
|
||
For support, to discuss your ideas or to schedule presentations of your solutions to the Fluence and fRPC community at large, reach out in [discord]("https://fluence.chat") or [telegram](https://t.me/fluence_project). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might as well delete that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we haven't formalized the design pattern, the hackathon references are outdated and the document needs to be reworked for future hackathons. so not much point confusing people with incomplete or outdated info.
but if you find that paragraph useful, just remove
Moreover, Fluence is sponsoring hackathons, like EthDenver 2023, for developers to try the substrate and hack on and expand on the control algorithms provided to serve their needs and provide improvements to the community.
for now.
the yaml file overview content is pretty much all outdated, e.g., fluence.yaml section. @InversionSpaces do you want to keep that section? |
Co-authored-by: boneyard93501 <4523011+boneyard93501@users.noreply.github.com>
Co-authored-by: boneyard93501 <4523011+boneyard93501@users.noreply.github.com>
Co-authored-by: boneyard93501 <4523011+boneyard93501@users.noreply.github.com>
Co-authored-by: boneyard93501 <4523011+boneyard93501@users.noreply.github.com>
I believe screenshot of metamask should be updated as it shows aurora testsnet, but we use mumbai testnet? |
f358c4c
to
7b37ab2
Compare
awesome. thank you. |
Okay, |