Public tooling
curl -fsSL https://raw.githubusercontent.com/amplify-edge/booty/master/scripts/install.sh | bash
Invoke-WebRequest -useb https://raw.githubusercontent.com/amplify-edge/booty/master/scripts/install.ps1 | Invoke-Expression
run
booty completion
or to write it to file (*nix / Darwin for example):
booty completion > compl.bash
it will generate your shell completion, refer to your shell documentation on how best to install it and source it on your shell.
# clone your forked repro.
# for this example the user is "johnsmith", and the repro is "shared".
git clone git@github.com-johnsmith:johnsmith/shared
cd shared
# setup git config to have remote section pointing to upstream repository.
booty gw reg share
booty gw fset amplify-edge
# make any change.
rm ./README.md
# add and commit.
booty gw add-all
booty gw commit 'blah'
# check if there were any changes on the shared remote upstream repo.
booty gw fup
# push from your local origin to your remote origin
booty gw push
# open the github repo and create a Push Request (PR) back to upstream as per normal.
open https://github.com/johnsmith/shared
- Clone this repository
- Run
make all
- Copy the binary in
bin
directory to yourPATH
- Run
booty
To add a component, implement the Component
interface in here
This program installs config under:
- Linux:
$HOME/.local/booty/etc
- Mac:
$HOME/Library/Application\ Support/booty/etc
- Windows:
C:\\ProgramData\booty\etc
The file config.reference.json
is provided as a reference should you want to change the program behaviour.
- Download 3rd party binaries and libraries our project needs
- Install said binaries
- Also install service, managed by OS' service supervisor, preferably as user service on dev and as system-wide service running under unprivileged user on production.
- Ability to run each service on the foreground like pingcap's
tiup playground
- Ability to self update and check for updates for third party binaries
- Manage configs and backups for
maintemplatev2