Closed skyrunner15 closed 11 months ago
Same here
@skyrunner15 the path was wrong, the right one is :/usr/src/app/db
. I have updated the README file. Let me know If this works.
Hmm... no dice. Now the instance gets stuck and doesn't start up with 0.6
From: Chris @.> Sent: Wednesday, November 15, 2023 10:23:30 AM To: chrisvel/tududi @.> Cc: Michael Nolan @.>; Mention @.> Subject: Re: [chrisvel/tududi] Docker volume not working (Issue #7)
@skyrunner15https://github.com/skyrunner15 the path was wrong, the right one is :/usr/src/app/db. I have updated the README file. Let me know If this works.
— Reply to this email directly, view it on GitHubhttps://github.com/chrisvel/tududi/issues/7#issuecomment-1812739513, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANAYSLUWHHHUYQWNPJ46R23YETM7FAVCNFSM6AAAAAA7MSFJGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSG4ZTSNJRGM. You are receiving this because you were mentioned.Message ID: @.***>
Can you try with 0.9 please? I believe it's fixed, I already tested it on 3 machines.
Just be careful with the volume, I changed the container path: -v ~/tududi_db:/usr/src/app/tududi_db
Works again. But for some reason I always get a "Invalid credentials" error.
This is my test config:
...
environment:
- TUDUDI_USER_EMAIL="mail@example.com"
- TUDUDI_USER_PASSWORD="test1234"
...
Even when I copy paste the credentials, I get this error
And the logs:
192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "POST /login HTTP/1.1" 200 2225 0.0021
192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0.0008
192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "GET /login HTTP/1.1" 200 2055 0.0007
W, [2023-11-16T12:11:46.979931 #9] WARN -- : Invalid credentials for user with email mail@example.com
I deleted the files in the persistent storage and the app loads fine for me in 0.9. I see the "production.sqlite3" file was created successfully. What doesn't work is the reverse proxy using HTTPS but that's another story :)
I will say this is coming along nicely! Using it for work today and fingers crossed my data stays here 😄
Works again. But for some reason I always get a "Invalid credentials" error.
This is my test config:
... environment: - TUDUDI_USER_EMAIL="mail@example.com" - TUDUDI_USER_PASSWORD="test1234" ...
Even when I copy paste the credentials, I get this error
And the logs:
192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "POST /login HTTP/1.1" 200 2225 0.0021 192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0.0008 192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "GET /login HTTP/1.1" 200 2055 0.0007 W, [2023-11-16T12:11:46.979931 #9] WARN -- : Invalid credentials for user with email mail@example.com
@TheZoker - did you use the right base 64 session key in the environment variables?
Works again. But for some reason I always get a "Invalid credentials" error.
This is my test config:
... environment: - TUDUDI_USER_EMAIL="mail@example.com" - TUDUDI_USER_PASSWORD="test1234" ...
Even when I copy paste the credentials, I get this error
And the logs:
192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "POST /login HTTP/1.1" 200 2225 0.0021 192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0.0008 192.168.2.90 - - [16/Nov/2023:12:11:37 +0000] "GET /login HTTP/1.1" 200 2055 0.0007 W, [2023-11-16T12:11:46.979931 #9] WARN -- : Invalid credentials for user with email mail@example.com
At this stage I'd suggest you rm the production.sqlite3 file manually from your local directory or just remove the docker volume. Then stop and re-run the command and it will work.
@TheZoker - did you use the right base 64 session key in the environment variables?
- TUDUDI_SESSION_SECRET=
Yes I set it using the openssl command. Something like this:
...
environment:
- TUDUDI_USER_EMAIL="mail@example.com"
- TUDUDI_USER_PASSWORD="test1234"
- TUDUDI_SESSION_SECRET="bf8bb1876432955442dbf2aedeb3f743c9f55a033d9f31dbeba6ff119ab1ee0cc4a5032364c49f0fa9966b344c221735ae9817dc20a08008f72ed2a367dc9914"
...
At this stage I'd suggest you rm the production.sqlite3 file manually from your local directory or just remove the docker volume. Then stop and re-run the command and it will work.
I already did this. Removed all the files, deleted the container and image and restarted everything. But still the same issue
Anything else I can test?
@TheZoker - did you use the right base 64 session key in the environment variables?
- TUDUDI_SESSION_SECRET=
Yes I set it using the openssl command. Something like this:
... environment: - TUDUDI_USER_EMAIL="mail@example.com" - TUDUDI_USER_PASSWORD="test1234" - TUDUDI_SESSION_SECRET="bf8bb1876432955442dbf2aedeb3f743c9f55a033d9f31dbeba6ff119ab1ee0cc4a5032364c49f0fa9966b344c221735ae9817dc20a08008f72ed2a367dc9914" ...
At this stage I'd suggest you rm the production.sqlite3 file manually from your local directory or just remove the docker volume. Then stop and re-run the command and it will work.
I already did this. Removed all the files, deleted the container and image and restarted everything. But still the same issue
Anything else I can test?
Did you change the password? The user is created the first time and then If you change it in the command it doesn't change in the database.
An alternative is to do a docker ps
to get the container id and then docker exec -it <docker_id> rake console
. Then User.last.update(password: "mynewpassword")
. It should output => true
. Then exit
and your new pass should work.
I was never able to login, so I don't think I changed the password anywhere.
When I run the update password function, this error happens:
I was never able to login, so I don't think I changed the password anywhere.
When I run the update password function, this error happens:
Are you using the latest image ?
I'm using this version:
image: chrisvel/tududi:0.9
I'm using this version:
image: chrisvel/tududi:0.9
Can you try to run docker exec -it <container_id> rake db:migrate
?
Done! Command went trough without any output
Thanks for your help BTW, really appreciate it, that you take your time to help me :)
No worries, thanks for your feedback!
When I pass this command into docker compose via portainer, no .db is created and a reload of the container wipes the data. I checked folder permissions which have everyone enabled for read/write.