Environment Setup
Step-by-Step Hedera Environment Setup Guide
Last updated
Was this helpful?
Step-by-Step Hedera Environment Setup Guide
Last updated
Was this helpful?
This environment setup guide outlines the steps needed to get your development environment ready for building applications on the Hedera network.
By the end of this guide, you will be able to:
Set up a project and install dependencies.
Create and configure a .env
file to store environment variables.
Before you begin, you should have completed the following guide:
To skip the setup steps and quickly get started, open the project repository in your language of choice and click the Open in Gitpod button. This will launch a Gitpod workspace/environment that automatically installs all the dependencies.
Clone the project repository in your language of choice. git clone
the repo and cd
into the project's root directory.
Install all dependencies:
Open your project directory in your code editor or IDE. This is what it should look like.
.env
FileWhen setting up your project, you must create a .env
file to store your environment variables. To make this process easier, run the script below. It will interactively prompt you for input and automatically populate the required values in the file based on your responses.
In your project root directory, run:
After the last prompt, you should see a new .env
file in your project root directory. Check that each of the environment variables has a value.
Storing private keys in a .env
file is not considered best practice. There is always a risk of accidentally committing and pushing to a public GitHub repo and exposing your keys. Make it a habit to add .env
to your .gitignore
file as a precautionary measure.
We highly advise against using a private key with mainnet funds.
Your progress will captured as metrics and published to the Hedera network for you to share with others! If you would like to disable publishing the metrics to the public ledger and viewable in a network explorer, please change metricsHcsDisabled
value to true
in the logger.json
file located in the root directory. The metrics are enabled by default with the value false
.
Example logger.json
file:
Congratulations, you have completed the Environment Setup guide in the Getting Started series!
You have learned how to:
Now that your environment is set up, you can start building on the Hedera Testnet! Based on your experience level and development needs, choose one of the following paths that best describes you:
Follow the prompts in the Gitpod console to configure your .env
file. Refer to the expandable in for guidance on completing your .env file setup.
Refer to for guidance on managing metrics. Learn how to disable them in Gitpod if you prefer not to store your progress metrics .
Once everything is set up, head to the section to choose your learning path and start building.
Enter a seed phrase
List of public endpoints .
This is the () from the testnet account created on the Hedera Portal or HashPack wallet.
If you used the Hedera to create a testnet account, this would be its corresponding private key.
Have questions? Join the and post them in the channel or ask on .
Web2 Developers
Choose this path if you're a web2 developer or a student new to web3 and Hedera. Learn to build on Hedera using SDKs in Java, JavaScript, or Go. Start with transferring HBAR, creating tokens, and managing topics.
EVM Developers
Choose this path if you have experience deploying Solidity contracts on Ethereum and other EVM networks. Learn to write, compile, deploy, and verify smart contracts using familiar EVM-compatible tools.
➡
➡