cloudwithchris.com
checkout
cloudwithchris.com | checkout | |
---|---|---|
10 | 62 | |
22 | 5,265 | |
- | 2.6% | |
6.9 | 7.6 | |
3 months ago | 3 days ago | |
JavaScript | TypeScript | |
MIT License | 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.
cloudwithchris.com
-
Shift Left and Increase your Code Quality with GitHub Branch Protection Rules
Navigate to a GitHub Repository that you own. For example, I am the organization owner of CloudWithChris, so will navigate to my cloudwithchris.com repository.
-
Choosing between Azure Static Web Apps and Static Websites on Azure Storage
For example, the website you're reading (Cloud With Chris) is - and has been - hosted using the Static Websites on Azure Storage approach since March 2020. As an end-user, when you navigate to www.cloudwithchris.com, you'll be routed to an Azure CDN instance that is fronting the Azure Storage Account which hosts the production Static Website. The CDN is how I'm able to have an SSL Certificate mapped against a Custom Domain, otherwise that wouldn't be possible directly on the storage account (as there's no way to map a custom SSL certificate in that way directly).
-
Introducing the Cloud Native Compute Foundation (CNCF)
So, what's the point in this post (other than reinforcing a brilliant episode, thank you again Annie)? Over time, I'll release a set of blog posts which cover these CNCF projects. I don't have a timeframe. I don't have a specific goal in mind just yet. But given that it's Cloud with Chris, it does feel that Cloud native should have a spot in there somewhere. So stay tuned! If you'd like me to focus on any projects in particular, please let me know either in the Cloud With Chris GitHub repository by raising a GitHub Issue, or letting me know on Twitter, @reddobowen.
-
Azure Static Web Apps are Generally Available
Now, one of the main points that I raise in my usual talk on hosting websites using the Static Content Hosting pattern is the significant cost-benefit of doing this. In an average month, I spend less than £5 for the entire end-to-end running of my environments. Yes, environments plural - that includes Preview, Staging and production, and also includes the cost of streaming my audio files to third party platforms like Apple Podcasts, Google Podcasts, Spotify and consumed directly from www.cloudwithchris.com.
-
Using schema.org for SEO optimisation
There are plenty of existing articles that talk about how to optimise these common SEO practices, so I recommend you search for these as I'm going to aim to not reinvent the wheel. If you're interested on how I achieve some of these in Cloud with Chris, you can take a look at the metadata partial template that I use within my Hugo template.
-
Using Git LFS to version Podcast Audio files and trigger releases to production with GitHub Actions
name: "Podcast Audio Upload" on: push: branches: - master paths: - "podcast_audio/**" jobs: publish: environment: name: production.azure url: https://www.cloudwithchris.com runs-on: ubuntu-latest steps: - name: Download Podcast files that are different from prior commit run: | git clone --config lfs.fetchexclude="/podcast_audio" https://github.com/chrisreddington/cloudwithchris.com.git ./ fileschanged=$(git diff --name-only HEAD^ HEAD -- '*.mp3') echo "$fileschanged" > files.txt xargs -a files.txt -d'\n' rm git config --unset lfs.fetchexclude git checkout . cd podcast_audio sed -i -e 's/podcast_audio\///g' ../files.txt for i in *; do if ! grep -qxFe "$i" ../files.txt then echo "Deleting: $i" rm "$i" fi done - name: Azure Login uses: azure/login@v1 with: creds: ${{ secrets.AZURE_CREDENTIALS }} - name: "Upload podcast files to storage that don't yet exist" uses: azure/CLI@v1 with: azcliversion: 2.20.0 inlineScript: | az storage blob upload-batch --account-name cloudwithchrisprod -d 'podcasts' -s '/github/workspace/podcast_audio' --if-unmodified-since 2020-01-01T00:00Z --auth-mode login
-
Using GPG Keys to sign Git Commits - Part 3
Once you have added the Public GPG Key details to GitHub, you can now go ahead and push your local changes to GitHub by using git push (If you haven't already associated a remote location with the Git repository, then you may also need to use the git remote add command, and then use git push). Assuming that the Public Key in the GPG Keys section of your GitHub account corresponds with the Private Key used to sign the commits, then you will notice that commits will be marked as verified in the GitHub user interface. See the example below from the cloudwithchris.com Git Repository Commits page.
-
JAMStack and the Cloud - A winning combination
Similarly, Cloud With Chris is an example of a JAMStack site, driven by Hugo, a static website generator. Rather than calling any backend APIs, the content is all entirely driven by markdown which is hosted in the GitHub repository mentioned a moment ago. This means I'm not calling any external APIs. Instead, the content is finalised at deployment time. I run a command in my GitHub Actions (Hugo build) which goes ahead and takes my site's configuration, necessary theme information and content, and renders the needed files to generate the set of webpages to render to my clients. The content is then uploaded to an Azure Blob Storage account which is publicly accessible and configured using the Static Website functionality.
checkout
-
Learning GitHub Actions in a Simple Way
checkout
-
Secure GitHub Actions by pull_request_target
To checkout the merged commit with actions/checkout on pull_request_target event, you need to get the pull request by GitHub API and set the merge commit hash to actions/checkout input ref.
-
Tell HN: PR GitHub Actions don't run over your commit by default
If you re-run GHA after master changes, CI is testing over different code.
You can [disable](https://github.com/actions/checkout#checkout-pull-request-head-commit-instead-of-merge-commit) on the checkout action:
```
-
GitHub Is Down
There was an outage yesterday too when the GitHub action “checkout@v3” broke when they released “checkout@v4”
Yes, they broke the ability for GitHub CI to checkout repos…
https://github.com/actions/checkout/issues/1448
- Can't use 'tar -xzf' extract archive file
-
Building project docs for GitHub Pages
The first two steps are setting up the job's environment. The checkout action will checkout out the repository at the triggering ref. The setup-python action will setup the desired Python runtime. My package supports Python 3.9+ so I'm targeting the minimum version for my build environments.
-
Automating GitHub Profile Updates with GitHub Actions
These first few steps demonstrate how you can run commands like npm install or import other workflows such as how it uses the actions/checkout to copy the contents of the repository into a working directory on the runner host. Read Reusable workflows for more about the syntax for referencing them.
-
Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions 🐳🐙
Check out the repo: We will use the actions/checkout action to checkout the repository.
-
[Actions] How do I take my dev branch, build it, and then create a pull request to main with the latest build artifacts?
Take a look at the checkout action usage here https://github.com/actions/checkout
-
Using Github Actions to publish your Flutter APP to Firebase App Distribution
Then, we have two important initial steps to define. The first one is an official GitHub Action used to check-out a repository so a workflow can access it. The second one it's pretty more complex but, briefly, downloads and set up a requested version of Java.
What are some alternatives?
smi-spec - Service Mesh Interface
ssh-action - GitHub Actions for executing remote ssh commands.
git-lfs - Git extension for versioning large files
cache - Cache dependencies and build outputs in GitHub Actions
keys
setup-node - Set up your GitHub Actions workflow with a specific version of node.js
static-web-apps-cli - Azure Static Web Apps CLI ✨
upload-artifact
Hugo - The world’s fastest framework for building websites.
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
billing
add-and-commit - :octocat: Automatically commit changes made in your workflow run directly to your repo