Download the PHP package technicpack/launcher-api without Composer

TechnicPack Launcher Api

Warning This project is abandoned and has been archived. For the current version of Solder, please see https://github.com/TechnicPack/TechnicSolder instead.

This package provides the endpoints necessary for the TechnicPack Launcher to load a modpack, its builds and the mods related with a build.

Its important to note that this package does very little on its own. Its intended to be included in a larger project such as TechnicPack Solder. See deployment for notes on how to deploy the package into another project.

Getting Started

These instructions will get you a copy of the package up and running on your local machine for development and testing purposes.

Prerequisites

Most of the requirements are handled through composer but you will still need to have a system with PHP 7.1+ and composer installed.

Setup

The package takes advantage of a framework for Laravel package development called Orchestral Testbench so there is little to do beyond cloning the repo and installing dependencies.

Running the tests

Its important that the project maintain very high test coverage to ensure that changes to the code don't break any expected behavior from the API. This API is called on nearly every time a user runs the TechnicPack Launcher, its an invisible part of what makes Technic work, and we want to keep it invisible to the day-to-day user.

PHPUnit Feature and Unit tests

A majority of the testing is done in feature tests which test the expected output of API endpoints under various conditions and with various inputs. You can run the full suite of unit and feature tests with PHPUnit.

Code style tests

Code style is also very important to us, a consistent code style makes the project easier to maintain and the pre-defined rules for how code should look lets everyone focus on function over form. Any push or PR will be checked by StyleCI before being merged. In order to reduce the number of commits, a local config and tool are included to allow you to run a fixer on your code before pushing it up to github.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Deployment

Deploying this package into a project is not trivial; the package is flexible but opinionated about the general underlying data structure. The instructions here will not be exhaustive, but should get you started towards integrating the Launcher API into your project.

Installation

Require this package with composer.

Laravel 5.5 uses Package Auto-Discovery, so doesn't require you to manually add the ServiceProvider.

If you are using Laravel < 5.5, you also need to add the service provider to your config/app.php providers array:

The package includes some database migrations, so make sure you run those migrations with php artisan migrate.

Configuration

The defaults are set in config/launcher-api.php. Copy this file to your own config directory to modify the values. You can publish the config using this command:

The configuration file is pretty well documented but make sure you read through everything and align it with your application. Sane defaults are set for all options, but these won't guarantee that the application works without any tweaking.

Implementation

As much of the code as possible has been encapsulated into the package; but there are some changes required to your application to hook up all the pieces. We've made those changes as minimal as possible end grouped things into traits and interfaces for ease of deployment.

Linking Modpacks to Clients

The HasClients trait provides several methods to assist you in managing private modpacks exposed to known clients. The trait defines a clients relation to the TechnicPack\LauncherApi\Client model allows you to iterate over all of the modpacks's clients:

The trait also provides several other helper methods that are useful when working with clients:

Describe relationships and scopes

This package assumes that the Modpack, Build and Mod models expose information about how they're related, and how to limit queries to specific kinds of results. The easiest way to provide that information is to implement the Modpack and Build interfaces on your models (there is no interface for Mod since the only information we need comes from the $build->mods() relationship).

Frontend

This package ships with a JSON API that you may use to allow your users to create clients and keys. However, it can be time consuming to code a frontend to interact with these APIs. So, we've also included pre-built Vue components you may use as an starting point for your own implementation.

note that the components do not include ANY template, you must implement your own html as an inline-template

To publish the Launcher API Vue components, use the vendor:publish Artisan command:

The published components will be placed in your resources/assets/js/vendor/launcher-api directory. Once the components have been published, you should register them in your resources/assets/js/app.js file:

After registering the components, make sure to run npm run dev to recompile your assets. Once you have recompiled your assets, you may drop the components into one of your application's templates to get started creating clients and keys.

Authors

• Kyle Klaus - Initial work - Indemnity83

See also the list of contributors who participated in this project.

License

This project is licensed under the MIT License - see the LICENSE.md file for details