-
Notifications
You must be signed in to change notification settings - Fork 7
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
WIP: Quality of life Updates #47
Conversation
Still a few things to do, but initially everything built properly so that's a good first step. |
- python runtime env - react proxy for local run
@you3h Got the new submodule in place, however I can't seem to load the UI. When hitting the react container directly: I get no log output from the container: ~/g/loopygen (dev/react-ui)> docker-compose logs react
Attaching to loopygen.react
loopygen.react | > loopminterjs-api@1.0.0 start
loopygen.react | > node index.js
loopygen.react | 2022-04-22T16:08:57.704Z: [info] [LOOPMINTER_API] version 1.0.0 starting
loopygen.react | 2022-04-22T16:08:57.707Z: [info] [NFT SERVICE] started
loopygen.react | 2022-04-22T16:08:57.707Z: [info] [Image SERVICE] started
loopygen.react | 2022-04-22T16:08:57.710Z: [info] [LOOPMINTER_API] started, listening at port 8000 Maybe there are some strict CORs settings in the app somewhere? If not, I wasn't having this issue when this was a branch of the larger repo, so something must have changed path-wise. |
Issue above is resolved, new list that block merge: |
TODO:
Things to prepare for on the Wiki:
Nice-to-have: