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

Ability to control bash / bat file name other than via normalizedName #217

Closed
eranation opened this issue Apr 4, 2014 · 4 comments
Closed

Comments

@eranation
Copy link

My normalizedName for the project doesn't fit as a good bat / bash file name for me.
e.g. the normalizedName is setups-foo (due to naming conventions) but I want the bat / bash file name to be foo.bat / foo

however all tasks use normalizedName as the bat / bash file name.

I think it will be nice to have this configurable in some way

@muuki88
Copy link
Contributor

muuki88 commented Apr 4, 2014

Yep, this would be a nice addition. Pull request welcome :)

@muuki88
Copy link
Contributor

muuki88 commented Apr 16, 2014

Yeah. That would be awesome @kardapoltsev . Take a look at #188 where are some additional information for scoping these settings.

@kardapoltsev
Copy link
Member

I'll wait until 188 will be fixed and then try to implement this feature. Really I need to install one application twice on one server (for testing and production) with different settings. So I don't need different bash script name but different application name.

@muuki88 muuki88 added this to the 0.8.0 - windows services milestone Jul 24, 2014
@muuki88
Copy link
Contributor

muuki88 commented Jul 24, 2014

This will be my next task after since #250 has been merged now.

@muuki88 muuki88 self-assigned this Jul 24, 2014
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

3 participants