æon 
UPDATE: In hindsight I should probably have read the development guide, the first sentence of which is "don't use docker to do development"
I installed a version manager to install a VM so I could use a package manager to install another package manager #webdev
got a non-docker setup now, but
- running it in the 'development' environment causes it to fail due to being unable to find ActiveRecordQueryTrace
- running it in 'test' works, but rspec fails trying to require rspec/expectations
just noticed that .ruby_version specifies v2.3.1 but the gems are being installed into vendor/bundle/ruby/2.3.0 :thinking: #mastodev
(I think this is maybe why I can't get rspec to work?)
UPDATE: no. the reason I couldn't get rspec to work was because .bundle/config had BUNDLE_WITHOUT set to "development:test", so none of the testing-related gems were being installed
I don't know why that happened, though
anyway now the gems are installed and rspec runs but it's complaining about not being able to connect to redis (which is definitely running) #mastodev
still getting redis errors. I can connect to the redis instance just fine from both redis-cli and irb, so I'm kinda not sure what's the deal here
(specifically the redis connection is timing out while running rspec tests)
it works now! thanks to @nightpool for assistance #mastodev
unfortunately the thing I was working on got trashed by upstream changes while I was trying to get my dev environment set up :/
I have done a pull request
...FOR THE FEDERATION
wow codeclimate isn't fuckin happy about this