Attention: the list was moved to
This page is not maintained anymore, please update your bookmarks.
|# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine|
|# This is how I upload my new Sol Trader builds (http://soltrader.net)|
|# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash|
|S3KEY="my aws key"|
|S3SECRET="my aws secret" # pass these in|
Locate the section for your github remote in the
.git/config file. It looks like this:
[remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = email@example.com:joyent/node.git
Now add the line
fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
cmder will be refered as console
##Mac Os, Ubuntu and windows users continue here:
Web fonts are pretty much all the rage. Using a CDN for font libraries, like TypeKit or Google Fonts, will be a great solution for many projects. For others, this is not an option. Especially when you are creating a custom icon library for your project.
Rails and the asset pipeline are great tools, but Rails has yet to get caught up in the custom web font craze.
As with all things Rails, there is more then one way to skin this cat. There is the recommended way, and then there are the other ways.
Here I will show how to update your Rails project so that you can use the asset pipeline appropriately and resource your files using the common Rails convention.