underpantsgnome.com UnderpantsGnome

underpantsgnome.com
Title: UnderpantsGnome
Keywords:
Description: UnderpantsGnome UnderpantsGnome 1. Collect Underpants 2. ??? 3. Profit! Around the web Github Twitter JABE 0.8.0 October 05, 2012 02:59 What’s new: Bootstrap 2.1.1 Removed Haml Removed Sass Remov
underpantsgnome.com is ranked 0 in the world (amongst the 40 million domains). A low-numbered rank means that this website gets lots of visitors. This site is relatively popular among users in the united states. It gets 50% of its traffic from the united states .This site is estimated to be worth $0. This site has a low Pagerank(0/10). It has 1 backlinks. underpantsgnome.com has 43% seo score.

underpantsgnome.com Information

Website / Domain: underpantsgnome.com
Website IP Address: 52.10.233.30
Domain DNS Server: ns-1689.awsdns-19.co.uk,ns-402.awsdns-50.com,ns-1382.awsdns-44.org,ns-534.awsdns-02.net

underpantsgnome.com Rank

Alexa Rank: 0
Google Page Rank: 0/10 (Google Pagerank Has Been Closed)

underpantsgnome.com Traffic & Earnings

Purchase/Sale Value: $0
Daily Revenue: $0
Monthly Revenue $0
Yearly Revenue: $0
Daily Unique Visitors 0
Monthly Unique Visitors: 0
Yearly Unique Visitors: 0

underpantsgnome.com WebSite Httpheader

StatusCode 200
Cache-Control max-age=0, private, must-revalidate
Content-Type text/html; charset=utf-8
Date Wed, 10 Aug 2016 10:26:23 GMT
Server Apache/2.4.7 (Ubuntu)

underpantsgnome.com Keywords accounting

Keyword Count Percentage

underpantsgnome.com Traffic Sources Chart

underpantsgnome.com Similar Website

Domain Site Title

underpantsgnome.com Alexa Rank History Chart

underpantsgnome.com aleax

underpantsgnome.com Html To Plain Text

UnderpantsGnome UnderpantsGnome 1. Collect Underpants 2. ??? 3. Profit! Around the web Github Twitter JABE 0.8.0 October 05, 2012 02:59 What’s new: Bootstrap 2.1.1 Removed Haml Removed Sass Removed simple_form Removed bootstrap-sass gem Comments: 0 JABE 0.6.1, Rails 3.1+ and mountable February 01, 2012 04:19 So I finally got around to updating JABE yeah I know its been forever (about a year). Well it now plays nice with Rails 3.1+ and you can now mount it to any path you want instead of just the root. Comments: 0 Sass on Heroku or any generated files for that matter May 11, 2011 22:34 Here’s yet another take on how to handle generated files when you are deploying to Heroku while keeping your git repo free of the artifacts. We deploy using a rake task rake deploy that was generating Jammit files, committing them to the repo and pushing them up. This works fine, but adds “junk” commits to your repo and even the occasional merge conflict from the generated files. Since Heroku doesn’t care what you push to it as long as it is in the master branch on their end, why not generate the assets in a throwaway branch and push that up? Here are the basic commands you would run in the shell. Wrap them up in a rake task that fits your project and off you go. # send it up to github git push origin master # get rid of the branch if it exists (it shouldn't) git branch -D deploy # generate Jammit, Sass, etc. files rake cache_assets # push it up to heroku, need force since it's a different branch every time git push heroku deploy:master --force git checkout master # get rid of the old branch git branch -D deploy As long as everybody uses the rake task to deploy you shouldn’t have any problems with this technique. Comments: 0 Queue failed Solr calls with Delayed::Job May 04, 2011 21:36 We are using websolr.com from one of our Heroku apps and from time to time we see connection errors. This is disruptive in the UI. One option was to move all of the Solr calls to DJ tasks, but I didn’t want to have a ton of stuff in the DJ queue. The other option was to make a variation of SilentFailSessionProxy and have it queue up the jobs we cared about, specifically index and remove and raise the others. Here is the current version of this. require 'sunspot/session_proxy/silent_fail_session_proxy' module Sunspot module SessionProxy class QueueFailureSessionProxy "Solr Exception", :error_message => "Solr Exception: #{ex.message}", :parameters => { :model => klass, :method => method_name } ) if defined?(HoptoadNotifier) klass.delay.index! if method_name.to_s.match('index') klass.delay.remove_from_index! if method_name.to_s.match('remove') else raise ex end end SUPPORTED_METHODS.each do |method| module_eval( ex self.rescued_exception(:#{method}, ex, args.first) end end RUBY end end end end Sunspot.session = Sunspot::SessionProxy::QueueFailureSessionProxy.new(Sunspot.session) Comments: 0 How to install private gems on heroku January 06, 2011 00:22 Scenario: I have to setup a staging app on Heroku. Sounds pretty simple, should take an hour tops, right? Think again. Mix in a gem from a private git repo and it gets messy. If the gem isn’t installed via version but with a commit ref you get even more fun. Setup the app on Heroku as you normally would, then try to deploy. Everything looks good, until it tries to fetch the private gem. Then git push heroku staging:master -----> Heroku receiving push -----> Rails app detected -----> Detected Rails is not set to serve static_assets Installing rails3_serve_static_assets... done -----> Gemfile detected, running Bundler version 1.0.3 Unresolved dependencies detected; Installing... ... Permission denied (publickey). fatal: The remote end hung up unexpectedly Hrm… Poke around the google some and find I’m not the only one. See references to an ~/.ssh/config that looks something like Host heroku.com HostName heroku.com User git ForwardAgent yes IdentitiesOnly yes Sounds reasonable. Nope, no luck. More time with google and it would seem that Heroku doesn’t pass your keys out the other side. Not sure if they have a specific reason for it or it’s just the default sshd_config. Ok, that’s not going to work. Lets try dropping the gem in vendor/cache and see if that helps. Oh, there isn’t an actual gem to cache. Lets grab the one in bundler. Nope that wont work either. Off to build the gem so I can place it in vendor/cache. cd ../my_gem rake build cp pkg/my_gem-0.0.2.gem ../rails_app/vendor/cache cd ../rails_app bundle install WTF!? Oh, it saw one gem in the cache dir, I must want them all in there, right?? No, no I don’t. Ok, well let’s place the gem in the app in a place I can get to it with bundler but it wont randomly trigger some other unwanted behavior. gem install ../my_gem/pkg/my_gem-0.0.2.gem gem unpack my_gem -v 0.0.2 --target vendor/private_gems Ok now I update my Gemfile to look like gem 'my_gem', :path => 'vendor/private_gems/my_gem-0.0.2' So far it seems happy. Though I have seen some really strange issues with it randomly Throwing the Gemfile.lock - Heroku has a read-only filesystem error which would make perfect sense other than the fact that the error came from running heroku rake db:migrate right after a successful push. Comments: 0 New home, new engine December 31, 2010 22:06 If you are reading this the site has moved to Heroku and is now powered by JABE in addition to the info on github, more info on JABE coming soon here. Comments: 0 Snow Leopard, Passenger 3, PassengerPane and Stock Apache October 08, 2010 10:34 I finally decided to start using Passenger and the stock Apache in OS X Snow Leopard. Here are the steps I followed, from memory, so if they are missing anything please let me know. install PassengerPane rvm install ree rvm ree rvm gemset create APP_NAME gem install passenger rvmsudo passenger-install-apache2-module Add an .rvmrc file rvm --rvmrc --create ree@APP_NAME Find the gems info rvm ree@APP_NAME rvm info | grep GEM GEM_HOME: "/Users/mmoen/.rvm/gems/ree-1.8.7-2010.02@APP_NAME" GEM_PATH: "/Users/mmoen/.rvm/gems/ree-1.8.7-2010.02@APP_NAME:/Users/mmoen/.rvm/gems/ree-1.8.7-2010.02@global" add those to the /etc/apache2/passenger_pane_vhosts/APP_NAME.local.conf SetEnv GEM_HOME /Users/mmoen/.rvm/gems/ree-1.8.7-2010.02@showcase SetEnv GEM_PATH /Users/mmoen/.rvm/gems/ree-1.8.7-2010.02@showcase:/Users/mmoen/.rvm/gems/ree-1.8.7-2010.02@global Make sure the envs are setup in /etc/apache2/passenger_pane_vhosts/APP_NAME.local.conf RailsEnv development RackEnv development If you make changes to routing or other places that don’t autoload, you will need to restart the instance touch tmp/restart.txt Known issues: If you are running a Rails 2.x app this way you will have to delete config.ru before starting or restarting the app. Otherwise it messes up Rails.env. And as always, feel free to tell me I’m way off or if you have any input, please share it. [edit] Update .rvmrc creation per Wayne’s suggestion Comments: 0 Ack.tmBundle March 23, 2010 20:56 If you are a Textmate user and you were tired of Find in Project being a dog, so you started using Grep in Project and even it was getting slow. You absolutely owe it to yourself to check out Ack in Project. It is ridiculously fast. Comments: 0 rvm friendly TextMate bundles February 20, 2010 07:54 I forked and modified the Cucumber and RSpec TextMate bundles to setup the rvm environment based on an .rvmrc in your project directory. Cucumber Bundle RSpec Bundle Enjoy. Let me know if you find any quirks. Comments: 0 rvm + gemsets + TextMate == yay! * 2 February 20, 2010 05:13 Ok so in my last post I mentioned I wasn’t able to find a way to automatically use an existing .rvmrc file. I spent some time with it again this afternoon and was able to get it to work. So now if you are using TextMate and you want to run a ruby script that uses your rvm environment all you have to do is edit the commands you use and replace the #! and add a couple lines. The odd thing is this is pretty much exactly what I was trying before, though on a different machine. #!/usr/bin/env bash [[ -f "$HOME/.rvm/scripts/rvm" ]] && . $HOME/.rvm/scripts/rvm [[ -f "$TM_PROJECT_DIRECTORY/.rvmrc" ]] && . $TM_PROJECT_DIRECTORY/.rvmrc And that’s it, you get your rvm config in TextMate. Comments: 0 1 2 3 4 5 Next ? Last ? Powered by JABE a Pixels and Bits project

underpantsgnome.com Whois

Domain Name: UNDERPANTSGNOME.COM
Registry Domain ID: 125933225_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: www.enom.com
Updated Date: 2014-06-30T02:26:46.00Z
Creation Date: 2004-07-29T06:08:00.00Z
Registrar Registration Expiration Date: 2016-07-29T06:08:59.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Reseller: NAMECHEAP.COM
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: WHOISGUARD PROTECTED
Registrant Organization: WHOISGUARD, INC.
Registrant Street: P.O. BOX 0823-03411
Registrant City: PANAMA
Registrant State/Province: PANAMA
Registrant Postal Code: 00000
Registrant Country: PA
Registrant Phone: +507.8365503
Registrant Phone Ext:
Registrant Fax: +51.17057182
Registrant Fax Ext:
Registrant Email: 55B10F0EDFC64D6FA8948C9588919830.PROTECT@WHOISGUARD.COM
Registry Admin ID:
Admin Name: WHOISGUARD PROTECTED
Admin Organization: WHOISGUARD, INC.
Admin Street: P.O. BOX 0823-03411
Admin City: PANAMA
Admin State/Province: PANAMA
Admin Postal Code: 00000
Admin Country: PA
Admin Phone: +507.8365503
Admin Phone Ext:
Admin Fax: +51.17057182
Admin Fax Ext:
Admin Email: 55B10F0EDFC64D6FA8948C9588919830.PROTECT@WHOISGUARD.COM
Registry Tech ID:
Tech Name: WHOISGUARD PROTECTED
Tech Organization: WHOISGUARD, INC.
Tech Street: P.O. BOX 0823-03411
Tech City: PANAMA
Tech State/Province: PANAMA
Tech Postal Code: 00000
Tech Country: PA
Tech Phone: +507.8365503
Tech Phone Ext:
Tech Fax: +51.17057182
Tech Fax Ext:
Tech Email: 55B10F0EDFC64D6FA8948C9588919830.PROTECT@WHOISGUARD.COM
Name Server: NS-1382.AWSDNS-44.ORG
Name Server: NS-1689.AWSDNS-19.CO.UK
Name Server: NS-402.AWSDNS-50.COM
Name Server: NS-534.AWSDNS-02.NET
DNSSEC: unSigned
Registrar Abuse Contact Email: abuse@enom.com
Registrar Abuse Contact Phone: +1.4252982646
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
Last update of WHOIS database: 2014-06-30T02:26:46.00Z
The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do not guarantee its accuracy. By submitting a
whois query, you agree that you will use this data only for lawful
purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.
We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/200