I used Homebrew Cask to install ngrok. The installation went fine. I'm trying to edit ngrok's config.yml file. I can't find it on my mac.
It appears that ngrok lives here:
/usr/local/Caskroom/ngrok/2.1.3,4VmDzA7iaHb
and there is a sub-directory in the above directory, but I can't open that directory. Any ideas on where I can find ngrok's config.yml file greatly appreciated.
A default config.yml doesn’t get installed. Instead ngrok checks $HOME/.ngrok2/ngrok.yml.
So on MacOS, for user foo, then ngrok looks for the file in Users/foo/.ngrok2/ngrok.yml.
Related
I am running out of space on my laptop, and I was wondering if it would be possible to change the default directory of installing casks on an external hard drive so that I can use the internal hard drive just for the OS and important files.
I guess you can overwrite the environment variable HOMEBREW_CASK_OPTS or you can use the --appdir=/my/path option. You can get more information with the command man brew-cask and there is a nice markdown documentation in the cask repository. Otherwise the executables can be found in the Applications folder.
EDIT:
Sometimes it helps to run a cleanup to delete the old versions:
brew cleanup
brew cask cleanup
I followed the Hyperledger fabric documentation to install and configure it in Windows 10. However when I run the command - "./byfn.sh -m generate" for first-network sample application, I get the following error,
I have gone thru all StackOverflow questions regarding this and made sure following steps are done,
Have set the $PATH variable correctly to include bin folder.
Have downloaded the platform-specific binary and my bin folder looks like this,
I have doubts about following steps,
I have installed Docker for Windows and was able to verify the docker installation by running hello-world image in Docker. However, I have not shared any of my local drives in Docker. Not sure whether this is the cause of this error.
Please note that this is my first question in StackOverflow. Forgive me for any mistakes/redundancies. Any help is greatly appreciated.
I'd suggest making sure that you run the script to download / install the binaries and images from within the fabric-samples directory.
The $Path is exported every time you run the byfn.sh script, confirm that the path configuration in the byfn.sh is correct and points to your correct bin location
# prepending $PWD/../bin to PATH to ensure we are picking up the correct binaries
# this may be commented out to resolve installed version of tools if desired
export PATH=${PWD}/../../bin:${PWD}:$PATH
export FABRIC_CFG_PATH=${PWD}
I'm currently evaluating RubyMine 7.0.4 on Mac OS X 10.8.5, and I'm trying to get my Ruby on Rails project up and running in the editor but after I try to bundle, I get "Error Copying Gems". Locally I use rbenv but this project uses Vagrant with Ruby 2.1.
I've gone into RubyMine Preferences -> Languages and Frameworks -> Ruby SDK and Gems and set up a "Remote Interpreter" which looks like it is correctly pulling in my Vagrant / SSH information.
After I click OK, it looks like it correctly pulls down the gems, and copies them to the vendor/bundle folder, but then the IDE pops up an error message saying :
"Error Copying Gems - Unknown message with code 'Could not determine the type of file sftp://127.0.0.0.1:2222/......'"
or sometimes I'll get a more detailed error:
"Error Copying Gems - Could not copy sftp://127.0.0.1:2222/usr/bin/sudoedit to file://Users/my.username/Library/Caches/RubyMine70/ruby_stubs/....."
It feels like it is trying to copy them to a local cache folder on my Mac but failing for some reason.
I was facing a similar albeit different problem, maybe you are making the same mistake:
When setting up RubyMine to work with Vagrant, I am assuming you are adding a remote interpreter using the Vagrant dialogue. There it asks you to input the path to ruby executible. This is misleading, what you need is the path to where the gems are installed.
I'm also assuming you using RVM on your VM, as you indicate that you are not using rbenv on your VM.
I solved this by following the symlink steps found http://randycoulman.com/blog/2013/11/05/rubymine-and-vagrant/
Basically, RubyMine isn't trying to save things on your host machine. Its trying to save things to that particular path on your guest OS. I worked around this issue by creating the /Users/user_name/... directory on my guest OS, and then symlinking the directory that has the projects to /vagrant (Again, on the guest OS)
I have trouble connecting to sites with ssl, i.e. https. It can successfully download artifacts from the internet if the url begins with http.
bower install will download dependencies via https. Is there anyway make it download via http?
I had troubles with this too, and I couldn't find an elegant way to fix it. My workaround was:
Go to your global npm folder and find the "bower" folder (on Windows 7 that is "C:\Users\\AppData\Roaming\npm\node_modules").
In that folder, search the default.js file placed in node_modules\bower-config\lib\util\default.js
Inside that file you will find a "var defaults". Replace the "registry" url property from "https" to "http".
Yes, I know. This shouldn't be done like this, but at least help me to bypass the connection error.
Hope that helps!
You can change the registry used by Bower in the .bowerrc file. The default registry is: https://bower.herokuapp.com and is defined in node_modules/bower-config/lib/util/default.js (as described by Jean Manuel Arias in his answer).
To override for your project, add a value for the registry setting in .bowerrc. An example file might be:
{
"directory": "<YOUR LIBRARY INSTALL DIRECTORY>",
"registry":"http://bower.herokuapp.com"
}
In the above example, the default https registry is being overridden with the http version. A full list of the available .bowerrc settings can be found at: Bower Spec.
You can do a global override for the current user by creating a %USERPROFILE%\.bowerrc file (for windows, in Linux it is: ~/.bowerrc). Bower follows a similar search path when applying settings to NPM (see npmrc settings). This is probably a better route as it avoids cluttering your project with local settings.
I've been searching for a way to install Image Magick on my Mountain Lion setup (where I use MAMP Pro). I did find this article, but it isn't specific to ML. Also found a couple other similar questions here on SO but they were too specific I think. Doesn't help that I'm not great at this sort of thing. Can anyone point me to a good resource?
As was pointed out in erwinheiser's comment, MAMP 3 now comes with imagemagick pre-installed. I checked MAMP's User Guide (PDF) and found this:
The ImageMagick PHP module is included by default, but you must enable it inside the php.ini template file. Remove the ‘;’ from the following line.
;extension=imagick.so
And how do you find and change the (right) php.ini file for MAMP Pro?
From MAMP's menu choose File › Edit Template › PHP › [the latest version]
or use the keyboard shortcut: ⌘4
Make the edit. (Imagick was was at line 542 in mine.)
Save and close the file.
MAMP asks if you want to restart the servers now, choose yes.
And you're done!
Make sure you check out Joel Farris' answer if you're using an up-to-date version of MAMP
I finally managed to get it installed properly using Homebrew and the instructions here: http://egoco.de/post/23167969231/installing-imagemagick-for-php-and-mamp
I did have to run brew doctor and brew link a couple of times to fix dependencies (and change permissions on a file or two), and use
brew install php54-imagick
rather than the one mentioned at the url.
The extension he mentions at the end (the bit you have to paste in your different ini files) is:
[imagick]
extension="/usr/local/Cellar/php54-imagick/3.1.0RC2/imagick.so"
Hope it helps!
MAMP comes with Imagick installed. I have MAMP v3.2.1 (not MAMP Pro) running on OS X 10.10.3 (Yosemite).
I enabled imagick by editing php.ini file which comes with MAMP.
php.ini file is available on the following path:
/Applications/MAMP/bin/php/php5.6.7/conf/php.ini
Replace 5.6.7 with your php version number.
php.ini file will contain the following line:
;extension=imagick.so
Change that line to:
extension=imagick.so
Now restart the MAMP servers and you are good to go.
We made a Mac installer package here— http://www.cactuslab.com/imagemagick/