Download the PHP package vijaycs85/notify-teams without Composer

On this page you can find all versions of the php package vijaycs85/notify-teams. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package notify-teams

action-notify-teams

Send deployment and container startup notifications to Microsoft Teams using Adaptive Cards. Works in two modes — as a GitHub Action for CI/CD pipeline events, or as a shell script for Azure container startup flows.

First time? Follow SETUP.md to create your Teams Incoming Webhook URL.

Mode 1 — GitHub Action (Deployment Events)

Use this in your GitHub Actions workflows to notify Teams when a deployment starts, succeeds, or fails.

Inputs

Name Description Required Default
teams_webhook_url MS Teams Incoming Webhook URL ✅ —
status start, success, or failure ✅ —
environment Target environment (e.g. dev, stg, prod) ✅ —
project_name Friendly project name shown on the card — ${{ github.repository }}
environment_url URL of the deployed environment — adds an Open environment button — —
message Optional extra detail shown on the card — —

Environment display names

Short codes are automatically mapped to friendly labels:

Input Displayed as
dev / development Development
stg / stage / staging Staging
prod / production Production
anything else Capitalised as-is

Basic usage — notify on start and completion

Recommended pattern — reusable notification workflow

Define a shared notification workflow once and call it from all your deployment workflows.

.github/workflows/notify.yml (in your project repo):

Calling it from a deployment workflow:

Mode 2 — Shell Script (Azure Container Startup Events)

Use this when your Azure Container App (or any server) needs to post Teams cards on restart, successful startup, or startup failure — independently of GitHub Actions.

Install via Composer

Add this package to your project and configure it to install into your .azure/ directory:

In your project's composer.json:

Then install:

The scripts will be available at .azure/notify-teams/scripts/notify_teams.sh.

Required environment variables

Set these in your Azure Container App configuration (or equivalent):

Variable Description Required
TEAMS_WEBHOOK_URL MS Teams Incoming Webhook URL ✅
ENVIRONMENT Environment name (e.g. dev, staging, prod) ✅
WEBSITE_SITE_NAME Auto-set by Azure — used as the container identifier —
PROJECT_NAME Friendly project name — falls back to WEBSITE_SITE_NAME —
ENV_URL URL shown as a link and button on the card —

Statuses

Status Card colour Meaning
restart 🟡 Warning Container has restarted, startup beginning
success 🟢 Good All startup steps completed
failure 🔴 Attention A startup step failed

Integrate into your startup script

Create .azure/startup.sh in your project (or update your existing one):

Configure the startup script in Azure

In your Azure Container App, set the startup command to:

Or in azure.yaml / Bicep:

All versions of notify-teams with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package vijaycs85/notify-teams contains the following files

Loading the files please wait ...