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

Document how to run publish & deploy from fork #59

Open
DistributedDoge opened this issue Feb 5, 2024 · 0 comments
Open

Document how to run publish & deploy from fork #59

DistributedDoge opened this issue Feb 5, 2024 · 0 comments

Comments

@DistributedDoge
Copy link
Collaborator

DistributedDoge commented Feb 5, 2024

Instructions given in readme are sufficient to play with data portal in interactive manner:

  1. Clone on local machine OR enter codespace, install dependencies
  2. make dev to spin-up dagster.
  3. 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:

  1. Register filebase account
  2. Create filebase key and add it to repository- wide ${{ secrets.FILEBASE_KEY }} + ${{ secrets.FILEBASE_SECRET }}
  3. Create filebase bucket with new name ( gitcoin-grants-data-portal won't work = bucket names have to be unique site-wide)
  4. 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:

  1. Setup github pages.
  2. 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).

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

1 participant