wait-for-secrets
FTP-Deploy-Action
| wait-for-secrets | FTP-Deploy-Action | |
|---|---|---|
| 4 | 4 | |
| 273 | 3,421 | |
| 2.2% | - | |
| 0.0 | 2.8 | |
| 10 months ago | 2 months ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | MIT License |
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.
wait-for-secrets
-
How to publish on npm with `--provenance` using Lerna-Lite
To deal with the OTP (or any other 2FA), we can use wait-for-secrets. Compared to the previous basic usage, we are splitting the Lerna-Lite Version & Publish into 2 separate tasks. The reason is simple, calling the OTP too early would timeout even before reaching the publish phase, so calling the OTP just before the publish is the best way to avoid invalid pin.
-
Rotate any secrets stored in CircleCI
While OIDC is a good option, at StepSecurity, we are building an open-source project that allows using your MFA tokens for deployments in CI/ CD. So far, it is implemented for GitHub Actions - https://github.com/step-security/wait-for-secrets. In this method, you get a link in the build log, click the link, and can enter credentials at run time, which then gets used in the next step in the pipeline for deployment. So there are no persistent secrets stored in the CI/ CD pipeline and no need for managing/ rotating separate deployment credentials.
- A way to publish from GitHub Actions using multi-factor authentication
- Show HN: Publish from GitHub Actions using multi-factor authentication
FTP-Deploy-Action
-
Setting up GitHub Actions to deploy your website via FTP
As GitHub Actions is a community-driven platform, we can utilize various open-source workflows available. In this case, we will use the popular "FTP-Deploy" Actions workflow developed by Sam Kirkland. In the main.yml file, include the following code:
- Automatically deploy your website code every commit
-
Continuous Deployment on Shared Hosting with GitHub Actions
This is where the files are now transferred to the shared hosting server. Get your FTP details from your shared hosting. Then go to your repo>settings>secrets then add the three secrets namely: server, username and then password. This action is courtesy of SamKirkland.
-
Revitalizing my Blog with Hugo and GitHub Actions (aka a New Hope)
SamKirkland/FTP-Deploy-Action
What are some alternatives?
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed
git-ftp - Uses Git to upload only changed files to FTP servers.
terraform-aws-oidc-github - Terraform module to configure GitHub Actions as an IAM OIDC identity provider in AWS.
checkout - Action for checking out a repo
circleci-audit
build-hugo - A GitHub Action to build Hugo site.
github-pages-deploy-action - 🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
dxcfg - Configuration as code for the masses
mc-publish - 🚀 Your one-stop GitHub Action for seamless Minecraft project publication across various platforms.
auto-approve-action - 👍 GitHub Action for automatically approving GitHub pull requests
wait-for-jobs - Wait for the specified jobs in the same run to be complete successfully before proceeding, helpful to prestart the job
pakman - 📦 Build project into Self contained package for deployment