4 ms·
Put it in an AWS S3 bucket. use aws command line tools to sync to your local repo easy way: aws s3 copy index.html s3://<mybucketname.com> --profile <awskeys
by mellavora 6y ago
Put it in an AWS S3 bucket.
use aws command line tools to sync to your local repo
easy way:
aws s3 copy index.html s3://<mybucketname.com> --profile <awskeys for this client>
hard way:
cd <mywebsiteroot dir>
git pull ## if needed
<website builder> ## i.e. webpack, angular, whatever
aws s3 sync public_html s3://<mybucketname.com>/ --profile <awskeys for this client>
- yonixw 6y agoThe problem with beginners and S3, is that they can't handle the billing side. Both calculating (outbound? same region? edge location?) and monitoring if things go south. Beginners will prefer the site going down rather than paying extra.
- ghaff 6y agoYeah, I use S3 myself for a static website (as well as podcast hosting and misc other stuff). But the lack of hard cost circuit breakers make me hesitant to recommend AWS in general to beginners for casual storage and hosting.
- enumjorge 6y agoFor true beginners even the easy single command might not be easy. You need to be familiar with the command line, you need to install the aws tool and hope that you don’t run into issues (often times if you’re on Windows installing command line tools can involve extra hoops for example), you need to navigate the AWS dashboard and get familiar with their unintuitive terminology (to host a site you need an “s3 bucket”), then you also need to create a key for your client and learn what a key is. Individually those tasks are not that difficult, but when you’re a beginner it adds up and quickly becomes intimidating.