You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instructions given in readme are sufficient to play with data portal in interactive manner:
Clone on local machine OR enter codespace, install dependencies
make dev to spin-up dagster.
Enter dagster instance, run whichever models you want.
BUT, what steps are needed to run publish & deploy Github Actions workflow from a fork?
Here is the summary of steps I had to take, may be slightly outdated:
Register filebase account
Create filebase key and add it to repository- wide ${{ secrets.FILEBASE_KEY }} + ${{ secrets.FILEBASE_SECRET }}
Create filebase bucket with new name ( gitcoin-grants-data-portal won't work = bucket names have to be unique site-wide)
Change filebaseBucket: gitcoin-grants-data-portal inside /.github/workflows/run.yml to new bucket name
This is for bucket, now we may also need to:
Setup github pages.
Register Covalent Account + add key to repository secrets
Once I have a moment I would put those steps in small HOW TO document on the off-chance that there is a single person somehow interested in running 100% independent replica of a portal (I found it handy for development to test CI changes + preview how portal-site would look like).
The text was updated successfully, but these errors were encountered:
Instructions given in readme are sufficient to play with data portal in interactive manner:
make dev
to spin-up dagster.BUT, what steps are needed to run
publish & deploy
Github Actions workflow from a fork?Here is the summary of steps I had to take, may be slightly outdated:
${{ secrets.FILEBASE_KEY }}
+${{ secrets.FILEBASE_SECRET }}
gitcoin-grants-data-portal
won't work = bucket names have to be unique site-wide)filebaseBucket: gitcoin-grants-data-portal
inside/.github/workflows/run.yml
to new bucket nameThis is for bucket, now we may also need to:
Once I have a moment I would put those steps in small
HOW TO document
on the off-chance that there is a single person somehow interested in running 100% independent replica of a portal (I found it handy for development to test CI changes + preview how portal-site would look like).The text was updated successfully, but these errors were encountered: