Download the PHP package discoverygarden/embargo without Composer

On this page you can find all versions of the php package discoverygarden/embargo. 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 embargo

Embargo

Embargo content indefinitely or till specified date, limiting access to specific users and/or IP addresses.

This module is intended to be a successor to https://github.com/discoverygarden/embargoes

Installation

Install as usual.

Migrating from embargoes

Migrations exist in the migrate_embargoes_to_embargo module for migrating from embargoes's entities onto embargo's. See the module's docs for more info.

Configuration

Configuration options can be set at admin/config/content/embargo, including a contact email and notification message.

Embargoes can be managed at admin/content/embargo.

To add an IP range for use on embargoes, navigate to admin/content/embargo/range and click 'Add IP range'. Ranges created via this method can then be used as IP address whitelists when creating embargoes. This CIDR to IPv4 Conversion utility can be helpful in creating valid CIDR IP ranges.

search_api processor(s)

We have multiple search_api processors which attempt to constrain search results based on the effects of embargoes on the entities represented by search results, including:

Typically, only one should be used in any particular index.

Usage

Applying an embargo

An embargo can be applied to an existing node by clicking the "Embargoes" tab on a node, or navigating to embargoes/node/{node_id}. From here, an embargo can be applied if it doesn't already exist, and existing embargoes can be modified or removed.

Known Issues/FAQ

Troubleshooting/Issues

Having problems or solved a problem? Contact discoverygarden.

Maintainers/Sponsors

Attribution

This module is heavily based on and includes contributions from discoverygarden/embargoes which was forked from fsulib authored by Bryan J. Brown.

License

GPLv2

All versions of embargo with dependencies

PHP Build Version
Package Version
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 discoverygarden/embargo contains the following files

Loading the files please wait ...