Each package contains the same application, compiled for its platform and signed. Then open the address in a browser, choose Set up CHIPS and enter the setup code. Check every download against SHA256SUMS.
Unzip, then double-click deploy\windows\install.cmd
tar xzf chips-2.2.0-macos-arm64.tar.gz && cd chips-2.2.0 ./deploy/install.sh
sudo apt install ./chips_2.2.0_amd64.deb
tar xzf chips-2.2.0-linux-x86_64.tar.gz && cd chips-2.2.0 sudo ./deploy/install.sh --domain chips.example.com \ --letsencrypt you@example.com
# behind an Application Load Balancer (ACM) sudo ./deploy/install.sh --domain chips.example.com --alb
pip install chips_estimation-2.2.0-*.whl chips --version
printf 'STORAGE_SECRET=%s\nDB_PASSWORD=%s\n' \ "$(openssl rand -hex 32)" "$(openssl rand -hex 24)" > .env docker compose up -d
Step-by-step instructions for every platform are in the installation guide; on AWS, see CHIPS on AWS. New to CHIPS? Open the demo right after setting up.
From the stories themselves: the scrum master records when work started and finished, defects, rework and carry-over, or CHIPS reads them from Jira's history, resolution dates, linked bugs and sprint field.
A new installation can only be set up with a one-time setup code from the server. Accounts get two-factor sign-in, lock after repeated wrong passwords and follow a password policy. Pages carry a strict content security policy, secrets are encrypted, the service runs sandboxed, and every sign-in and change is in the activity log. The software you install is compiled and signed, and notices if it has been modified.
Yes. Back up the database and restore it on the new server. A key bound to one installation keeps working because the installation ID is stored in the database; if you start fresh, ask support for a re-issued key.
On Linux the installer puts the Apache web server in front of CHIPS. Apache answers on ports 80 and 443, handles HTTPS with a free Let's Encrypt certificate, and passes pages and live updates to CHIPS, which is never reachable directly. On AWS it runs on an EC2 instance with Amazon Linux 2023, Ubuntu or Debian, on its own or behind an Application Load Balancer with an ACM certificate, with the database on the instance or in Amazon RDS. A launch script sets up a new instance without logging in.
Only to install the packages it depends on. An offline bundle with every dependency is available for isolated networks.