Nice tutorial, thanks. Bears mentioning that when the css and js file names are changed with every build to refresh cash so simply syncing your new build folder each time will clutter the bucket with files from previous builds. Might want to clear the static folder before syncing.
Yes good point, you also want to specify --delete on the command to clear up files that aren't in the source folder. Don't forget unless you cache in GitHub Actions there won't be any previous build files.
Yes you can but you would have to set up a separate to push to a different S3 bucket. You can do conditional steps that only run when the branch is tagged for example.
I like it your video. You explained very good. I've got a question, ¿Can I programm for differents enviroments?, For example, from dev to qa, from qa to staging, from staging to prod.
Yes you can set conditional environment variables in GitHub Actions but it is more fiddly than it should be. I have not tried it myself but there is a good post here on it: hungvu.tech/advanced-github-actions-conditional-workflow#heading-creating-an-action-3-times-for-3-branches-results-in-duplicated-code-should-there-be-a-way-to-refactor You would also need at least to have separate S3 buckets as the names need to be globally unique even if in separate AWS accounts.
Thanks my friend, helped me to build my own version.
That's helpful 😊 thank you
ever clear solution. the best
Thank you 🙏 I am glad you liked it.
Awesome, thank you.
Nice tutorial, thanks. Bears mentioning that when the css and js file names are changed with every build to refresh cash so simply syncing your new build folder each time will clutter the bucket with files from previous builds. Might want to clear the static folder before syncing.
Yes good point, you also want to specify --delete on the command to clear up files that aren't in the source folder. Don't forget unless you cache in GitHub Actions there won't be any previous build files.
Very helpful. Thank You
Glad it was helpful!
Hi...can we do this for multiple environments like staging,prod?
Yes you can but you would have to set up a separate to push to a different S3 bucket. You can do conditional steps that only run when the branch is tagged for example.
I like it your video. You explained very good. I've got a question, ¿Can I programm for differents enviroments?, For example, from dev to qa, from qa to staging, from staging to prod.
Yes you can set conditional environment variables in GitHub Actions but it is more fiddly than it should be. I have not tried it myself but there is a good post here on it:
hungvu.tech/advanced-github-actions-conditional-workflow#heading-creating-an-action-3-times-for-3-branches-results-in-duplicated-code-should-there-be-a-way-to-refactor
You would also need at least to have separate S3 buckets as the names need to be globally unique even if in separate AWS accounts.
@@alexhyettdev Thanks so much!!