Download the PHP package dannyweeks/mersey without Composer

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

Mersey

Build Status Codacy Badge

A command line (CLI) tool written in PHP to simplify establishing/interacting an SSH connection to multiple servers quickly.

Some cool things you can do:

I also wrote a blog post when Mersey was first released you might find interesting.

Upgrading from Mersey v1 to v2?

Prerequisites

Installation

If it isn't already, add composers bin directory to your PATH by adding the below to your ~/.bash_profile (or ~/.bashrc).

Now, install Mersey globally so you have access to it anywhere by running

Initialise Mersey. This creates a hidden directory in your home to store your servers.

Your servers are loaded via a json file which is located ~/.mersey/servers.json. It comes populated with some example servers to help you on your way. Read the Defining Servers section for more information.

Assumptions/Default Settings

Mersey assumes your SSH key is stored ~/.ssh/id_rsa.

Mersey uses port 22 to connect the server.

However, these can be set manually on a per server basis.

Usage

Below are the commands to interact with the mersey tool.

Description Command Options/Notes
Add a server to the config mersey add Interactive questions
Edit the server config mersey edit Opens in default text editor
Edit global scripts mersey scripts Opens in default text editor
Ping servers and show results mersey ping
Connect to a server mersey <servername> -f/--force Skip reachable test. -p/--projects List projects
Go to a project mersey <servername> <projectname> -f/--force Skip reachable test. -s/--scripts List scripts
Run a script mersey <servername> <projectname> <scriptname> -f/--force Skip reachable test.

Defining Servers

There is a small amount of setting required to get up and running. Each server is an object in a json array. A server object needs a minimum of the following:

You can get started by running mersey add which will ask a series of questions and then add the defined server to your config file.

servers.json

Additional Server Settings

There are optional setting for servers which help facilitate your needs.

servers.json

Projects

Add a project to a server by creating an object in the projects array of the server.

servers.json

Scripts

Scripts are a way of running a command on a project and then exiting the session. They can be defined in two ways; either on a per project basis or globally.

A script object contains three required properties:

Before the command you define is ran mersey connects to the server and changes directory to the project's root.

An example of a script object would be:

Per Project

A script can be defined on a project by adding it to the project's scripts array.

servers.json

Global Scripts

Global scripts are defined in their own file: ~/.mersey/scripts.json. Global scripts can be run on any project.

The scripts.json must be a json array containing script objects.

scripts.json

Full Example Server Definition.

Below is a an example of a server called personal with one project called project. project has a script attached to it called clean.

Upgrade Guide

Upgrading To Version 2

Update Mersey via Composer.

composer global require dannyweeks/mersey:^2

Create global scripts file.

cp -i ~/.composer/vendor/dannyweeks/mersey/scripts.json.example ~/.mersey/scripts.json

Convert project scripts to objects.

The way scripts are defined has changed therefore must be updated open ~/.mersey/servers.json. See the scripts per project section for more details.

Contributing

All pull requests and bug fixes are welcomed. Please check the CONTRIBUTING file for more information.

All versions of mersey with dependencies

PHP Build Version
Package Version
Requires symfony/console Version ^2.7
justinrainbow/json-schema Version ^1.5
illuminate/support Version 5.2.21
illuminate/container Version 5.2.21
illuminate/contracts Version 5.2.21
geerlingguy/ping Version ^1.0
vlucas/phpdotenv Version ^2.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 dannyweeks/mersey contains the following files

Loading the files please wait ....