Releases: section/sectionctl
Releases · section/sectionctl
v1.12.3
v1.12.2
- Minor bug fixes & improvements
v1.12.1
- fixed
sectionctl login
not working
Windows Install: Use the installer
Ubuntu: sectionctl-v1.12.1-linux-amd64.deb
dpkg -i sectionctl-v1.12.1-linux-amd64.deb
RHEL/CentOS/Fedora: sectionctl-v1.12.1-linux-amd64.rpm
sudo rpm –i sectionctl-v1.12.1-linux-amd64.rpm
Mac Install:
brew tap section/brews
brew install sectionctl
v1.12.0
- rpms, debs, and windows installers
- the package json variables are now applied globally for any command ie:
{
"name": "cra2",
"version": "0.1.0",
"private": true,
"dependencies": {
"serve": "^11.3.2"
},
"Section": {
"accountId": "1887", // same as -a or --account-id
"appId": "7749", // same as -i or --app-id
"environment": "Production", // same as -e or --environment
"module-name": "nodejs", // same as --app-path
"start-script": "start" // not presently supported, but may be in the future
},
"scripts": {
"start": "serve -s build -l 3000 -l 8080",
"deploy": "sectionctl deploy"
}
}
if you are in the same directory as the app, and you run a command such as sectionctl logs
, or sectionctl deploy
, it will automatically fill in the information for you.
~/cra2/ $ sectionctl logs
InstanceName[Log Type] Log Message
nodejs-57ccf76c77-gp9tg-5e3[app] 2021/06/07 20:17:17 Redirecting access.log to STDOUT and error.log to STDERR.
nodejs-57ccf76c77-gp9tg-5e3[app] Listening on http://0.0.0.0:9000/metrics
nodejs-57ccf76c77-gp9tg-5e3[app] 2021/06/07 20:17:17 [WARN] Updating environment
nodejs-57ccf76c77-gp9tg-5e3[app] 2021/06/07 20:17:17 [ERROR] Node.js is not listening on any ports
nodejs-57ccf76c77-gp9tg-5e3[app]
nodejs-57ccf76c77-gp9tg-5e3[app] > cra2@0.1.0 start /opt/section/node
nodejs-57ccf76c77-gp9tg-5e3[app] > serve -s build -l 3000 -l 8080
nodejs-57ccf76c77-gp9tg-5e3[app]
nodejs-57ccf76c77-gp9tg-5e3[app] INFO: Accepting connections at http://localhost:3000
nodejs-57ccf76c77-gp9tg-5e3[app] INFO: Accepting connections at http://localhost:8080
nodejs-57ccf76c77-gp9tg-5e3[app] [WARN] Node is listening on the following port(s): 8080 3000
nodejs-57ccf76c77-gp9tg-5e3[app] [WARN] App will serve on the following port: 8080
nodejs-57ccf76c77-gp9tg-5e3[app] 2021/06/07 20:17:28 [WARN] The node app is already being served.
nodejs-57ccf76c77-gp9tg-5e3[app] 2021/06/07 20:17:28 [WARN] Initialising Nginx
nodejs-57ccf76c77-gp9tg-5e3[app] 2021/06/07 20:17:28 [WARN] Updating custom Nginx server.conf
v1.11.1
- Fix spinner flashing on windows terminal
- debug logging overhauled to JSON format
- CI mode using --quiet or environment variable set
CI=true
that has minimal output. - more colors for a prettier experience.
- parse package json for variables with this syntax. can be used with
sectionctl deploy
to avoid specifying any flags.
{
"name": "cra",
"version": "0.1.0",
"private": true,
"dependencies": {
"serve": "^11.3.2"
},
"Section": {
"accountId": "1887", // same as -a or --account-id
"appId": "7749", // same as -i or --app-id
"environment": "Production", // same as -e or --environment
"module-name": "nodejs", // same as --app-path
"start-script": "start" // not presently supported, but may be in the future
},
"scripts": {
"start": "serve -s build -l 4001 -l 8080",
"deploy": "sectionctl deploy"
}
}
v1.10.4
- remove requirement of server.conf in your node.js package folder as it is now optional.
v1.10.3
- environments with slashes in their name were failing to deploy due to a difference in how the git repo URL is formatted. fixed
- the temp folder for the app repo was misspelled, also fixed that
v1.10.2
- sectionctl deploy now allows for the
-e
or--environment
argument to specificy a branch on your section config git repo to push to. It defaults toProduction
.
ie:
sectionctl deploy -a 0000 -i 0000 -e staging
the default still works
sectionctl deploy -a 0000 -i 0000 # same as: sectionctl deploy -a 0000 -i 0000 -e Production
v1.10.1
- sectionctl now uses its own git author instead of the default system one, fixing issues for users with no default
v1.10.0
- Deploy now uses git so that failed deployments give better feedback and have more time before timing out.