-
Notifications
You must be signed in to change notification settings - Fork 12
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
[BUG] <title> Setting up a branch for working in local #254
Comments
You should change 'Change It!' to a proper password @filimannino that's why it does not work. |
I managed to get the site locally but running: During the make install process I got several errors and I downloaded all the things needed but I think I messed up something. I have changed a lot of files formatting so that I can arrive at the end of the process. |
Nevertheless, I restarted the procedure from scratch. I have fetched a new branch. I changed the password as you said. @guilbep mkdir -p secrets && cat <<EOF > secrets/.env
POSTGRES_USER=ccfatigue
POSTGRES_PASSWORD=manninof
EOF Then I run:
Everything smooth When I run make dev-backend: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: password authentication failed for user "ccfatigue" (Background on this error at: https://sqlalche.me/e/14/e3q8) I also tried: |
@filimannino when changing the password, you need to recreate the database, so you should probably delete the current volume, and restart the database with the new password. |
Ok, i managed to and I got the site running without changing anything. Thank you @guilbep I have run:
I opened another shell and I put:
Now i have the site in local but I cannot see the changes in the .vue file clicking just the refresh button on google. |
In addition I tried with this simple change in the DataUpload.vue: Mi chiamo Filippo And i got this error: ERROR Failed to compile with 1 error 6:01:22 PM [eslint] ✖ 1 problem (1 error, 0 warnings) You may use special comments to disable some warnings. ✖ 1 problem (1 error, 0 warnings) webpack compiled with 1 error Moreover I am sure that the problem is in the newline command because if I only add text the site still runs. For example:
becomes
And everything is ok. |
Hello @filimannino If you want me to have a look, you need to push your changes to your branch. That way it'll be available to everyone.
Also, a good rule is: One problem == One issue |
Ok. Regarding the refreshing of the page is not a problem of compiling. Because by only changing a word it doesn't work. @guilbep I put this: Then i change with this |
@filimannino in what file ? Do you save the file ? |
In DataUpload.vue. Of course I save the file! @guilbep I have pushed the branch. Is everything ok? Can you please have a look at it? Can we please have a teams call in which you show me all the correct procedures? Thank you. |
@filimannino I cannot see your latest commit only that you have created a branch called: Filippo_Mannino_february3rd) I can make the changes reflect directly in the browser as you can see in the following videos, I sent you a zoom meeting so we can see what's wrong on your side ccfatigue.webm |
Thank you! |
Is there an existing issue for this?
Current Behavior
I tried in changing the sync-url and it seemed working. BTW I don't know what is the docker volume.
After that I got problems in running:
make dev-frontend
It gives me error which I think are related with the ending line character.
Can we please setup a quick TEAMS call today in which I share my screen so we can solve all these problems and I can start working?
Thank you.
@guilbep @charlottegiseleweil
Expected Behavior
No response
Steps To Reproduce
mkdir -p secrets && cat < secrets/.env
POSTGRES_USER=ccfatigue
POSTGRES_PASSWORD=Change It!
EOF
make install
Here I got this
46 vulnerabilities (7 low, 19 moderate, 17 high, 3 critical)
make dev-database
make dev-backend
ValueError: invalid interpolation syntax in 'postgresql://ccfatigue:Change+It%21@localhost:5432/ccfatigue' at position 32
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: