Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Management #24

Open
mastersign opened this issue Feb 24, 2016 · 4 comments
Open

Project Management #24

mastersign opened this issue Feb 24, 2016 · 4 comments

Comments

@mastersign
Copy link
Collaborator

mastersign commented Feb 24, 2016

  • Project index with Git remotes
    • Project groups
    • Project activation (git clone) and deactivation (wipe if git status is clean)
    • Automatic dependency download (lein deps, npm install, bower install, ...)
  • Improved dashboard for projects
    • with project bound actions (activate, deactivate, editor, shell, tasks)
    • create new project with different kinds of scaffolding (lein new, npm init, yo xyz, ...)
@mastersign
Copy link
Collaborator Author

mastersign commented May 7, 2016

Internal PlugIn architecture via aspect-oriented interfaces.

Possible aspects:

  • creation/initialization
  • dependency download
  • build
  • watch
  • edit
  • clean
  • release
  • publish

@mastersign mastersign mentioned this issue Dec 15, 2016
33 tasks
@mastersign
Copy link
Collaborator Author

Commands from CLI:
project, prj, p

  • ... new, n <tool> [args*]
  • ... backup, a <project name>
  • ... dependencies, deps, d <project name>
  • ... build, b <project name>
  • ... run, r <project name>
  • ... test, t <project name>
  • ... delete, x <project name>
  • ... custom-task, c <project name> <task name>

@mastersign
Copy link
Collaborator Author

Plug-in interface need to be worked out to define the possible user tasks at the Dashboard and the CLI.

@mastersign mastersign added this to the v1.0 Feature Complete milestone Jan 2, 2017
@mastersign mastersign self-assigned this Feb 15, 2017
@mastersign
Copy link
Collaborator Author

Most importantly the checkout of existing projects should be imlemented, because it generates the biggest benefit for Bench as a prepared dev-environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant