search

kauri-io / Content

A peer reviewed repository of content for kauri.io
12 stars 22 forks source link

Deploying Full stack Dapp to AWS #51

Closed ChrisChinchilla closed 5 years ago

ChrisChinchilla commented 5 years ago

We have an existing tutorial collection that takes new web3 developers from beginning steps to a functioning full stack web3 dapp.

https://kauri.io/collection/5b8e401ee727370001c942e3

We want to add a new tutorial to this collection to show the steps to deploy application side of the dapp to AWS. In this particular case, also show the reader how to deploy their smart contract to running on an AWS managed blockchain instance.

Ideally the deployment process is maintainable as code changes, the app should also update.

The article should follow on from earlier parts of the series, use simple technical english and as little passive voice as possible. If you make a PR to this repo it offers advice on your text via a CI process.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.9 ETH (285.2 USD @ $316.88/ETH) attached to it as part of the kauri-io fund.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Workers have applied to start work.

These users each claimed they can complete the work by 12 months from now. Please review their action plans below:

1) mul1sh has applied to start work _(Funders only: approve worker | reject worker)_.

I will develop a full stack dApp as per the tutorial and deploy it to aws whilst documenting every step of the way and then finally do a PR with all the steps needed to be taken to deploy the dApp.

Should tae me no more than 4 days to finish this.

Learn more on the Gitcoin Issue Details page.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Workers have applied to start work.

These users each claimed they can complete the work by 12 months from now. Please review their action plans below:

1) mul1sh has applied to start work _(Funders only: approve worker | reject worker)_.

I will develop a full stack dApp as per the tutorial and deploy it to aws whilst documenting every step of the way and then finally do a PR with all the steps needed to be taken to deploy the dApp.

Should tae me no more than 4 days to finish this. 2) sanchaymittal has applied to start work _(Funders only: approve worker | reject worker)_.

Almost Done, I need your permission to share it with you.

Learn more on the Gitcoin Issue Details page.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Workers have applied to start work.

These users each claimed they can complete the work by 12 months from now. Please review their action plans below:

1) mul1sh has applied to start work _(Funders only: approve worker | reject worker)_.

I will develop a full stack dApp as per the tutorial and deploy it to aws whilst documenting every step of the way and then finally do a PR with all the steps needed to be taken to deploy the dApp.

Should tae me no more than 4 days to finish this. 2) sanchaymittal has applied to start work _(Funders only: approve worker | reject worker)_.

Almost Done, I need your permission to share it with you. 3) abhimanyu121 has applied to start work _(Funders only: approve worker | reject worker)_.

Initial plan will be to make a simple dapp and host it on aws along with writing steps to do so along with the screenshots and screen records wherever necessary. After the initial work smart contract would be deployed on instance of blockchain on aws from same dapp. 4) man-jain has applied to start work _(Funders only: approve worker | reject worker)_.

I have a good experience with cloud platforms like heroku, aws, gcloud etc. So, I will create a step by step process with good images which can help the user in every step.

Learn more on the Gitcoin Issue Details page.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 9 months, 2 weeks from now. Please review their action plans below:

1) abhimanyu121 has applied to start work _(Funders only: approve worker | reject worker)_.

Initial plan will be to make a simple dapp and host it on aws along with writing steps to do so along with the screenshots and screen records wherever necessary. After the initial work smart contract would be deployed on instance of blockchain on aws from same dapp. 2) mul1sh has been approved to start work.

I've already submitted the PR :)

Learn more on the Gitcoin Issue Details page.

ChrisChinchilla commented 5 years ago

Sorry, everyone, I was on holiday for 2 weeks! @mul1sh if you are still interested, then I'd love to have you on-board, please re-apply. Note that this is a follow up post to the existing collection (https://kauri.io/collection/5b8e401ee727370001c942e3), as stated in the description.

gitcoinbot commented 5 years ago

@mul1sh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 5 years ago

@mul1sh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 5 years ago

@mul1sh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 5 years ago

@mul1sh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

mul1sh commented 5 years ago

@ChrisChinchilla nearly done with this, just a final question, should I explain how to deploy/create an aws blockchain instance as well as explaining how to deploy a fullstack dApp in the running blockchain instance?

ChrisChinchilla commented 5 years ago

Yeah sorry @mul1sh I've mentioned that enthusiastic bot to the team a few times 😆 .

I feel like getting an instance running is a pretty essential part of the process if AWS doesn't make it too complex, which they often do :/

gitcoinbot commented 5 years ago

@mul1sh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

mul1sh commented 5 years ago

@ChrisChinchilla true 😅.

Also actually come to think of it, I don't think it's possible to deploy an ethereum app to an AWS managed blockchain instance because they have not released the ethereum service yet. Currently they only support IBM's hyperledger fabric.

Just realised this now which means what I've been documenting I.e. deploying a dApp to an EC2 instance running as a mainnet node using AWS blockchain templates, is wrong!!

And so with this in mind I don't think this bounty can be completed at this point in time at-least not until aws finally releases the managed blockchain instance service for ethereum😥

EDIT

I'll stop working on this issue for now because it can't be resolved till aws releases managed blockchain instances for ethereum. But once they do and this issue is still open, I'll gladly jump on it again 😄

ChrisChinchilla commented 5 years ago

So… @mul1sh

We've decided to keep this going with a different approach, let me know if you're still keen.

Front end - deploy to EC2 / S3 / Lamda (whatever you prefer) Ethereum instance - use Kaleido and update Truffle config to use it.

If you're not I'll put the bounty up for grabs again.

mul1sh commented 5 years ago

@ChrisChinchilla sounds great to me, let me continue working on it then, thanks for alerting me 😃

ChrisChinchilla commented 5 years ago

Excellent :)

pbteja1998 commented 5 years ago

@ChrisChinchilla is this bounty available? I like to work on this if it is available. Thanks.

gitcoinbot commented 5 years ago

⚡️ A tip worth 0.90000 ETH (163.59 USD @ $181.77/ETH) has been granted to @mul1sh for this issue from @ChrisChinchilla. ⚡️

Nice work @mul1sh! Your tip has automatically been deposited in the ETH address we have on file.

gitcoinbot commented 5 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This Bounty has been completed.

Additional Tips for this Bounty: