[FeatureRequest] Add non alias versions of the run.sh commands if possible. #75

New issue

Closed

opened 2019-06-15 18:27:53 +02:00 by Leopere · 3 comments

Leopere commented

2019-06-15 18:27:53 +02:00

(Migrated from github.com)

https://github.com/lbryio/lbry-docker/tree/master/contrib contains a README that relies on a run.sh if we could have the vanilla commands somewhere available perhaps at the bottom or something it could be useful then just refer to the vanilla command guide reference next to the commands.

EnigmaCurry commented

2019-06-15 18:59:58 +02:00

(Migrated from github.com)

You can use run.sh without the alias, you just need to specify the full path to it.

Do you mean though that you would like a reference for the kubectl and helm commands that run.sh utilizes?

You can use run.sh without the alias, you just need to specify the full path to it. Do you mean though that you would like a reference for the kubectl and helm commands that run.sh utilizes?

Leopere commented

2019-06-15 20:58:13 +02:00

(Migrated from github.com)

would like a reference for the kubectl and helm commands that run.sh utilizes?
Just want to kind of assume that in some cases we're teaching someone how to functionally do this from the ground up so that adoption can have a lower barrier to entry.

> would like a reference for the kubectl and helm commands that run.sh utilizes? Just want to kind of assume that in some cases we're teaching someone how to functionally do this from the ground up so that adoption can have a lower barrier to entry.

EnigmaCurry commented

2019-06-15 21:01:31 +02:00

(Migrated from github.com)

I agree. It may make sense to make ancillary .md files to break this up a bit. Then I could add additional info that is not necessarily pertinent to the regular install.

Also, this is why the run.sh exe function exists. It logs every raw command to the screen before running it, so it is fully transparent what is going on.

I agree. It may make sense to make ancillary .md files to break this up a bit. Then I could add additional info that is not necessarily pertinent to the regular install. Also, this is why the run.sh `exe` function exists. It logs every raw command to the screen before running it, so it is fully transparent what is going on.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-docker#75

No description provided.