Skip to content

Instantly share code, notes, and snippets.

View mur-wtag's full-sized avatar
🏠
Working from home

M Mahabubur Rhaman (Rony) mur-wtag

🏠
Working from home
View GitHub Profile
@armandfardeau
armandfardeau / How to use
Created July 13, 2018 12:33
Register sidekiq as a service
which bundle
# /home/adminosp/.rbenv/shims/bundle
sudo nano /etc/systemd/system/sidekiq.service
sudo systemctl start sidekiq.service
sudo systemctl enable sidekiq.service
sudo systemctl status sidekiq.service
sudo service sidekiq status
# sudo systemctl daemon-reload
@fernandoaleman
fernandoaleman / fix-libv8-mac.txt
Created May 5, 2016 15:14
Fixing libv8 and therubyracer on Mac
brew tap homebrew/versions
brew install v8-315
gem install libv8 -v '3.16.14.13' -- --with-system-v8
gem install therubyracer -- --with-v8-dir=/usr/local/opt/v8-315
bundle install
@DanHerbert
DanHerbert / fix-homebrew-npm.md
Last active January 14, 2026 12:03
Instructions on how to fix npm if you've installed Node through Homebrew on Mac OS X or Linuxbrew

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.