Pamplejuce Docs Getting Started How does this all work? Setting up your project Setting up Code Signing Customization File Management Including files outside of /source JUCE Adding JUCE Modules Private JUCE modules Dealing with Binary Data JuceHeader.h GitHub Actions 101 Tips and Gotchas How do GitHub variables work? Using self-hosted runners Life with Pamplejuce Adding Tests and Benchmarks Clang Format Managing Releases How to update your Project Other stuff The `SharedCode` interface target Example projects Original References & Insipration
Pamplejuce Docs > JUCE > Private JUCE modules
Table of Contents +

Private JUCE modules

You can also use a JUCE module that is not publicly published.

Generate an ssh key (without a passphrase) for the repository and add it as a secret to your Pamplejuce-derived repository.

Then, use the ssh_key option in the checkout action, like so:

- name: Checkout code
  uses: actions/checkout@v3
  with:
    ssh_key: ${{ secrets.SSH_PRIVATE_KEY }}
    submodules: true # Get JUCE populated

See @mikelange49’s solution here.

< Previous
Adding JUCE ModulesNext >
Dealing with Binary Data

Last Updated

Posted on 

 by sudara

Leave a Reply

Your email address will not be published. Required fields are marked *