Replies: 9 comments
-
Update: replaced them with "true", now this:
|
Beta Was this translation helpful? Give feedback.
-
But I still need full instructions how to configure the dev backend manually. I cannot build docker every time I add a new line of code. I must be able to debug as I go. |
Beta Was this translation helpful? Give feedback.
-
Three weeks, no reaction... |
Beta Was this translation helpful? Give feedback.
-
@Impa10r , were you able to run with this? |
Beta Was this translation helpful? Give feedback.
-
@Impa10r, it worked for me stopping and removing previously built docker images cd robosats/frontend
npm install
npm run dev
# CTRL + C
cd ../nodeapp
docker compose up |
Beta Was this translation helpful? Give feedback.
-
I wanted to develop |
Beta Was this translation helpful? Give feedback.
-
This is a setup for frontend development (simple things). Incidentally the setup you used in your bug description is also for frontend development. If you want to run the backend you need to docker compose at the repo root. |
Beta Was this translation helpful? Give feedback.
-
I want to debug and develop backend |
Beta Was this translation helpful? Give feedback.
-
Then your best option is to use Docker |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Having a hard time trying to set up a dev environment following the setup.md instructions.
robosats.onion.moe:8081 opens Wordle Game
I did redirect robosats.onion.moe:8081/static/frontend/main.js to 127.0.0.1:8081/frontend/main.js, but still get Wordle Game at robosats.onion.moe:8081. Opening robosats.onion.moe:8081/static/frontend/main.js shows js code instead of Not Found, so the redirect definitely works.
If I try to start my own back-end in docker, I get this:
Desktop (please complete the following information):
Beta Was this translation helpful? Give feedback.
All reactions