status-im/dreddit-dapp
2
0
Fork 0
mirror of https://github.com/status-im/dreddit-dapp.git synced 2025-02-23 19:58:30 +00:00
Code Issues Projects Releases Wiki Activity

Minor grammar updates to 7: Deploy

Browse Source 
Just a few small changes for better readability.
This commit is contained in:
Andy Tudhope 2018-08-25 11:24:35 +02:00 committed by GitHub
parent 0d78c99dc3
commit ed34376ae1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
instructions/7 Testnet Deployment.md
View File

@ -1,5 +1,5 @@
## Testnet Deployment ## Testnet Deployment
Now that we finished building our dApp, we need to deploy it. We'll perform this activity deploying our contracts to the ropsten testnet, and our dApp resources to IPFS using Embark's upload feature. Now that we finished building our dApp, we need to deploy it. We'll deploy our contracts to the ropsten testnet, and our dApp resources to IPFS using Embark's upload feature.
### Configuring our deployment ethereum account ### Configuring our deployment ethereum account
Let's edit`./config/contracts.js` to add a testnet section that will contain our contract deployment settings. Embark supports different types of configurations for [deployment](https://embark.status.im/docs/contracts.html#Deployer-Account) of smart contracts. For this particular tutorial, we will use a private key that contains Ropsten ETH: Let's edit`./config/contracts.js` to add a testnet section that will contain our contract deployment settings. Embark supports different types of configurations for [deployment](https://embark.status.im/docs/contracts.html#Deployer-Account) of smart contracts. For this particular tutorial, we will use a private key that contains Ropsten ETH:
@ -11,10 +11,10 @@ Let's edit`./config/contracts.js` to add a testnet section that will contain our
}] }]
} }
``` ```
> Notice that on dappConnection we only specified $WEB3. This is because we will use a web3 provider that is automatically injected by Status / Metamask / Mist. However, this might change in the future with [EIP-1102](https://eips.ethereum.org/EIPS/eip-1102) > Notice that on `dappConnection` we only specified `$WEB3`. This is because we will use the web3 provider that is automatically injected by Status / Metamask / Mist. However, this might change in the future with [EIP-1102](https://eips.ethereum.org/EIPS/eip-1102)
### Storage ### Storage
For storage, we will use [Infura](https://infura.io) IPFS Gateway to upload our dApp files. This is configured on `./config/storage.js`. In this config file, we need to add a `testnet` section and configure both the `upload`, and `dappConnection` for handling the file uploads during the dApp runtime. For storage, we will use the [Infura](https://infura.io) IPFS Gateway to upload our dApp files. This is configured in `./config/storage.js`. In this config file, we need to add a `testnet` section and configure both the `upload`, and `dappConnection` for handling the file uploads during the dApp runtime.
``` ```
testnet: { testnet: {
@ -36,8 +36,8 @@ For storage, we will use [Infura](https://infura.io) IPFS Gateway to upload our
``` ```
### 3... 2... 1... Deploy! ### 3... 2... 1... Deploy!
Once you've done all the configuration, we'll proceed to execute `embark blockchain testnet` in a terminal session and `embark upload testnet` in other. Embark will proceed to compile our contracts, deploy them and upload the files to our dApp Once you've done all the configuration, we'll proceed to execute `embark blockchain testnet` in one terminal session and `embark upload testnet` in a separate one. Embark will proceed to compile our contracts, deploy them, and prepare the files for our dApp.
> Notice we are running `embark blockchain testnet` in a separate session in order to be able to see the sync state of our geth light node. The first time this is executed, geth will download a number of headers of the mined blocks, so the initial deployment of our contracts might take longer than usual. After our node synchronizes, our deployments will be faster. > Notice we are running `embark blockchain testnet` in a separate session in order to be able to see the sync state of our geth light node. The first time this is executed, geth will download a number of headers of the mined blocks, so the initial deployment of our contracts might take longer than usual. After our node synchronizes, our deployments will be faster.
Once the upload process concludes, execute `ipfs daemon` to share the dApp files with the IPFS network, and you would be able to access your dApp in the browser using the URL shown by Embark's upload process. You can access now your dApp via Status, or a Browser using Metamask. Once the upload process concludes, execute `ipfs daemon` to share the dApp files with the IPFS network, and you would be able to access your dApp in the browser using the URL shown by Embark's upload process. You can access now your dApp via Status, or a Browser using Metamask.