deploy static site demo on AWS

[robroyhobbs]

@NateRobinson

How does this work for AWS? how to push into an aws instance of the node? I'm sure this is all obvious to you all.

https://docs.arcblock.io/en/abtnode/developer/static-blocklets

I went through the steps of creating the static site blocklet but it is unclear to me on how I upload into my AWS node since I am not using cli? I'm sure its obvious but I am not clear. Also, compared to other static site systems maybe we can borrow a few ideas.

A few ideas:

1. gitpod integration for docs/sites
2. a GUI based implementation / app like github pages/netlify to connect and import/add inside of a docs blocklet so I can just edit/add inside of the blocklet? I really want the zero to hero in 3 steps that netlify says on their new site page deployment process.
3. if we have some type of cloud cli integrated we could interact with the docs blocklet and could just do something like hugo with its quick start process inside of the blocklet I guess.

For me, two steps - first is how to seamlessly add the docs/sites/content into the node, and then how to interact with it and whether we enable that type of functionality in the node itself.

I do think its important to have a ready page to edit if a user doesn't add their own and also some themes similar to some of the original theming we did with xmark.

thoughts?

and then a second blocklet for blogs and others like forestry ;) https://forestry.io/starters/

[robroyhobbs]

adding notes
Our doc about deploy is out of date, currently we have supported remote deploy https://docs.arcblock.io/en/abtnode/developer/abtnode-cli#8-deploy-options-folder

6:54
The remote deploy command like this:
6:54
an deploy . --endpoint --access-key --access-secret

@wangshijun @polunzh for end-user node where only 443 and 80 are open does this process work? I also imagine something much simpler than this process for the less sophisticated users. Compared to netlify/github pages, jekyl, etc ours is a bit complicated and honestly not something I would likely use.

[wangshijun]

@NateRobinson @robroyhobbs For the doc editing and preview issue, facts are:

• We have enabled auto build and deployment of the doc site
• We do not have live edit and preview support in ABT Node or elsewhere. you do not need to deploy to production node for preview purpose right?

So, I suggest we stick with the gitpod support for live edit and preview, once your code changes pushed and merged, those changes will be deployed to production automatically.

[wangshijun]

@NateRobinson 关于 gitpod 的 support，你可以给我们几个主要的 doc 仓库添加下支持

[robroyhobbs]

@wangshijun note, this is just me attemping to create a static site and is unrelated to our own abtnode docs. for example, similar to using s3, netlify or others to create and host a new static site.

as an AWS user, I don't have access to the deploy command since everything is being done through GUI, additionally, how can users create a blocklet for their docs, upload them and host them to end users? I just used the static site instructions since that is what we have.

[robroyhobbs]

another user example and I prefer they just use ours instead of aws. :)

we’ve just been uploading manually via GUI. However when we need to operational use that I expect we will integrate with it properly via aws APIs.