zef VS starter-workflows

To begin, you'll want to make sure that you have Raku installed, I recommend using Rakubrew. Then we'll want to install Zef, if you're new to Raku, Zef is basically just NPM or CPAN for Raku, it's written by the fabulous Ugexe and is the default package manager people use with Raku. If you installed Raku with Rakubrew, you can simply run rakubrew build-zef and it will handle all of the configuration for you.

I tested it on my computer. I needed to install zef from here. I installed libraries needed to use rakudo_debug. Here hat I get below:

See: https://github.com/ugexe/zef/blob/9779091b7997468257ce3037f8bc0e9c65d1f974/t/repository.rakutest#L85-L128 for an example of how the tiering of ecosystems work, and https://github.com/ugexe/zef/commit/a12d286312c6d7bc3c8ffebe51cce4caae6268cf for some reasoning

I have Rakudo 2022.07 on my Mac. I cloned https://github.com/ugexe/zef, which got me version 0.14.4. I cd'ed into the clone and ran this:

zef -v install https://github.com/ugexe/zef.git

FROM ghcr.io/jj/raku-gha ENV PKGS="git tar" PKGS_TMP="make gcc linux-headers musl-dev" WORKDIR="/home/raku" LABEL version="1.0.3" maintainer="[email protected]" rakuversion=$VER USER root RUN apk update && apk upgrade && apk add --no-cache $PKGS $PKGS_TMP USER raku # Environment ENV PATH="${WORKDIR}/.raku/bin:${WORKDIR}/.raku/share/perl6/site/bin:${PATH}" \ ENV="${WORKDIR}/.profile"\ RAKULIB="inst#/home/raku/.raku" # Basic setup, programs and init WORKDIR $WORKDIR RUN git clone --depth 1 https://github.com/ugexe/zef.git \ && cd zef && raku -I. bin/zef install . \ && zef install Linenoise \ && cd .. && rm -rf zef USER root RUN apk del $PGKS_TMP USER raku ENTRYPOINT ["raku"]

This is the issue I found on GitHub.

GitHub, as one of the leading web-based Git repository hosting service, provides a powerful suite of CI/CD tools in the form of GitHub Actions. These are directly integrated into the platform which empowers developers to increase the speed, efficiency and reliability of delivering products. In this brief article, we will take a look at what CI/CD is, why we should use it, as well as some of its applications in my projects.

GitHub Actions is a modern CI/CD tool integrated natively on GitHub. Itenables the rapid automation of build, test, deployment, and other custom workflows on GitHub with no need for external tools.

GitHub Actions is GitHub's CI/CD solution. You can use it to run automated tasks each time you change your code. Although the platform lacks a built-in Kubernetes integration, third-party plugins such as Azure's Deploy to Kubernetes Cluster action can automate deployments and manage different rollout strategies.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).