StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Set up Capistrano to deploy</strong> You'll want to learn capistrano if you don't already know it, and use it to deploy your code in an automated way. This will involve setting up your shared directory and shared resources like database.yml.</p> <p><strong>Install C Based MySQL gem</strong> If you don't have all the required libs, this can take a little while, but less than 20 minutes. </p> <p><strong>Make sure you aren't vulnerable to common web application attacks</strong> Session fixation, session hijacking, cross-site scripting, SQL injection (probably you don't have to worry much about SQL injection). Be sure you use h() when outputting user-entered data in a view screen. Lots of good material online about this. </p> <p><strong>Choose a server architecture</strong> Nginx, Mongrel, FastCGI, CGI, Apache, Passenger: there is a lot to choose from. Think about how your app will be used and decide on the best architecture, then set it up. </p> <p><strong>Set up Exception Notifier or Exception Logger</strong> You will want your app to warn you when it breaks. Set one of these tools up to track production exceptions. Note: Exception notifier will warn you when routing errors occur (i.e. when people fat-finger URLs or script kiddies attack you): so think about what you want the framework to do when that happens and adjust accordingly. </p> <p><strong>Make sure all of your passwords are out of source control</strong> If you have database.yml, mail.yml (if you use yaml_mail_config) or other sensitive files in source control, get them out of there, replace them with database.yml.example, and put them in the shared/ folder on your server. </p> <p><strong>Ensure that your DB is locked down.</strong> A lot of people forget to secure MySQL when setting up their new production Rails box. Don't be like them. </p> <p><strong>Make sure all of the little web-files are in place</strong> If you are planning to be listed in Google, generate a <em>sitemap.xml</em> file. If you are planning to use an .<em>htaccess</em> file for something, make sure it's there. If you need a <em>robots.txt</em> file to prevent certain areas of your site from being indexed, make one. If you want a good looking <em>404 Page</em>, make sure it's set up correctly. If you want a "Be Right Back" page to be present when you deploy, make sure that you have a Capistrano maintenance file specified and Nginx or Apache knows how and when to redirect to it. </p> <p><strong>Get your SSL Certs in place</strong> If you are going to use SSL, make sure you get certificates that are valid on your production domain, and set them up. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload