-
Notifications
You must be signed in to change notification settings - Fork 196
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
Problem getting the app running locally #269
Comments
Thanks for reporting! Based on the details provided, it seems that you mixed between the instructions of setting up Pezzo in development mode VS spinning up the working stack for usage only. Which means we should probably improve the docs. What is your goal? Do you want to modify the code? Or just run it locally and experiment? |
@arielweinberger I first tried the full docker appoach:
after that I brough down the docker containers, tried to set it up locally
and i got the same error this way |
also if you help me out with that I'd be happy to contribute back by improving the readme or docs if I can :) |
Cool! Let's stick to the first path of just running Also, can you share the logs coming from the server container in the stack? |
Update: I think this is caused by an issue with signing up/in via email and password (vs SSO using Google). Will continue to investigate. |
So, let's start from the start:
then docker ps:
meaning all is up and running. |
I started experiencing the same issue. |
Any update here? Can I help in any way? |
Hey folks, I'm still investigating the root cause. It's pretty recent. If you want to run Pezzo and try it out, I suggest trying v0.6.9 (in the compose files), prior to a recent update we've made, where this is a non issue. Upgrading once fixed should be straightforward - there are no breaking changes. Sorry about that. |
@arielweinberger thank you, not a problem at all! |
@grski @arielweinberger Hello guys, any updates in this issue? I faced the issue even with v0.6.9 ! |
@grski @arielweinberger Hello Folks, Do we have any update here ? |
@dmockingbird551 I have tried to reproduce the issue and failed. Since it was created some things have changes. Can you try to see if it still happens to you and share new logs? @Hicham-azer fyi |
@ranst91 Getting the same issue
|
This log seems to happen because of missing .env file. |
Can we please fix this issue ? I'm not able to use ( I see similar problems in running locally in other threads) this awesome library because of these issues. |
@dmockingbird551 use the .env.example file to create a .env (and possibly also a .env.docker) files (include your actual credentials in the new files) If you are still unable to use, the logs should tell a different story, feel free to post the new errors here |
Report
First of all - awesome stuff!
I followed the insctruction from the docs and from the README.
On top of that I've copied the envs from server and console into .env file at the root.
Tried runnign both through:
docker-compose -f docker-compose.infra.yaml up
npx nx serve server npx nx serve console
and just docker compose up
in both cases after login i'm facing an error when trying to get to the console:
Expected behavior
No response
Steps to reproduce the problem
Logs (if applicable)
Pezzo version
latest git clone
How do you use Pezzo?
Docker Compose
The text was updated successfully, but these errors were encountered: