Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

kpm pack should create .sh files for each entrypoint #327

Closed
davidfowl opened this issue Jun 12, 2014 · 7 comments
Closed

kpm pack should create .sh files for each entrypoint #327

davidfowl opened this issue Jun 12, 2014 · 7 comments
Assignees
Milestone

Comments

@davidfowl
Copy link
Member

We create cmd files but no sh files

@davidfowl davidfowl added this to the CTP2 milestone Jun 12, 2014
@borgdylan
Copy link

Is this being worked on?

@graemechristie
Copy link
Contributor

My wife has just had a baby, but I should have some time in a week or so. If no one else has put anything forward by then, I'll have a look at this.

@davidfowl
Copy link
Member Author

@graemechristie Congrats!

@davidfowl davidfowl added this to the 1.0.0-beta1 milestone Oct 2, 2014
@davidfowl
Copy link
Member Author

@ChengTian can you look at this since you're working on #272

@ChengTian
Copy link
Contributor

Adding more details for this issue:

Today, when we kpm pack a project, the root of output contains batch files used to run the pack application.

For example, if we have run and web commands (i.e. entrypoints) defined in project.json of the project being packed, the packed output will contain run.cmd and web.cmd. Users of packed app can simply run a batch file to start the app with a specific entrypoint.

We want the same thing on OSX/*nix. So kpm pack should generate bash scripts (run.sh and web.sh in example above), too.

@glennc glennc modified the milestones: 1.0.0-beta2, 1.0.0-beta1 Oct 21, 2014
@graemechristie
Copy link
Contributor

@ChengTian Is this still being worked on ?

@davidfowl
Copy link
Member Author

@graemechristie #788

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

No branches or pull requests

5 participants