Download the PHP package alsvanzelf/debby without Composer

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

⚠️ ARCHIVED

This package is not maintained anymore. As an alternative you can use dependabot and github webhooks to get notifications.


Debby - stay on top of your dependencies

Debby checks your Composer & npm dependencies and tells you when to update.

In the end, you'll be more comfortable upgrading because updates can be often and small.

Super fast setup :rocket:

Replace repo with the path of your repository on GitHub (organization/project) and token with a personal access token. This runs Debby every day at 8 o'clock and create issues whenever updates are found.

Setup in a normal pace, with a bit more explanation

  1. Install Debby via Composer
  2. Configure notifications to GitHub, Trello, Slack, email
  3. Setup a cronjob (there's other ways as well, see below)

Also check out the questions Debby gets asked frequently. Or checkout :blue_book: the documentation.

1. Installation

Use Composer to install Debby herself. Use require to get the latest stable version:

2. Configure notifications

Debby can talk to GitHub issues, Trello, Slack, and email.

Pick the channel(s) that you want notifications on, make a debby.json configuration file with the access details for these channels, and place it in the root of your project.

I.e. for notifying to GitHub issues, use:

See the :blue_book: wiki on the specific configuration.

3. Fire up

Setup a cronjob to run the built-in notify script passing it your configuration file.

Run crontab -e and add:

:thumbsup:

Sit back and relax. Take a :coffee: or :tea: or :beer:

FAQ

Can I run it without a cronjob?

You can call Debby from php and do what every you want.

See example/custom.php for a complete example.

I don't want to run Debby in production

You don't trust her? She's open source you know. Anyway, Debby runs just fine in a testing environment. No hard feelings. :heart: Just take into account that Debby will run just as fine while bisecting on old commits and notify you for updates since then. Also be-aware that Debby caches earlier notified packages, which might cause trouble when switching branches backwards.

Debby can not determine manage paths?

or

Can I have composer.json outside the project root?

or

I don't want to check [Composer|npm|...]

By default, Debby checks all package managers it can find. In some situations this doesn't work. I.e.:

Then you'll need to adjust configuration to specify which managers you want to check, and where to find them.

I.e. for checking Composer, add the following to your debby.json:

See the :blue_book: wiki on the specific configuration.

Why does Debby tell me to update above the composer constraint?

Debby will tell you about an update i.e. 2.0 when you require ^1.5. If you would run composer update yourself, that update won't show up. However, new releases might contain security updates also affecting your older version. For now, Debby defaults to telling you all these updates. You're welcome to help making Debby smarter in this, i.e. checking for security updates.

Contribute

Pull Requests or issues are welcome!

License

MIT

:girl:

By the way, Debby will tell when she needs an update herself. You don't need to do anything. :sparkles:


All versions of debby with dependencies

PHP Build Version
Package Version
Requires php Version >=5.5
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 alsvanzelf/debby contains the following files

Loading the files please wait ....