You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current working directory where you start up the taps server must be read/writable so the server can create the sqlite://tabs.db file. This is not always the case. I got a very confusing warning:
/Library/Ruby/Gems/1.8/gems/sqlite3-ruby-1.2.5/lib/sqlite3/errors.rb:62:in `check': SQLite3::CantOpenException could not open database: unable to open database file (Sequel::DatabaseConnectionError)
(i.e. To recreate, cd to a read-only directory, then try to start up a taps server)
So, perhaps add a startup check to make sure :taps_database_url is writeable (and print out a warning if it is not), or have the url point, instead, to a temp directory.
The text was updated successfully, but these errors were encountered:
The current working directory where you start up the taps server must be read/writable so the server can create the sqlite://tabs.db file. This is not always the case. I got a very confusing warning:
/Library/Ruby/Gems/1.8/gems/sqlite3-ruby-1.2.5/lib/sqlite3/errors.rb:62:in `check': SQLite3::CantOpenException could not open database: unable to open database file (Sequel::DatabaseConnectionError)
(i.e. To recreate, cd to a read-only directory, then try to start up a taps server)
So, perhaps add a startup check to make sure :taps_database_url is writeable (and print out a warning if it is not), or have the url point, instead, to a temp directory.
The text was updated successfully, but these errors were encountered: