Download the PHP package writecrow/basecamp_api without Composer

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

Example code of writecrow/basecamp_api

Informations about the package basecamp_api

Basecamp API v3 Integration

This is a Drupal module that facilitates using the [https://github.com/basecamp/bc3-api](Basecamp API v3).

As an integration module, this facilitates transactions between the Basecamp endpoints, and requires simple coding to achieve this.

After creating an authorized application & storing the initial access token & refresh token, this module will continue to renew the token via a cron job that runs once per day.

Once complete, actions, such as creating a new todo, are as simple as:

Proper setup & configuration of the refresh token

At this time, creating the initial access & refresh token is the purview of the developer (and it is pretty easy -- see https://github.com/basecamp/api/blob/master/sections/authentication.md).

  1. Sign in to Basecamp with the user ID that will provide the integration (in most cases, this should be identified as a non-human account so that people know that actions performed are being triggered by the Drupal integration).
  2. Go to https://launchpad.37signals.com/integrations and use the Authorization dialog to generate a 1-time code.

  3. Trade this code for a long-lived access token & refresh token:

  4. Set these tokens in Drupal's non-config-exportable State API:

  5. Important: by default, this token will not refresh via cron so that development environments don't accidentally invalidate your access token in the production environment. For the token to be refreshed regularly in your production environment, add the following to your settings.php or equivalent:

All versions of basecamp_api with dependencies

PHP Build Version
Package Version
Requires composer/installers Version ^1 || ^2
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 writecrow/basecamp_api contains the following files

Loading the files please wait ....