Foodsoft

Replace <vm-ip> with the public IP of your VM. The default login user is azureuser.

ssh azureuser@<vm-ip>

Check the systemd units and the Compose containers:

sudo systemctl is-active docker.service nginx.service foodsoft.service foodsoft-firstboot.service cd /opt/foodsoft && sudo docker compose ps --format "table {{.Name}}\t{{.Status}}"

Each systemd unit prints active. The five Compose containers (foodsoft-app, foodsoft-worker, foodsoft-cron, foodsoft-db and foodsoft-redis) are all in the Up state.

The nginx reverse proxy serves an unauthenticated static /sac-health endpoint on port 80, and the Foodsoft login page answers on /f/login. The Rails app listens on loopback only, and the database and Redis are not published to any host port. Check the endpoints and the listening sockets with:

curl -s -o /dev/null -w "%{http_code}\n" http://127.0.0.1/f/login
curl -s http://127.0.0.1/sac-health
sudo ss -tlnH | awk '{print $4}' | sort -u

/f/login returns 200, and /sac-health returns OK. The listening sockets show only :80 (nginx) and :22 (SSH) on the public interface, with the Rails app on 127.0.0.1:3000. MariaDB and Redis do not appear, because they are reachable only on the Docker network.

On its first boot, your instance generates a unique administrator password and writes it to a root-only file, along with a fresh Rails secret key base and database password. Read the file with:

sudo cat /root/foodsoft-credentials.txt

The file lists FOODSOFT_URL (where to sign in), FOODSOFT_LOGIN_URL, FOODSOFT_ADMIN_USER (admin) and FOODSOFT_ADMIN_PASSWORD. Store the password somewhere safe.

Foodsoft's upstream seed creates an initial admin user with the well-known password secret. On this image, first boot rotates that password to your per-VM value before the web app is ever exposed, so the default login no longer works. Verify this with:

cd /opt/foodsoft
sudo docker exec foodsoft-app bundle exec rails runner \
  'puts User.authenticate("admin","secret") ? "DEFAULT STILL LIVE" : "default admin/secret REJECTED"'

The output is default admin/secret REJECTED, which confirms that the seeded default credential no longer works.

Open http://<vm-ip>/ in your browser. Foodsoft redirects you to the foodcoop login page at /f/login. Enter the user admin and the FOODSOFT_ADMIN_PASSWORD from Step 4, then click Login.

You can also verify the credentials from the command line. The command prints LOGIN_OK when the per-VM password authenticates:

PASS=$(sudo grep '^FOODSOFT_ADMIN_PASSWORD=' /root/foodsoft-credentials.txt | cut -d= -f2-)
cd /opt/foodsoft
sudo docker exec -e RT_PASS="$PASS" foodsoft-app bundle exec rails runner \
  'puts User.authenticate("admin", ENV["RT_PASS"]) ? "LOGIN_OK" : "LOGIN_FAIL"'

After you sign in, you land on the Foodsoft dashboard. It shows the current ordering rounds, your order group's balance and engagement, and quick links to members, orders, products and finances.

Open Articles -> Suppliers/articles to manage the suppliers your coop buys from. Each supplier holds its own article catalogue, stock and deliveries. Use Create new supplier to add your own.

Open a supplier to manage its article catalogue: names, categories, units, net prices, VAT and deposit. You can add articles one at a time, upload a spreadsheet, or open a new ordering round for the coop directly from here.

The day-to-day flow is then as follows. Open an order for a supplier, let members place their orders during the ordering window, and close the order. Finally, balance the order in the finance area so that each order group's account is charged its share.