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.

Sign up for GitHub

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

Jump to bottom

Example of GP4BTC setup - NOT TO BE MERGED #244

Closed
wants to merge 7 commits into from
Closed

Example of GP4BTC setup - NOT TO BE MERGED #244

wants to merge 7 commits into from

Conversation

artursudnik
Copy link
Member

@artursudnik artursudnik commented Mar 14, 2023 •
edited
Loading

This PR makes it possible to recreate the gp4btc setup locally. The gp4btc backend needs to be also running on localhost:3000

@artursudnik artursudnik force-pushed the gp4btc-example branch 6 times, most recently from 26b8d48 to a625577 Compare April 12, 2023 07:55
@artursudnik artursudnik force-pushed the gp4btc-example branch 2 times, most recently from 0a54549 to f9f8e98 Compare May 12, 2023 10:04
@jrhender
Copy link
Contributor

@artursudnik do you think it's better to keep this PR open or close for now? I think that we can close as we have a working setup for GP4BTC and can always refer back to this PR if need be.

@artursudnik
Copy link
Member Author

sometimes I use this to replicate issues locally

@artursudnik
Copy link
Member Author

closing and leaving only branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@artursudnik @jrhender