-
Notifications
You must be signed in to change notification settings - Fork 16
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
Doesn't seem to actually talk to the database #30
Comments
How we handle this is actually very interesting. We don't throw up lots of error messages when your not connected because the sync is so good. Plus when your out and about we want it to be seemless. When it is connected you should see a "Replication complete" pop up in the bottom right. I bet if you open the console something is happening if you configured the couchdb info in the connection screen. |
Just wanted to posted here, as @LeeThompson might have ran into the same thing I just did... I initially randomly generated a password for my "couch" admin user: The connection screen would just keep trying to load. If I refreshed the page everything seemed to be "happy" but nothing really worked. A few times I got another couchdb user account which would load the tool, but nothing would ever seem to update the couchdb. Turns out, it looks like the webapp didnt like one of the special characters in: As a test, I make a new password of just uppercase, lowercase letters and numbers, and everything was miraculously happy. |
I set it up on my Synology (I can't use docker-compose but I followed the instructions, btw you missed the step on actually creating the database), but I see no evidence that StoreDown ever communicates with CouchDB, it doesn't throw any error messages but so far the database has literally nothing in it.
UPDATE: I'm already moving onto a different solution.
The text was updated successfully, but these errors were encountered: