Unable to use 'silk skel' on a fresh installation

Martin Melin avatarMartin Melin created an issue

At the moment, new users can't get up and running with silk-deployment without applying patches from two open pull requests, one on silk-deployment and one on silk-config.

Expected results:

$ silk skel sitename should create silk skeleton directory, as described in README.

Actual results:

silk dies with an opaque AttributeError, because there is no site.yaml file.

When this is fixed by https://bitbucket.org/btubbs/silk-config/pull-request/2/dont-assume-get_site_root-finds-a-site there is another issue.

silk skel dies because install_skel needs a site name as an argument, but it isn't being passed on by cmd_dispatcher.

Fixed by https://bitbucket.org/btubbs/silk-deployment/pull-request/1/update-to-pass-args-to-silk-skel-site

Steps to reproduce:

  1. Create a new virtual environment with --no-site-packages
  2. $ pip install silk-deployment
  3. $ silk skel test

Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.