Install Cadius with this simple Github Action -- enable ProDOS images in your workflows!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Dagen Brock 17c5fc128c
Merge pull request #4 from digarok/dependabot/npm_and_yarn/actions/core-1.9.1
1 week ago
.github cicd 2 years ago
dist rebuild 2 years ago
src fix documentation and branding for release 3 years ago
.gitignore fix documentation and branding for release 3 years ago
LICENSE initial test version 3 years ago update package 2 years ago
action.yml fix documentation and branding for release 3 years ago
package-lock.json Bump @actions/core from 1.2.6 to 1.9.1 5 months ago
package.json Bump @actions/core from 1.2.6 to 1.9.1 5 months ago
tsconfig.json Latest with inputs, P8 download and extractions 3 years ago

latest workflow


A Github Action for installing Cadius and allowing you to manipulate ProDOS disk images in your workflows.

Example usage

    # This will install Cadius on your Github Runner machine
    - name: Install Cadius
      uses: digarok/install-cadius-action@master
        include_prodos: true
    # Now you can use it to create a new bootable ProDOS disk
    - name: Create Boot Volume
    - run: |
        cadius createvolume exampledsk.po exampledsk 140KB
        cadius addfile exampledsk.po /exampledsk/ ./PRODOS.2.4.2/PRODOS


This action has one input: include_prodos. It defaults to true, it will download the latest release of ProDOS (2.4.2) and extract all of the files to a directory called PRODOS.2.4.2. This allows you to use those files, if needed, in subsequent steps. So you can create a bootable disk or even add BASIC.SYSTEM to launch into AppleSoft BASIC. If you don't need any of the ProDOS files, you can skip this by setting it to false and save a second or two.

Usage Recommendations

  1. While you can call Cadius directly from run commands as shown above, it makes sense to put your packaging command(s) in a script which can be run locally with the same results.
  2. Cadius uses a specific file, _FileInformation.txt for inferring ProDOS filetype and access information. That is not covered here, see the Cadius Documentation.
  3. This action is intended to pair really well with my install-merlin32-action which let's you assembled the 65xx source code to build your object/system files that can then packaged inside a ProDOS image file using this action for immediate use in your emulator or flash drive. I use this workflow to handle build and release all via Github Actions.


Cadius is a disk image program originally by the amazing French team, Brutal Deluxe. They are not involved with this Open Source version, but I do recommend you view their site for more information on Cadius and their other incredible tools and releases.

Further Examples

For a fully-integrated pipeline, see my example Apple II project here (