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

Add a section for the bctl upgrade procedure #26

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

moshiurH
Copy link
Contributor

Making explicit user documentation for how to upgrade bctl binary version.

@@ -42,6 +42,9 @@ Next you can install the binary on your system using the following `tar` command
tar xzf bctl_<os>_<arch>.tar.gz -C /usr/local/bin/
```

### Upgrading the bctl binary version
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should be able to just rerun the script and it will override the existing install. Did you run into an issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for clarifying how the installer script works. I haven't tested or tried that out. I wasn't sure that was the case with the installer script. I was hoping we could make it clear to the end user in our documentation that inplace upgrading the bctl binary was possible (without needing to uninstall boundless first).

Should we perhaps mention the in-place upgrading aspect in our installer portion of this documentation? "You may install or upgrade to the latest Boundless with the following script."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm actually debating if it makes sense to start breaking this page into separate sections. The page title is Install but it now contains much more than just the install methods.

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

Successfully merging this pull request may close these issues.

2 participants