funkytwig: I'd be curious about the models, I assume you have associations setup between Walk and WalkSection ?
funkytwig: I'd try to do something along the lines of this: https://gist.github.com/jtperreault/7ce89a1d57fe374496529fd5eb3ffb43
funkytwig: in this case, we use the .find() method rather than .where() which will return the WalkSection instance with the ID you pass in, rather than an Array of results which you would get using .where()
funkytwig: and then on the next line, assuming you have the model associations, we just call for the Walk instance based on the WalkSection that you found
funkytwig: not sure what you're asking... would need to see the view files, and model files too for the whole picture. otherwise im just making my best guess
funkytwig: but if @walk returns nothing in the view then that'd require some more looking... I would open up a rails console, create an instance of the WalkSection in question, and then see if you can get a Walk instance by calling .walk
memo1: I'm pretty sure you can find that in heroku under the app's settings, open the config vars
memo1: Not sure if you can from a rails console, check this for help perhaps? https://devcenter.heroku.com/articles/config-vars#setting-up-config-vars-for-a-deployed-application
What's the standard place for setting my sidekiq log level for production? I assume I should add Sidekiq::Logging.logger.level = Logger::WARN to the bottom of my environments/production.rb file as opposed to opening a conditional env check in the sidekiq initializer... thoughts?
terrabl: I believe JSON.parse() uses string keys (not symbols) by default. So, based on your example, you should be able to access the data using hash["key"] rather than hash[:key]