Skip to content
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.

Deploy directions: Actually deploying brick isn't covered #34

Closed
atc0005 opened this issue May 24, 2020 · 0 comments · Fixed by #36
Closed

Deploy directions: Actually deploying brick isn't covered #34

atc0005 opened this issue May 24, 2020 · 0 comments · Fixed by #36
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation
Milestone

Comments

@atc0005
Copy link
Owner

atc0005 commented May 24, 2020

How embarrassing. The current doc covers other aspects of the deployment process, but completely skips copying the previously built binary to the target /usr/local/sbin/ directory.

@atc0005 atc0005 added bug Something isn't working documentation Improvements or additions to documentation labels May 24, 2020
@atc0005 atc0005 added this to the v0.1.1 milestone May 24, 2020
@atc0005 atc0005 self-assigned this May 24, 2020
atc0005 added a commit that referenced this issue May 24, 2020
Add coverage for identifying target OS architecture,
matching brick binary name/pattern and setting
executable bit/permissions on fully-qualified
path to binary after deployment.

refs GH-34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant