console1984
console1984 copied to clipboard
basecamp
The Rails console you love, 1984 style
It currently asks for a name to log info, but with multiple folks having access any one can use anyone's name. Would be great to have a password issued to...
Because `thread_mattr_accessor` uses `Thread.current[]`, doing `self.prevent_instance_data_manipulation_after_freezing = false` in the `Object` extension doesn't work when using fibers (it defaults to `true`). FWIW discussions in https://github.com/rails/rails/issues/19693 seem related. In our case...
As the name suggests, storing console session data in the primary database results in the session record being rolled back in a transaction when running `rails console --sandbox` once it...
We are using this gem slightly different than originally designed. In order to better adapt it to our needs we needed the ability to make changes to some of the...
An incompability exists with https://github.com/Shopify/symbol-fstring. I'm not sure if the bug is in this gem or that one, but it's easier to make a test case here and I *think*...
Fixes https://github.com/basecamp/console1984/issues/91
In our app we have methods that read encrypted attributes from one record and save them in another record. ``` # first_name is encrypted user = User.find(id) other_user = User.find(other_id)...
Any statements entered while inside a pry console aren't added to the console1984_commands table. ### Steps to reproduce I created a [dummy repo](https://github.com/ohthatjames/console1984-pry-test) to test this. It's a vanilla `rails...
Hey @jorgemanrubia, I've been trying out a way to prevent direct access to certain `ENV` values in the console. The gem already takes care of Rails Credentials, so I thought...
Steps to reproduce: 1. `bundle console` 2. `require_relative 'config/environment.rb'` **Expected result:** it logs activity and prevents accessing encrypted data **Actual result:** it does not log activity nor prevents accessing encrypted...
