FHIR Chat · attempt to write a readonly database error · inferno

Stream: inferno

Topic: attempt to write a readonly database error


view this post on Zulip Richard Braman (Jul 25 2020 at 17:21):

This is my opening into Inferno, more posts to come but first I have to get something back from the Commmand line. I didn't see any mention of database setup in the Readme.

bundle exec rake --trace inferno:execute[https://sandbox.dpc.coms.gov/v1/api,bdt]
INFO | Inferno | Environment: development
/Users/richardbraman/.rvm/rubies/ruby-2.5.6/lib/ruby/gems/2.5.0/gems/data_objects-0.10.17/lib/data_objects/pooling.rb:149: warning: constant ::Fixnum is deprecated
** Invoke inferno:execute (first_time)
** Execute inferno:execute
rake aborted!
DataObjects::ConnectionError: attempt to write a readonly database

I get that Inferno suns SQLlite, but that came with my Mac (no need to install), and there is no mention of the sqlite database file that needs to have its permissions modified in the README. Those files are in the root of the project in the data directory.

I can get around the permissions error for now by running inferno as sudo

view this post on Zulip Robert Scanlon (Jul 27 2020 at 13:52):

Hi Richard -- you are right, the sqllite files are in [project_root]/data. As long the *.db files are writable by your user I believe it should just work. Our intent was to not require sudo.


Last updated: Apr 12 2022 at 19:14 UTC