Use case

Deliver from CI

Every test build sent from CI under a code, and the client’s answer coming back as a status: approved, or changes.

.github/workflows/recette.yml

# colis is built from the repository until it is on npm
- run: npm run build && tar cz ./dist > recette.tar.gz
- run: |
    CODE=$(colis envoyer ./recette.tar.gz)
    echo "Build de recette : https://livraison.example.com/$CODE" >> "$GITHUB_STEP_SUMMARY"
  env:
    COLIS_REMOTE: https://livraison.example.com/api/transfers
    COLIS_TOKEN: ${{ secrets.DROP_PASSWORD }}

# later, in any script
# colis statut "$CODE" | head -1   → envoyé, ouvert, validé or à corriger

The situation

What is actually going on.

The problem

Every test build leaves through a different channel: a storage link that never expires, a file too heavy for email, a screenshot in a chat. The tester’s feedback lands somewhere else, and which build was tested is never clear.

What colis does about it

The pipeline sends the build with colis envoyer against your delivery page. The code is the only thing on stdout, so it drops into a message or a pull request comment. The client opens the link, downloads, tests, then approves or describes what is wrong. colis statut <code> | head -1 gives a script the state, and --json the whole receipt.

Worth watching

The things that are easy to get wrong.

The function’s limit

The CLI sends in one request, through the delivery page’s function, so the file has to fit under DROP_MAX_SIZE_MB: 4 MB by default, for Vercel. Above that, send it from the page, which goes straight to the bucket in parts, or raise the limit on a host without that cap.

The token is the upload password

--token, or COLIS_TOKEN in CI, is the page’s DROP_PASSWORD. The CI machine needs no S3 key at all.

The page’s options do not ride along

A parcel the CLI creates takes the deployment’s defaults: no password, no note, the default lifetime. To set them from a terminal, send the x-drop-* headers with curl.

Packagescoliscolis-drop

Other ways to deliver.

Get a mock-up signed off

A PDF or an image sent under a code, previewed by the client in the page, approved in one click or sent back with a comment.

Deliver heavy files

Up to 2 GB by default, sent by the browser straight to your bucket, in parts, resumed if the connection drops.

A confidential delivery

A password the client types once, a short lifetime, and a code that is gone at the first download.

Send it. They sign off. You know.

Your storage, a delivery page under your name, a webhook at every step. Nothing hosted by someone else.

Try the demo Deploy the delivery page GitHub