Libraries tagged by stratus

thisisbd/silverstripe-maintenance-mode

24 Favers
11504 Downloads

SilverStripe Maintenance Mode Module. Allows an administrator to put site in offline mode with 503 status to display a 'Coming Soon', 'Under Construction' or 'Down for Maintenance' Page to regular visitors, whilst allowing a logged in admin user to browse and make changes to the site.

Go to Download


t3n/flow-healthstatus

6 Favers
25968 Downloads

Flow Framework package to check the health status of you application

Go to Download


smith197/steamauthentication

448 Favers
527 Downloads

SteamAuthentication is a basic set of PHP files that enable users to login using their steam account to view protected content on your website. it creates a session using their steamid as the sessionID and checks for the session when a user visits the page. It also includes a file which allows you to use their profile information such as their avatar and online status.

Go to Download


sfneal/dependencies

1 Favers
4980 Downloads

Track your application dependencies and there status within a Laravel Application

Go to Download


sametsahindogan/laravel-jwtredis

124 Favers
1615 Downloads

This package allows JWT-authenticated users to be stored and management in Redis with their roles, permissions, statuses and anything you want.

Go to Download


sachoo/phalcon-console-migration

1 Favers
124543 Downloads

Based on sachoo/phalcon-console, this component handle databases migrations (up, down, diff, status, run)

Go to Download


paypaplane/svix-client

0 Favers
8669 Downloads

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download


lobotomised/laravel-autocrawler

1 Favers
20216 Downloads

A tool to crawl your own laravel installation checking your HTTP status codes

Go to Download


liquidweb/ssl-certificate

18 Favers
3600 Downloads

A class to easily query the properties of and validate the status of an ssl certificate

Go to Download


leadtech/http-commons

0 Favers
18870 Downloads

A zero dependency set of definitions to help work with headers and status codes.

Go to Download


eleirbag89/mastodonbotphp

29 Favers
641 Downloads

A very simple PHP Mastodon API for sending statuses

Go to Download


chantouch/laravel-jwt-redis

9 Favers
3624 Downloads

This package allows JWT-authenticated users to be stored and management in Redis with their roles, permissions, statuses and anything you want.

Go to Download


amazeelabs/silverback_publisher_monitor

0 Favers
11246 Downloads

Publisher status indicator for drupal.

Go to Download


always-open/laravel-auth-notifications

3 Favers
9422 Downloads

A Laravel package to notify your users when their password, two-factor authentication, or login status changes.

Go to Download


68publishers/health-check

3 Favers
2032 Downloads

Check the status of an application services.

Go to Download


<< Previous Next >>