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

Multi-service support #1

Open
2 of 5 tasks
aquiladev opened this issue Feb 25, 2020 · 4 comments
Open
2 of 5 tasks

Multi-service support #1

aquiladev opened this issue Feb 25, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@aquiladev
Copy link
Owner

aquiladev commented Feb 25, 2020

It would be good to have multi-service support, besides default and custom endpoint.
Take a look https://www.npmjs.com/package/ipfs-deploy

  • infura
  • pinata
  • fission
  • ipfs-cluster
  • dappnode
@aquiladev aquiladev added the enhancement New feature or request label Apr 14, 2020
@aquiladev
Copy link
Owner Author

a5bcaec Pinata service support

aquiladev added a commit that referenced this issue Jun 27, 2020
@markg85
Copy link

markg85 commented Aug 14, 2020

Perhaps related, i'd very much like to pin it to multiple services in one script. So in my case to a IPFS node i'm running and to pinata.

@aquiladev
Copy link
Owner Author

@markg85 The issue is not related to simultaneous multi-service support. I think it is quite a rear case.
You can solve it with multiple steps in your pipeline yaml.
Something like:

    - name: Upload to IPFS
      uses: aquiladev/[email protected]
      with:
        path: ./build

    - name: Upload to Pinata
      uses: aquiladev/[email protected]
      with:
        path: ./build
        service: pinata
        pinataKey: ${{ secrets.PINATA_KEY }}
        pinataSecret: ${{ secrets.PINATA_SECRET }}

@markg85
Copy link

markg85 commented Aug 14, 2020

Ohh, that's awesome!
Thank you for that :)

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

No branches or pull requests

2 participants