Document setup for local development environment

briangershon commented 2 years ago

Why?

If you're a developer that wants to be able to change any of the 3 major pieces, it took several hours to run through all the separate README's to get everything running together.

This is meant to help onboard people new to the project, particularly if they are new to Web3.

Details

This PR is to introduce a new FULL_LOCAL_SETUP.md file specifically for a developer that wants to setup all 3 pieces locally.
I also added new instructions for how to test everything, including MetaMask setup, minting a test genesis token on Rinkeby, and finding the contract for the Mumbai Testnet deploy.
Mention new setup file in the main README.

I make a couple of minor changes:

Standardized on one provider (infura.io) instead of both infura.io and alchemy.io
Add missing HTTP_PORT env variables to example env file
Add PROD and STAGING web servers to main README

Should we remove the separate READMEs?

No, I left in the 3 separate READMEs in case a developer only needs to get part of the setup running. For example, to make changes to the front-end, you could decide to use the hosted server and deployed contract instead of setting that up yourself.

vercel[bot] commented 2 years ago

@briangershon is attempting to deploy a commit to the Developerdao Team on Vercel.

A member of the Team first needs to authorize it.

rasmuscnielsen commented 2 years ago

LGTM. Will merge :-)

Developer-DAO / pixel-avatars