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

fix(readme): Enhance readme #113

Merged
merged 27 commits into from
Oct 23, 2023
Merged

fix(readme): Enhance readme #113

merged 27 commits into from
Oct 23, 2023

Conversation

InversionSpaces
Copy link
Contributor

@InversionSpaces InversionSpaces commented Oct 12, 2023

  • Separate command from outputs so it is easy to copy commands
  • Update deployment guide
  • Add warning about previous deployment info removal

@InversionSpaces InversionSpaces marked this pull request as ready for review October 12, 2023 15:27
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:

Copy link
Collaborator

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.

Copy link
Contributor Author

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?

Copy link
Contributor Author

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?

Copy link
Contributor Author

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

Copy link
Collaborator

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.

Copy link
Collaborator

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:
Copy link
Collaborator

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.

README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
![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)
Copy link
Collaborator

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.


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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this isn't resolving right:
image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do you view this? I use "show rich diff" on this PR in github UI and I get:
image
Github has its own markdown flavour

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved

## 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).
Copy link
Collaborator

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?

Copy link
Collaborator

@boneyard93501 boneyard93501 Oct 16, 2023

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.

README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@boneyard93501
Copy link
Collaborator

the yaml file overview content is pretty much all outdated, e.g., fluence.yaml section. @InversionSpaces do you want to keep that section?

InversionSpaces and others added 4 commits October 16, 2023 10:24
@InversionSpaces
Copy link
Contributor Author

I believe screenshot of metamask should be updated as it shows aurora testsnet, but we use mumbai testnet?

@InversionSpaces InversionSpaces requested a review from meph October 16, 2023 15:26
@boneyard93501
Copy link
Collaborator

awesome. thank you.

@InversionSpaces
Copy link
Contributor Author

Okay, fluence deal logs does not work still.
Created a task to add it later: DXJ-512
Will merge now

@InversionSpaces InversionSpaces merged commit bf49ebf into main Oct 23, 2023
3 checks passed
@InversionSpaces InversionSpaces deleted the fix/readme branch October 23, 2023 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants