| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
| NETWORK ID | NAME | DRIVER | SCOPE |
|---|---|---|---|
| ############ | bridge | bridge | local |
| ############ | host | host | local |
| ############ | none | null | local |
You CANNOT move scripts between directories (if you do, learn to debug).
/voloume1
└── docker_assistant
├── custom_data - misc files used in a container setup
├── scripts - re-usable code base (bash scripts)
└── templates - deployment container and scripts
/voloume1
└── docker_assistant
├── dev not a deploy directory, this is where we try things out, or setup a degug environment.
├── lan 1 local area network, no intarnet access, only intranet (local lan) via a whitelist (wan access will receive a not authorized)
└── wan 2 wide area network, accessible from internet and intranet
Naming standard should be {PACKAGE_NAME}-{VERSION}
Currently, these do not have any parameters, so no -h option If the deployment package does not support something, a message will be diplayed when executed
/voloume1
└── docker_assistant
└── {lan or wan}
└── {container_name}
├── attach.sh
├── down.sh
├── env.sh
├── log.error.sh
├── log.standard.sh
├── log.tail.sh
├── restart.sh
└── up.sh
You can execute these by doing:
sudo ./{script}.sh
sudo ./up.sh
| Back | FazBrowse Home | New Git URL |