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

document first-time setup #2410

Closed
bard opened this issue Oct 2, 2023 · 3 comments
Closed

document first-time setup #2410

bard opened this issue Oct 2, 2023 · 3 comments
Labels

Comments

@bard
Copy link
Contributor

bard commented Oct 2, 2023

Overview

It is currently not straightforward for external contributors to clone the repository and launch the application(s). This is mostly due to the applications depending on API keys which, however free, are tied to invididual developers' accounts, and thus cannot be provided as part of the repository and need to be requested by developers from third-party services.

Details

There should be a section in the README or a separate document listing these required API keys and, at minimum, linking to pages where the developer can get them from, e.g.:

  • REACT_APP_ALCHEMY_ID= - sign up to the free plan on alchemy.com and request an API key
  • REACT_APP_INFURA_ID= - sign up to the free plan on infura.io and request an API key
    ...

Challenges and unknowns

It is not clear whether certain keys can at all be available to external contributors, e.g. REACT_APP_SUBGRAPH_ARBITRUM_API. If not, this might be a blocker for external contributions.

@bard bard added the chore label Oct 2, 2023
@bard bard added this to Grants Lab Oct 2, 2023
@bard bard moved this to Backlog in Grants Lab Oct 2, 2023
@ArslanYM
Copy link
Contributor

Overview

It is currently not straightforward for external contributors to clone the repository and launch the application(s). This is mostly due to the applications depending on API keys which, however free, are tied to invididual developers' accounts, and thus cannot be provided as part of the repository and need to be requested by developers from third-party services.

Details

There should be a section in the README or a separate document listing these required API keys and, at minimum, linking to pages where the developer can get them from, e.g.:

  • REACT_APP_ALCHEMY_ID= - sign up to the free plan on alchemy.com and request an API key
  • REACT_APP_INFURA_ID= - sign up to the free plan on infura.io and request an API key
    ...

Challenges and unknowns

It is not clear whether certain keys can at all be available to external contributors, e.g. REACT_APP_SUBGRAPH_ARBITRUM_API. If not, this might be a blocker for external contributions.

This issue was solved after (#2443) , If there is still a need for a proper first time setup guide, Can I work on a video tutorial or blog that documents the whole process of running the project locally?

@bard
Copy link
Contributor Author

bard commented Oct 24, 2023

This issue was solved after (#2443) , If there is still a need for a proper first time setup guide, Can I work on a video tutorial or blog that documents the whole process of running the project locally?

There is a DEV.md document that was also recently updated, could you have a look at it and see if it's missing something, based on your direct experience of getting the project running?

You're welcome to also blog about it of course. :) I'd advise against videos because setup processes can change, and when they do, it's easy to update a written tutorial than a recorded one.

@bard bard closed this as completed Oct 24, 2023
@github-project-automation github-project-automation bot moved this from Backlog to Live in Grants Lab Oct 24, 2023
@ArslanYM
Copy link
Contributor

This issue was solved after (#2443) , If there is still a need for a proper first time setup guide, Can I work on a video tutorial or blog that documents the whole process of running the project locally?

There is a DEV.md document that was also recently updated, could you have a look at it and see if it's missing something, based on your direct experience of getting the project running?

You're welcome to also blog about it of course. :) I'd advise against videos because setup processes can change, and when they do, it's easy to update a written tutorial than a recorded one.

Cool, I will create a blog for first-time-contributors to setup the project locally. The DEV.md is perfectly fine as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Live
Development

No branches or pull requests

2 participants