Download the PHP package moox/devlink without Composer

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

Moox Devlink

Moox Devlink is used to link packages a monorepo into any project and to deploy a production-ready composer.json. That allows us to develop Moox packages in any project. It runs on MacOS and Linux, Windows with special configuration.

Installation

Screenshots

Link

Status

Verbose

How It Works

  1. Prepare your project's .gitignore file:

  2. Configure your paths and packages in the config/devlink.php file and change the package path in the .env file, if needed (Windows users should set the DEVLINK_PACKAGES_PATH variable to packageslocal).

  3. When running php init.php

    • Creates a .env file from .env.example
    • Copies composer.json-linked to composer.json
    • Runs composer update

  4. When running devlink:status:

    • Shows the configuration and status of each package
    • Shows the link status (Linked, Unlinked, Deployed)
    • Shows the update status (Up-to-date, Outdated)
    • Has a verbose mode -v to show more information

  5. When running devlink:link:

    • Creates the packages folder, if it does not exist
    • Creates symlinks for all configured packages
    • Updates composer.json with development configuration
    • Creates composer.json-linked for production use
    • Asks to run composer install
    • Asks to run php artisan optimize:clear
    • Asks to run php artisan queue:restart

  6. When running devlink:deploy:

    • Removes all symlinks
    • Deletes the packages folder, if empty
    • Restores production-ready composer.json from composer.json-linked
    • Asks to run composer install
    • Asks to run php artisan optimize:clear
    • Asks to run php artisan queue:restart

  7. CI Safety Net - deploy.sh:

    • If composer.json-linked exists in the repository:
      • Remove all symlinks from /packages
      • rename composer.json-linked to composer.json
    • Commit and push the change in your GitHub Action

Mac and Linux work out of the box. You can have local packages mixed with the symlinked packages in your /packages folder.

Windows

On Windows there are most probably some issues with ignoring symlinks. If you run into issues, you can either globally or project-wise disable the symlinks or do the following:

Devlink will then link the packages into the packageslocal folder instead of mixing them into packages.

Classes

Please see the CLASSES.md file for a quick class overview.

Roadmap

Please see the ROADMAP.md file for what is planned.

Changelog

Please see the CHANGELOG.md file for what has changed.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

The MIT License (MIT). Please see License File for more information.

All versions of devlink 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 moox/devlink contains the following files

Loading the files please wait ....