amplify-preview-actions VS s3-sync-action

Compare amplify-preview-actions vs s3-sync-action and see what are their differences.

amplify-preview-actions

This action deploys your AWS Amplify pull request preview for your public repository (by yinlinchen)

s3-sync-action

πŸ”„ GitHub Action to sync a directory with a remote S3 bucket 🧺 (by jakejarvis)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
amplify-preview-actions s3-sync-action
1 7
14 1,003
- -
0.6 0.0
7 days ago about 1 month ago
Shell Shell
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

amplify-preview-actions

Posts with mentions or reviews of amplify-preview-actions. We have used some of these posts to build our list of alternatives and similar projects.

s3-sync-action

Posts with mentions or reviews of s3-sync-action. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-20.
  • Bringing together Hungarian technology conferences
    2 projects | dev.to | 20 Mar 2023
    I cannot ignore the fact that I am an AWS Community Builder, so it was a no-brainer that I would implement this on AWS. Registering a domain and setting it up on Route 53 was the first step. Then I looked at the possibilities of hosting. The site is written in Jeklly and each page is generated separately. Using GitHub Actions, I can regenerate the static pages every time there is a new commit. Hosting a static website on AWS isn’t rocket science. S3 static file hosting is a cheap and easy way. I just needed to find a way how to publish my files to S3. Jake Jarvis created a GitHub Action that can sync your files to S3. All you have to do is to create the appropriate IAM permissions and your files will be pushed to the S3 bucket of your choice. From there, AWS will do the rest. I have created a CloudFront distribution to get HTTPS and fast access from Hungary. Currently there is no AWS region in Hungary, but there is an edge location in Budapest, so serving the site from there gives fast access to Hungarian users. πŸ”₯πŸ”₯πŸ”₯
  • Cheap way to host a Javascript project. (e.g. Node APIs & React Apps)
    1 project | dev.to | 25 Feb 2023
  • request critical feedback on the yaml for my first github action, please
    2 projects | /r/github | 16 Dec 2022
    I mean.. I would probably just have used https://github.com/marketplace/actions/s3-sync :)
  • Nestjs + Nextjs Monorepo with AWS
    2 projects | /r/node | 29 Jan 2022
    I would consider sending the UI build files to S3 using either cloud formation or Github Actions. For the backend, sounds like a docker container could serve you well and cloudformation or Github Actions can handle this.
  • CI/CD failing for permission... anybody can help me?
    1 project | /r/aws | 21 Nov 2021
    The action in GitHub is the following (as per instructions here : https://github.com/jakejarvis/s3-sync-action )
  • How do you implement your Front-end build & deploy process?
    2 projects | /r/Nestjs_framework | 4 Mar 2021
    You can deploy your frontend build to S3, then point your domain to these files, for example with CloudFlare or Route53. We use a Github action to publish these for each deploy. This makes the frontend and backend effectively two different services.
  • 15. CI/CD (Front end)
    2 projects | dev.to | 12 Jan 2021
    Git hub actions pushes the source code to my S3 bucket the moment they are pushed to my git repository using a git actions. Git action: https://github.com/jakejarvis/s3-sync-action

What are some alternatives?

When comparing amplify-preview-actions and s3-sync-action you can also consider the following projects:

gh-action-pypi-publish - The blessed :octocat: GitHub Action, for publishing your :package: distribution files to PyPI: https://github.com/marketplace/actions/pypi-publish

git-repo-sync - Git Repo Sync enables you to synchronize code to other code management platforms, such as GitLab, Gitee, etc.

github-slug-action - GitHub Action to expose slug value of GitHub environment variables inside your GitHub workflow

build-hugo - A GitHub Action to build Hugo site.

latex-action - :octocat: GitHub Action to compile LaTeX documents

git-repo-sync - Auto synchronization of remote Git repositories. Auto conflict solving. Network fail resilience. Linux & Windows support. And more.

git-auto-commit-action - Automatically commit and push changed files back to GitHub with this GitHub Action for the 80% use case.

terraform-multienv - A template for maintaining a multiple environments infrastructure with Terraform. This template includes a CI/CD process, that applies the infrastructure in an AWS account.

build-arch-package - Build an Arch Linux package

terraform-security-scan - Run a security scan on your terraform with the very nice https://github.com/aquasecurity/tfsec

OpenWrt-Rpi - Raspberry Pi & NanoPi R2S/R4S & G-Dock & x86 OpenWrt Compile Project. (Based on Github Action / Daily Update)

jekyll-action - A GitHub Action to publish Jekyll based content as a GitHub Pages site