| Architecture: Rails 3.2, Solr 1.4 with sunspot_solr gem, Apache HTTP server as reverse proxy to | |
| Rails app, Jquery UI | |
| Note: I don't care about the distinction between autocomplete and autosuggest. I am implementing what some | |
| people call autosuggest, and I'm calling it autocomplete. | |
| Given the above existing architecture, I want to add an autocomplete field into my app for a single | |
| attribute on a single model. It needs to be fast and secure (duh). The search target field could have | |
| white space and the search input should allow it, e.g., if I search with "iker's gui" it should return |
| # Nginx+Unicorn best-practices congifuration guide. Heartbleed fixed. | |
| # We use latest stable nginx with fresh **openssl**, **zlib** and **pcre** dependencies. | |
| # Some extra handy modules to use: --with-http_stub_status_module --with-http_gzip_static_module | |
| # | |
| # Deployment structure | |
| # | |
| # SERVER: | |
| # /etc/init.d/nginx (1. nginx) | |
| # /home/app/public_html/app_production/current (Capistrano directory) | |
| # |
In the seemlingly endless search for the actual correct and easy way to deploy a Rails app, we have tried several ways. We tried out using Apache2 and running a cluster of Thin servers. With the built in threading of Puma we decided to use it with Nginx.
Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.
| Start and stop the server on Windows | |
| Start and stop the server on Linux | |
| Start and stop Apache | |
| Start and stop the server on Windows | |
| Start the server from the Start menu | |
| Choose Start > All Programs > Adobe > Flash Media Server 4.5 > Start Adobe Flash Media Server 4.5. | |
| Choose Start > All Programs > Adobe > Flash Media Server 4.5 > Start Flash Media Administration Server 4.5. | |
| Stop the server from the Start menu |
| # PassengerMaxPoolSize | |
| # Default: 6 | |
| # For 2gb RAM: 30 | |
| # For 256 slice with MySQL running: 2 | |
| PassengerMaxPoolSize 2 | |
| # PassengerPoolIdleTime | |
| # Recommended to be avg time per page * 2 | |
| # In Google Analytics... (Avg time on site / Avg page views) * 2 | |
| # Default: 300 |
| /** | |
| * ReactJS: JavaScript like you've always done it. | |
| * | |
| * This example renders your top ten most followed friends/followers, `filter`ing | |
| * only your favorites, and putting a star on all verified accounts. | |
| * | |
| * With ReactJS, any time your data changes, the UI is always brought up to date | |
| * automatically. If friends length changes, or followCount - it always shows what | |
| * `render` describes. | |
| */ |
What I did to disable local delivery. I'll be using the example.com domain.
Requirements:
| # db/migrate/20131118172653_create_transactional_items_view.rb | |
| class CreateTransactionalItemsView < ActiveRecord::Migration | |
| def up | |
| select_sql = File.open("#{Rails.root}/db/migrate/20131118172653_create_transactional_items_view.sql", 'r') { |f| f.read } | |
| # for materialized view: | |
| view_sql = "CREATE MATERIALIZED VIEW transactional_items AS (#{select_sql})" | |
| # for normal view: | |
| view_sql = "CREATE VIEW transactional_items AS (#{select_sql})" | |