This guide will walk you through adding a ChatGPT-like messaging stream to your Ruby on Rails 7 app using ruby-openai, Rails 7, Hotwire, Turbostream, Sidekiq and Tailwind. All code included below!
First, add the ruby-openai gem! Needs to be at least version 4. Add Sidekiq too.
| -- show running queries (pre 9.2) | |
| SELECT procpid, age(clock_timestamp(), query_start), usename, current_query | |
| FROM pg_stat_activity | |
| WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' | |
| ORDER BY query_start desc; | |
| -- show running queries (9.2) | |
| SELECT pid, age(clock_timestamp(), query_start), usename, query | |
| FROM pg_stat_activity | |
| WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' |
| # for redirecting hhtp traffic to https version of the site | |
| server { | |
| listen 80; | |
| server_name example.com; | |
| return 301 https://$server_name$request_uri; | |
| } | |
| # for redirecting to non-www version of the site | |
| server { | |
| listen 80; |
| # in features/support/env.rb | |
| require 'selenium/webdriver' | |
| # we need a firefox extension to start intercepting javascript errors before the page | |
| # scripts load | |
| Capybara.register_driver :selenium do |app| | |
| profile = Selenium::WebDriver::Firefox::Profile.new | |
| # see https://github.com/mguillem/JSErrorCollector | |
| profile.add_extension File.join(Rails.root, "features/support/extensions/JSErrorCollector.xpi") | |
| Capybara::Selenium::Driver.new app, :profile => profile |
| # Hack for Capybara to use SSL connections using selenium. | |
| # | |
| ### Usage: | |
| # Require this from rails_helper.rb | |
| # | |
| ### Steps to generate a SSL certificate on a Linux box: | |
| # 0. Starting from 'Rails.root' | |
| # 1. Generate private key. Type in some password. | |
| # $ openssl genrsa -des3 -out private.key 4096 | |
| # 2. Generate certificate sign request |
| # patch for make ruby error | |
| # % rbenv install 1.8.7-p375 | |
| # ... | |
| # ossl_pkey_ec.c:815: error: ‘EC_GROUP_new_curve_GF2m’ undeclared (first use in this function) | |
| # ossl_pkey_ec.c:815: error: (Each undeclared identifier is reported only once | |
| # ossl_pkey_ec.c:815: error: for each function it appears in.) | |
| # make[1]: *** [ossl_pkey_ec.o] error 1 | |
| # ... | |
| # | |
| # refs: http://forums.cpanel.net/f5/case-84173-error-installing-ruby-377831.html |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| #!/bin/bash | |
| # | |
| # DESCRIPTION: | |
| # | |
| # Set the bash prompt according to: | |
| # * the branch/status of the current git repository | |
| # * the branch of the current subversion repository | |
| # * the return value of the previous command | |
| # | |
| # USAGE: |
| (function() { | |
| // Usage: | |
| // | |
| // <script src='http://pressly.com/redirect.js' type='text/javascript'></script> | |
| // <script>Pressly.redirect("http://tablet.domain.com");</script> | |
| // | |
| /* >> Generated code from Issue Config */ | |
| // Supported devices to redirect |
