-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add more parameters to the launcher script #1
Comments
I debated about this. I figured people would take the launcher script, then modify it to suit their purposes. For example, at the top of the launcher script, you can change the
Then, the launched image will use port 80 instead of 8080. I could certainly add switches and options too, I just didn't want to over-complicate the launcher script and make it harder to read for people who aren't used to shell scripting so much. Curious about your thoughts! |
Yes both solutions sounds right, just for me as a developer I think that more options is more customization ;). And by the way for people not used to shell scripting if they have to open it to customize, not sure that sounds great for them... ;) |
In this latest release, I've enhanced the launcher script, and included details on the main documentation page. There are probably many more customizations, but is this a good start?
|
@garywiz sounds like a great start, wiil try it and come back to you if I have some feedback or ideas. |
Hello,
First thanks for this useful image!
It could be great to add some more parameters to the launcher script, especially a
-p
to allow use of a custom port like docker does, but maybe also some others I don't think of at this time...What do you think?
The text was updated successfully, but these errors were encountered: