Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: use actions/cache to cache the install of neonctl #63

Open
martin-purplefish opened this issue Aug 29, 2024 · 4 comments
Open
Assignees

Comments

@martin-purplefish
Copy link

This would save about 10s per run.

@duskpoet duskpoet self-assigned this Aug 30, 2024
@duskpoet
Copy link
Member

duskpoet commented Sep 2, 2024

Hey!
I've tried caching npm cache directory and global node_modules and it didn't affect the npm i -g neonctl command duration. But the actual caching took 2m30sec!
Anyway, I think rewriting this project in JavaScript will also give it free caching capabilities.

@duskpoet
Copy link
Member

duskpoet commented Sep 2, 2024

@martin-purplefish
Copy link
Author

martin-purplefish commented Sep 2, 2024

@duskpoet try doing something like:

      - name: Install Neon CLI
        run: |
          if ! command -v neonctl &> /dev/null; then
            npm install --global neonctl@latest
          else
            echo "Neon CLI is already installed"
          fi

Also maybe the v4 action instead of v3?

@duskpoet
Copy link
Member

duskpoet commented Sep 2, 2024

This way we won't pick up the newest CLI version when it's released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants