Go to File -> Settings -> Tools -> Terminal and change Shell path based on the the installed git version.
for 64bit:
"C:\Program Files\Git\bin\sh.exe" --login -i
for 32bit:
"C:\Program Files (x86)\Git\bin\sh.exe" --login -i
Go to File -> Settings -> Tools -> Terminal and change Shell path based on the the installed git version.
for 64bit:
"C:\Program Files\Git\bin\sh.exe" --login -i
for 32bit:
"C:\Program Files (x86)\Git\bin\sh.exe" --login -i
CMDER_ROOT
to your root Cmder folder (in my case C:\Program Files (x86)\Cmder
). It seems to be important that this does not have quotes around it because they mess with concatenation in the init script."cmd" /k ""%CMDER_ROOT%\vendor\init.bat""
as the Shell path. The double-double-quotes are intentional, as they counteract the missing double quotes in the environment variable.sudo apt-get update | |
sudo apt-get install nginx | |
# default website |
This tutorial was created by Shopify for internal purposes. We've created a public version of it since we think it's useful to anyone creating a GraphQL API.
It's based on lessons learned from creating and evolving production schemas at Shopify over almost 3 years. The tutorial has evolved and will continue to change in the future so nothing is set in stone.
var FtpDeploy = require('ftp-deploy'); | |
var ftpDeploy = new FtpDeploy(); | |
var config = { | |
username: process.env.FTPUSERNAME, | |
password: process.env.FTPPASS, | |
host: process.env.FTPHOST, | |
port: 21, | |
localRoot: __dirname + "/../dist/", | |
remoteRoot: "/", |
I work as a full-stack developer at work. We are a Windows & Azure shop, so we are using Windows as our development platform, hence this customization.
For my console needs, I am using Cmder which is based on ConEmu with PowerShell as my shell of choice.
Yes, yes, I know nowadays you can use the Linux subsystem on Windows 10 which allow you to run Ubuntu on Windows. If you are looking for customization of the Ubuntu bash shell, check out this article by Scott Hanselman.
Export the private key
openssl pkcs12 -in certificate.pfx -out certificate.key -nocerts -nodes
Take out the encryption from the private key
openssl rsa -in certificate.key -out certificate_new.key
source: http://www.markbrilman.nl/2011/08/howto-convert-a-pfx-to-a-seperate-key-crt-file/ | |
`openssl pkcs12 -in [yourfile.pfx] -nocerts -out [keyfile-encrypted.key]` | |
What this command does is extract the private key from the .pfx file. Once entered you need to type in the importpassword of the .pfx file. This is the password that you used to protect your keypair when you created your .pfx file. If you cannot remember it anymore you can just throw your .pfx file away, cause you won’t be able to import it again, anywhere!. Once you entered the import password OpenSSL requests you to type in another password, twice!. This new password will protect your .key file. | |
Now let’s extract the certificate: | |
`openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out [certificate.crt]` |