masonite: Init install fails - [CommandNotFound] Command "key" is not defined.

Trying the initial test setup as displayed on the wiki I get the following;

PY3.6, $ craft -V; Craft Version: 2.0.2

patrick@patrick-P506:~/tmp$ craft new project
Crafting Application ...

Application Created Successfully!

Now just cd into your project and run

    $ craft install

to install the project dependencies.

Create Something Amazing!
patrick@patrick-P506:~/tmp$ cd project/
patrick@patrick-P506:~/tmp/project$ craft install

                                 
  [CommandNotFound]              
  Command "key" is not defined.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 42 (30 by maintainers)

Links to this issue

Masonite 2.0 Released - The Modern Python Web Framework!

Most upvoted comments

yeah so bizarre lol … So everything works perfectly except you keep on getting that key command not found error when you type craft install. I’ll try testing this on Ubuntu. Could be an issue which how ubuntu does subprocess calls. What should happen is that it should pip install and then masonite will be installed so it should have the key command now and then it will run the key command but apparently it’s not getting that. especially weird that you said Masonite is installing

josephmancuso on Jun 20, 2018

Whoops, @josephmancuso and @nmalacarne got it. Sorry to double-suggest it, Github didn’t update the thread for me.

I like your idea to add a --user flag to craft install

aisola on Jun 19, 2018

maybe do something like craft install --user?

josephmancuso on Jun 19, 2018

The latest version of craft shoulld be 2.0.3.

try running:

$ pip3 install --upgrade masonite-cli

josephmancuso on Jun 16, 2018