dagger-for-github
actions-gh-pages
dagger-for-github | actions-gh-pages | |
---|---|---|
2 | 14 | |
93 | 4,436 | |
- | - | |
0.0 | 8.6 | |
10 months ago | 26 days 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.
dagger-for-github
-
Use Docker to build better CI/CD pipelines with Dagger
The Dockerized design also allows pipelines made with Dagger devkit to be run in every CI/CD runtime environment like, for example, Github Action (using the official Dagger Github Action from the marketplace). Furthermore, it can also be run independently of the architecture of the platform. The only requirement is the Docker ecosystem support. So it can be run on a managed runner (eg. Github Runners), a self-hosted runner, a local machine, a serverless compute instance, etc.
-
Dagger: a new way to build CI/CD pipelines
Fun dact, Crazy Max is the author of the Github Action for Dagger :) https://github.com/dagger/dagger-for-github
actions-gh-pages
-
Where can I host a basic HTML page? Free.
Check out the GitHub action you can use for deploying to GitHub pages: https://github.com/peaceiris/actions-gh-pages.
-
Share rust docs
In addition to just sharing the .html generated files which would likely be cumbersome, you can host the docs on github pages and use something like https://github.com/peaceiris/actions-gh-pages + github actions to upload the documentation from your private repository to a public repo (required for non paid users).
-
The strongest principle of the blog's growth lies in the human choice to deploy it
I started by using runs-on: ubuntu-22.04 in this workflow to check if everything works ok. It run without any issues. After that I created PRs to add support for ubuntu-22.04 and ubuntu-latest version to GitHub Actions for Hugo and GitHub Pages Action
-
PSA: If you're using gh-pages to host your CI-generated documentation, make sure you don't store any history for that branch
As a first-step measure, we changed the CI script to overwrite the gh-pages branch at every run, rather than just appending a new commit. We use this gh-pages action, so it was just a matter of adding a force_orphan: true parameter.
-
How I created my Portfolio website using Hugo and GitHub pages?
Interesting to note that GitHub stores this workflow in the "main" branch under .github/workflows folder. For more details on this Action please refer the documentation and code at https://github.com/peaceiris/actions-gh-pages.
-
Preview Pull Requests and Automated CI/CD
My first workflow is to build and deploy or preview Client, It runs whenever a push or pull request creates for main branch containing changes to the code of client. It install dependencies and builds vue.js app. After build I use peaceiris/actions-gh-pages to deploy it to Github Pages. If the event is Pull Request then deploy to a sub-directory named preview and commit hash and leave a comment on PR.
-
GitHub Actions Reporting My ❤️ Music
If the data fetch from previous step succeeds, the workflow continues by building the static website with Hugo. Hugo is setup using action peaceiris/actions-hugo. When the files are ready, the result is published to GitHub pages, using another GitHub action, peaceiris/actions-gh-pages.
-
Generate PDF handbook with Docusaurus using GitHub Actions
peaceiris/actions-gh-pages@v3 - deploys any folder(s) to gh-pages, can use it for multiple static endpoints
-
Deploy Hugo website using Github pages
For more information about the actions used and their options, please see Hugo and Github pages on Github.
-
Automating the building and deployment of GitHub Pages
This quote is quite true. Without automation, we would spend a lot of out time on things that would have to be done repetitively, for example, manually building and deploying your GitHub pages every time there is a change. Luckily, you can easily use GitHub Actions to build and deploy your pages by just pushing your repository to GitHub! You don't even need to do anything except to add a configuration file to your repository. In this post, I will be creating a workflow and using peaceiris/actions-gh-pages@v3 from GitHub Marketplace (it's free).
What are some alternatives?
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
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.
pipeline - A cloud-native Pipeline resource.
trailing-slash-guide - Understand and fix your static website trailing slash issues!
Dagger.jl - A framework for out-of-core and parallel execution
tauri-action - Build your Web application as a Tauri binary for macOS, Linux and Windows
dagster - An orchestration platform for the development, production, and observation of data assets.
actions-mdbook - GitHub Actions for mdBook (rust-lang/mdBook) ⚡️ Setup mdBook quickly and build your site fast. Linux (Ubuntu), macOS, and Windows are supported.
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
actions-hugo - GitHub Actions for Hugo ⚡️ Setup Hugo quickly and build your site fast. Hugo extended, Hugo Modules, Linux (Ubuntu), macOS, and Windows are supported.
cloak - Secrets automation for developers
mdbook-admonish - A preprocessor for mdbook to add Material Design admonishments.