`mkcert` command not found, after installing ddev - ddev

mkcert doesn't seem to be installed (or maybe not in the right path) on Ubuntu
ddev version
DDEV-Local version v1.8.0
commit v1.8.0
db drud/ddev-dbserver:v1.8.0-10.2
dba drud/phpmyadmin:v1.8.0
ddev-ssh-agent drud/ddev-ssh-agent:v1.8.0
docker 18.09.5
docker-compose 1.21.2
domain ddev.local
os linux
router drud/ddev-router:v1.8.0
web drud/ddev-webserver:v1.8.0
On Ubuntu 18
mkcert -install
zsh: command not found: mkcert

If you use( a package manager homebrew on Linux or macOS, or use the ddev Windows installer, or use Chocolatey on WIndows) then mkcert gets installed for you. In all other cases you have to install it yourself, see https://github.com/FiloSottile/mkcert
Note that mkcert is optional. It's how we get the browser (and curl, etc) to trust the local development site using https. But of course, we can just use all the various means we've always used to ignore untrusted connections. But mkcert makes it really nice!
Note that on Linux mkcert -install may give you some extra instructions that you'll need to do for everything to work right, see docs.

For me, I had to use chocolaty to get this in. Everything else kept failing..
choco install mkcert

Related

nvm install --lts keeps failing no matter what I try.. I already have v12 working properly as default under nvm

On a Ubuntu 20.04 server - I've also tried removing and reinstalling curl as per This SO answer.
This
is also open.. So no idea how to install Node v14 LTS under nvm now..
The readme on the github for NVM says to use the provided install script for Linux installs. This can be achieved with curl or wget:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
I recommend that you click the link and read, as their is quite a bit of related info there.
I was interested and just tested it out in a clean docker container (ubuntu:20.04) (as I dont use node that often), and it looked pretty straight forward:
apt-get update -y
apt-get install -y curl
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
source ~/.bashrc
nvm version
# none
nvm install --lts --default
nvm version
# v14.17.0
If it not that, then I would also assume, that the issue is related to your general environment, like network inspection, proxy access or else.
As it is visible from the logs, the checksum process keeps failing in a repeated manner. And there have been issues highlighting that some ISO images can show issue with hashing process due to Windows 10 components. , which implicitly effects the checksum process under a guest environment on VirtualBox.
You can complete the steps provided by VirtualBox team there to resolve this issue, as pointed out on Virtual Box's forum:
it's Hyper-V that is causing the checksum problem you posted about, not the version of Virtualbox.

apt in Linux Subsystem for Windows 10 is failing with 404 Not Found

OK, so this is my first SO question so I'm gonna try my best to lay this out.
I have a Windows 10 laptop on which I am trying to install gcc. I have in the past tried alternatives such as netbeans, cygwin and various emulators and virtual machines all to no avail.
What has been working so far is that I enabled the 'new' windows developer mode which allowed me to download a Linux bash shell from the windows store. It works for all the regular Linux commands, but doesn't have gcc installed.
When I type in gcc (or gcc --version) in the shell, it prints the following line:
The program 'gcc' is currently not installed. You can install it by typing:
sudo apt install gcc
Which I tried, it then ran through a bunch of installer stuff but consistently seemed to run into errors such as the following:
Err:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdpkg- >perl all 1.18.4ubuntu1.2
404 Not Found [IP: INSERT IP ADDRESS HERE ]
where the ip address is different on each error line.
It ultimately fails with the following line:
Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I have tried but again I get the same kinds of errors as above.
I would really like to get gcc working in the Windows/Linux shell as it is working great for everything else, and I'm trying to keep the number of programs on my computer to a minimum.
Does anyone know why this isn't working, or how (if possible) I can make it work?
P.S I do need it to be gcc because of school reasons
For what it's worth: I landed on this SO topic after having a similar issue.
What fixed it for me was to run
sudo apt-get update
sudo apt-get upgrade
I guess the repo URLs were too old, even though my Ubuntu was in a recent version.
I just ran into the same thing attempting to install python-pip. According to this article, this happens when you have the Windows 10 Anniversary Update (older) instead of the Creators update (newer). The solution is to either uninstall and re-install Ubuntu, or upgrade it (from 14.04 to 16.04). I found the upgrade to be simple and painless:
sudo do-release-upgrade
To check what you have, before and after via:
lsb_release -a
I had the same problem. Pinging the IP resulted in no response and visiting the website returned a 404.
I found a ppa with most current GCC and registered the PPA and was able to successfully install GCC with it; ppa website. I used GCC to build some software I wanted that was not found with apt-get.
From their page:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
Try to run Ubuntu application in Windows with an option "Run as Administrator".

Can openssh be installed on MSYS?

I'm using MSYS in windows 7 and now i need it to provide ssh server service. can openssh be installed in msys like it is in cygwin?
i can find ssh in /msys/bin, and it can be used as ssh client. but no server seems to be installed. how can i install one? i googled a lot but almost every theads leads to openssh in cygwin, that does not apply to my situation.
i compared cygwin and msys and decide to use msys. We need to run some applications both built and supposed to be ran in windows.
what i've tried:
mingw-get install mysys-openssh
test#WIN-L3L622JBT6G ~
$ mingw-get install msys-openssh
install: openssh-5.4p1-1-msys-1.0.13-bin.tar.lzm
installing openssh-5.4p1-1-msys-1.0.13-bin.tar.
install: openssh-5.4p1-1-msys-1.0.13-doc.tar.lzm
installing openssh-5.4p1-1-msys-1.0.13-doc.tar.
install: openssh-5.4p1-1-msys-1.0.13-lic.tar.lzm
installing openssh-5.4p1-1-msys-1.0.13-lic.tar.
test#WIN-L3L622JBT6G ~
$ openssh
sh: openssh: command not found
the package seems to be installed but i don't know how to find the service. do i need to link it or modify the profile?
The answer would be "NO".
Msys provide ssh client but not ssh server, as it's document indicates.
And Openssh cannot be installed on windows without cygwin. you can install a full cygwin and install openssh in cygwin. It's also feasible to only install partial cygwin.
Msys is outdated. Use Msys2, which does support sshd: https://www.booleanworld.com/get-unix-linux-environment-windows-msys2/

Getting the Error "Required option '-K, --private-key KEY' missing (-h for usage)"

I am using an Ubuntu 12.04. I have downloaded the EC2 CLI tools from the Amazon website. The following are the steps that I have done..
Unzipped the file and put it in a directory.
Set the Java class path properly (My Tomcat is working).
Set the EC2 home path, after that set the EC2 Home and bin path in bashrc
Set the access and secret key in bashrc.
When I am trying to trying to start an instance or do anything for that matter from the terminal, I am getting the error
Required option '-K, --private-key KEY' missing (-h for usage)
Could someone please help me with this?
Posting this so it might be helpful for others. The problem was happening because when I installed Ubuntu I had installed the ec2-tools using the apt-get from terminal.
This version of ec2 which Ubuntu has is an outdated version (it was last updated in 2011).
When I found this out, I removed it. And reconfigured the path to the current version of ec2 cli tools I had downloaded and it worked!!! :)
The way to install newer versions of the ec2-api-tools, as suggested by https://help.ubuntu.com/community/EC2StartersGuide, is to simply add the aws-tools PPA:
sudo apt-add-repository ppa:awstools-dev/awstools
sudo apt-get upgrade
and then a simple apt-get install ec2-api-tools will install the correct version. :)

Having Trouble Using "brew link" to switch between PostgreSQLs

I want to run a Rails app on Heroku so I installed PostgreSQL on my Snow Leopard machine using Homebrew. Currently, brew installs 9.1.2 into /usr/local/Cellar/postgresql. After some research, I discovered that the free, shared version of Heroku requires 8.3.x. While homebrew-alt doesn't have 8.3, it does have 8.4 so I downloaded it instead and it installed into /usr/local/Cellar/postgresql8. I then confirmed that I am able to create and run databases on each version. Thinking that I could use "brew [link | unlink] to switch back and forth, I ran "brew unlink postgresql8" and then "brew link postgresql". However, running the latter command results in this error:
Linking /usr/local/Cellar/postgresql/9.1.2...
Error: Cannot link postgresql
Another version is already linked: /usr/local/Cellar/postgresql/9.1.2
Is there any way to do this (switch back and forth) or am I misunderstanding how brew link/unlink is supposed to be used?
By the way, "brew list" shows "postgresql" and "postgresql8" so I don't think it's the case that I should say "brew link postgresql9".
Thanks.
Use brew switch, which is an extension shipped with Homebrew. In your case, you could use 8.4 by running
$ brew switch postgresql 8.4
Thanks, mipadi! That did the trick. There was only one additional thing that I needed to do. The 'brew switch' command assumes all versions of postgresql are installed in /usr/local/Cellar/postgresql. That was not the case with version 8.4.8 as it was installed in /usr/local/Cellar/postgresql8. Consequently I had to create a symbolic link to point to this older version:
cd /usr/local/Cellar/postgresql
ln -s ../postgresql8/8.4.8 8.4.8
Naturally, it also makes sense to keep your database clusters in separate directories:
/usr/local/var/postgres/8.4.8
/usr/local/var/postgres/9.1.2

Resources