All the commands disappeared in 2.1.0

[jeremyvaught]

Laravel Valet 2.1.0

Usage:
  command [options] [arguments]

Options:
  -h, --help            Display this help message
  -q, --quiet           Do not output any message
  -V, --version         Display this application version
      --ansi            Force ANSI output
      --no-ansi         Disable ANSI output
  -n, --no-interaction  Do not ask any interactive question
  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Available commands:
  help     Displays help for a command
  install  Install the Valet services
  list     Lists commands```

[drbyte]

Hmmm ... here's the output I get:

valet list
Laravel Valet 2.1.0

Usage:
  command [options] [arguments]

Options:
  -h, --help            Display this help message
  -q, --quiet           Do not output any message
  -V, --version         Display this application version
      --ansi            Force ANSI output
      --no-ansi         Disable ANSI output
  -n, --no-interaction  Do not ask any interactive question
  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Available commands:
  fetch-share-url    Get the URL to the current Ngrok tunnel
  forget             Remove the current working (or specified) directory from Valet's list of paths
  help               Displays help for a command
  install            Install the Valet services
  link               Link the current working directory to Valet
  links              Display all of the registered Valet links
  list               Lists commands
  on-latest-version  Determine if this is the latest version of Valet
  open               Open the site for the current (or specified) directory in your browser
  park               Register the current working (or specified) directory with Valet
  paths              Get all of the paths registered with Valet
  restart            Restart the Valet services
  secure             Secure the given domain with a trusted TLS certificate
  share              Generate a publicly accessible URL for your project
  start              Start the Valet services
  stop               Stop the Valet services
  tld                [domain] Get or set the TLD used for Valet sites.
  trust              Add sudoers files for Brew and Valet to make Valet commands run without passwords
  uninstall          Uninstall the Valet services
  unlink             Remove the specified Valet link
  unsecure           Stop serving the given domain over HTTPS and remove the trusted TLS certificate
  which              Determine which Valet driver serves the current working directory
 make
  make:db            Create a new database

[mattstauffer]

Quick fix: run valet install.

I think this is happening because you have a ~/.valet directory (from your old version) instead of a ~/.config.valet version.

[drbyte]

It does display differently if you haven't installed it, since most commands are irrelevant if you haven't run valet install

[mattstauffer]

@drbyte I'm running out right now, but I think the fix might be to add a check in valet.php where it checks for VALET_HOME_PATH... if the result there is false, it should check for ~/.valet, and if that exists, it should run the upgrade process from the ~/.valet folder to the ~/.config./valet folder maybe

[mattstauffer]

@drbyte yah, the problem is if you installed a while ago and then upgraded, you are going to see no commands until you install again.

[drbyte]

Agreed.

[drbyte]

valet/cli/valet.php

Line 57 in b76bb0d

if (is_dir(VALET_HOME_PATH)) {

[jeremyvaught]

valet install did it. Not sure why I didn't just try that, I was looking past it for whatever reason.

I think because previously if there is a Valet issue, the answer was always to delete it from vendor and composer global update. Works every time... until this time it didn't.

Thanks everyone!

[mattstauffer]

I'm gonna keep this open because I'd like us to fix it so people don't have to run install after they upgrade if it's possible. Thanks Jeremy!

[jeremyvaught]

copy that!! Welcome!

[ctf0]

@mattstauffer cant we have a cli cmnd to show the path to the valet folder instead of having the user going in circles for hours trying to figure out why the f*ck the ~/.valet does no longer exist ?

[mattstauffer]

@ctf0 I don't really understand your question. Is it related to this issue above? If not, please open a new issue. Thanks!

[ctf0]

#645