31–40 of 101 posts
Earlier quoted context omitted.
Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.
FATAL: too many connections for role "ruwdncbzdkulsh"
Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
Looking forward to this. Anyone know a reason it can't support offline editing?
psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
This is a great example of a Minimum Viable Product. It has just enough features to be useful (multiple accounts, search, editing) and no more. From the website, they have plans to iterate quickly, with the help of what I'm sure will be a lot of feedback from the initial release. This kind of discipline in feature selection is admirable, and something we should all strive for in app development. My only critique is t…
psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
Kind of confused by this heroku error message I received? Are you storing my gmail credentials on heroku? When I tried again I have a google /looking/ login screen? http://cl.ly/1p0M0o2t0H1E3Z1h3i0n