サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
TGS2024
collectiveidea.com
Collective Idea Home Blog Home Blog Contact Bundler’s Multiple Source Security Vulnerability How Bundler is broken and what you can do about it by Steve Richert October 6, 2016 Bundler has a major security vulnerability that affects all stable versions. The vulnerability allows an attacker to inject arbitrary code into your application via any secondary gem source declared in your gemfile, whether
Cleanly integrating modern Javascript into a Rails app by Jason Roelofs March 9, 2016 Updated November 27, 2016 with tweaks as well as an example Rails 5 site showcasing this setup. Want to write ES6 and/or use JSX or any of a vast array of modern Javascript tools in your Rails app? What about also writing your Javascript tests with the same tools? It’s easy with Browserify-rails and Teaspoon! I’l
Photo © Vaughan Leiberum https://www.flickr.com/photos/laertes_za/5342495338/. Licensed under a Creative Commons license. Updated May 13, 2016 with new brew services syntax PostgreSQL 9.5 was released yesterday and has a lot of cool new features. If you’re on Mac OS X and using Homebrew, you can upgrade with the steps below. Note: Keita Kobayashi guide to upgrading to 9.4 is a great resource and t
Optimizing Rails for Memory Usage Part 3: Pluck and Database Laziness This is part three in a four-part series on optimizing a potentially memory-heavy Rails action without resorting to pagination. The posts in the series are: Part 1: Before You Optimize Part 2: Tuning the GC Part 3: Pluck and Database Laziness Part 4: Lazy JSON Generation and Final Thoughts Pluck the Chicken If changing Ruby’s GC
Optimizing Rails for Memory Usage Part 1: Before You Optimize This is part one in a four-part series on optimizing a potentially memory-heavy Rails action without resorting to pagination. The posts in the series are: Part 1: Before You Optimize Part 2: Tuning the GC Part 3: Pluck and Database Laziness Part 4: Lazy JSON Generation and Final Thoughts We recently built an API server for a mobile appl
Spring, as described in its README, is a Rails application preloader. It speeds up development by keeping your application running in the background so you don't need to boot it every time you run a test, rake task or migration. I want to focus on the first assertion in the description above… It speeds up development I should begin by saying that I love the idea of Spring. As a developer, any tool
Flash messages were one of those little features that amazed me when I was first introduced to Rails. Developers often use Rails' flash to display messages to their users, but messages aren't the only reason to use flash. A typical interaction with flash looks something like this in the controller: class OrdersController < ApplicationController def new @order = Order.new end def create @order = Or
Update: Heroku has now posted a more complete Unicorn setup here.) In 3 easy steps you can setup a rails app on Heroku that can easily handle 200 requests per second and 100 concurrent connections, for free. Step 1: Use Unicorn With the Cedar stack on Heroku, you can now run any process, so why not use Unicorn. Here’s how to set this up. Add this to your Gemfile group :production do gem 'unicorn'
On a current project, we switched our javascript driver to Poltergeist, a driver for Capybara that allows you to run your tests in a headless browser provided by PhantomJS. Happy days and green dots locally, but our build server on Travis CI had a different opinion. Failure/Error: And I am logged in as user "[email protected]" Capybara::Poltergeist::PhantomJSTooOld: PhantomJS version 1.6.1 is too
If I sat down with your code base and asked you how such-and-such a feature is implemented, what would you say? Would you lead me through controller filters and actions? What about model methods, includes, callbacks or observers? How about objects in lib/ (oh, and there’s also this other call to a mailer to make sure emails get sent out…), or would you even dive down into the database itself? Or w
One eventuality in the mobile development space these days is that you will, at some point, find yourself in need of a backend service for your app. You can handle this in a variety of ways: pay a company like Collective Idea to do it for you write it yourself use one of the backend-as-a-service web apps that are springing up. One such backend-as-a-service is Parse.com. They have SDKs for iOS and
Photo by Tambako the Jaguar, used under Creative Commons https://flic.kr/p/e9AnTA At Collective Idea, we ♥ Cucumber, Capybara and ChromeDriver… and alliteration. But we recently encountered an issue with a very Ajaxy Rails app where we need to test a file download and assert its content. Our scenario looks like: Scenario: Exporting the fruits list Given the following fruits exist: | Name | Color |
A recent project has us using spine.js as well as a few other JavaScript libraries. Though spine.js comes with its own routing, it conflicts with pjax. The solution was to roll our own. The requirements are simple, we should be able to give it a set of routes and their corresponding callbacks and we should be able to process the browsers url upon request. The CoffeeScript for that looks like this:
Most of the time, you test your apps on a fast connection, especially when working on a local machine. Most of your clients/visitors/customers aren’t so lucky, but how do you simulate their connection speed? If you have installed Xcode on Lion, you have access to a very cool tool called Network Link Conditioner[1]. It is a preference pane, but not installed by default. You’ll find it in /Developer
Ruby 1.9.3-p0 makes psych—the replacement for 1.8.7’s YAML library, Syck—the default YAML parser. Psych is a wrapper around libyaml, so you’re going to need it installed and configured before installing Ruby. If you install 1.9.3-p0 without libyaml, you’ll see warnings like this: It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml a
Collective Idea Home Blog Home Blog Contact Photo by Tambako the Jaguar, used under Creative Commons https://flic.kr/p/dJD2dV We frequently swap out Firefox for Chrome in our selenium (@javascript) cucumber tests. It is actually very easy, but not widely known. Update: I got some questions about **why** we'd use Chrome. Speed hasn't been the issue (use capybara-webkit for that) but we have found s
At Collective Idea, we do a lot of work with RESTful JSON APIs. They can be a joy to build but a pain to test. We’re currently working on a project that’s all API all the time, so we developed some reusable Cucumber steps for testing. Now, we’ve abstracted all that goodness out into its own gem… json_spec. The Gem The json_spec gem is a collection of RSpec matchers and a collection of Cucumber ste
Update: Rails 3.1 bakes this in, so I've updated the instructions below to show that. So you saw Firesheep and are worried about security in your app? That’s good, you should be. SSL is easy to do and there’s no reason not to these days. Also, the tools are much better than before, so let’s get started. 1. Use SSL all the time There are two great gems that you can use if you’re on Rails 2.3*/strik
It’s a given: being happy makes us more productive. A few weeks ago while pairing, we decided that choirs should sing and crowds should cheer whenever we commit. I now have this in .git/hooks/post-commit for the projects that I work on most often: #!/bin/sh afplay ~/.git/happykids.wav > /dev/null 2>&1 & Here is the sound file it plays. I giggle every time I commit. It makes me want to start on the
このページを最初にブックマークしてみませんか?
『Collective Idea』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く