Value | Color |
---|---|
\e[0;30m | Black |
\e[0;31m | Red |
\e[0;32m | Green |
\e[0;33m | Yellow |
\e[0;34m | Blue |
\e[0;35m | Purple |
#!/bin/sh | |
cmd=$* | |
authorize() { | |
for host | |
do xhost | egrep -q "^INET6?:$host$" || xhost + $host | |
done | |
} |
unless ARGV.size > 0 | |
puts " Missing executable file argument" | |
puts " Usage (in a Dockerfile)" | |
puts " RUN crystal run ./path/to/list-deps.cr -- ./bin/executable" | |
exit 1 | |
end | |
executable = File.expand_path(ARGV[0]) | |
unless File.exists?(executable) |
I use tmux splits (panes). Inside one of these panes there's a Vim process, and it has its own splits (windows).
In Vim I have key bindings C-h/j/k/l
set to switch windows in the given direction. (Vim default mappings for windows switching are the same, but prefixed with C-W
.) I'd like to use the same keystrokes for switching tmux panes.
An extra goal that I've solved with a dirty hack is to toggle between last active panes with C-\
.
Here's how it should work:
# If you're having cert issues on ruby 2.0.0-p0, the issue is most likely that ruby can't | |
# find the required intermediate certificates. If you built it via rbenv/ruby-build, then | |
# the certs are already on your system, just not where ruby expects them to be. | |
# When ruby-build installs openssl, it installs the CA certs here: | |
~/.rbenv/versions/2.0.0-p0/openssl/ssl/cacert.pem | |
# Ruby is expecting them here: | |
$(ruby -ropenssl -e 'puts OpenSSL::X509::DEFAULT_CERT_FILE') | |
# Which for me, is this path: |
RSpec.configure do |config| | |
config.around do |example| | |
# For examples using capybara-webkit for example. | |
# Remove this if you don't use it or anything similar | |
if example.metadata[:js] | |
example.run | |
ActiveRecord::Base.connection.execute("TRUNCATE #{ActiveRecord::Base.connection.tables.join(',')} RESTART IDENTITY") | |
else | |
ActiveRecord::Base.transaction do |
upstream plex-upstream { | |
# change plex-server.example.com:32400 to the hostname:port of your plex server. | |
# this can be "localhost:32400", for instance, if Plex is running on the same server as nginx. | |
server plex-server.example.com:32400; | |
} | |
server { | |
listen 80; | |
# server names for this server. |
With Heroku's JRuby support you may have already seen that you can run TorqueBox Lite on Heroku. But, that only gives you the web features of TorqueBox. What about scheduled jobs, backgroundable, messaging, services, and caching?
With a small amount of extra work, you can now run the full TorqueBox (minus STOMP support and clustering) on Heroku as well! I've successfully deployed several test applications, including the example Rails application from our Getting Started Guide which has a scheduled job, a service, and uses backgroundable and messaging.
This example uses TorqueBox 3.0.2, but the instructions may work with other TorqueBox versions.
- Create a JRuby application on Heroku, or convert an existing application to JRuby. Make sure your application works on JRuby on Heroku before throwing TorqueBox into the mix.
- Add th
# Place in config/initializers | |
ActiveRecord::Base.class_eval do | |
class << self | |
def inherited_with_strong_params(sub) | |
inherited_without_strong_params(sub) | |
# Filter out plugin models that won't work with strong_parameters yet | |
unless sub.name =~ /^doorkeeper/i | |
sub.send :include, ActiveModel::ForbiddenAttributesProtection | |
end | |
end |