A PHP-based self-hosted URL shortener on Platform.sh

Alejandro Celaya ede7551856 Updated build script so that it allows building a dist file for non-swoole envs 3 years ago
.github 1c492881e1 Updated to swoole 4.6.3 3 years ago
bin 16873201e9 Added support to search short URLs by title 3 years ago
config 9c48e6578d Removed mezzio-helpers and used ContentLengthMiddleware from shlink-common 3 years ago
data f5666c9451 Added new columns for extra tracking in visits table 3 years ago
docker 2fc6fb0a9a Added option to disable orphan visitstracking 3 years ago
docs 7d6d8e3a68 Added support to publish orphan visits in mercure 3 years ago
module 4e00c950cc Created ProcessRunnerTest 3 years ago
public 79ff12a1b0 Allow serving of 0-byte, real files 3 years ago
.dockerignore 3e2701f136 Updated how to copy mezzio helper script to dist file 3 years ago
.gitattributes 3a4a2e4483 Replaced scrutinizer with codecov 3 years ago
.gitignore a0d8d237d7 Gitignored helper file 3 years ago
.phpstorm.meta.php 2151b97bec Project migrated from zend to laminas 4 years ago
CHANGELOG.md 4e00c950cc Created ProcessRunnerTest 3 years ago
CONTRIBUTING.md 31a7212a71 Improvements in CONTRIBUTING doc 3 years ago
Dockerfile 1c492881e1 Updated to swoole 4.6.3 3 years ago
LICENSE 9a951589dc Updated year in license 3 years ago
README.md b5b3a50bb2 Added missing mention to xml extension 3 years ago
UPGRADE.md b6b0d09647 Added missing information in upgrading document 4 years ago
build.sh ede7551856 Updated build script so that it allows building a dist file for non-swoole envs 3 years ago
composer.json a2030b6c27 Updated to shlink-event-dispatcher 2.1 3 years ago
docker-compose.ci.yml f6d9a83202 Moved initial ci databases to specific docker-compose file 4 years ago
docker-compose.override.yml.dist 42e84e526e Added mariadb container for development environment 4 years ago
docker-compose.yml a2030b6c27 Updated to shlink-event-dispatcher 2.1 3 years ago
indocker 7c5825d1bc Removed custom AccessLogFactory by updating to zend-expressive-swoole 2.2 5 years ago
infection-db.json fff10ebee4 Applied API role specs to single short URL edition 3 years ago
infection.json fff10ebee4 Applied API role specs to single short URL edition 3 years ago
migrations.php e107aa9ed8 Removed commented migrations option 3 years ago
phpcs.xml 6433a67d52 Added all docker stuff to the project 4 years ago
phpstan.neon d932f0a204 Increased timeout on db commands to 10 minutes 3 years ago
phpunit-api.xml 3b1fc2a27d Updated link to PHPUnit's xsd to use local one 3 years ago
phpunit-db.xml 3b1fc2a27d Updated link to PHPUnit's xsd to use local one 3 years ago
phpunit.xml.dist 3b1fc2a27d Updated link to PHPUnit's xsd to use local one 3 years ago

README.md

Shlink

Build Status Code Coverage Latest Stable Version Docker pulls License Paypal donate

A PHP-based self-hosted URL shortener that can be used to serve shortened URLs under your own custom domain.

Table of Contents

Full documentation

This document contains the very basics to get started with Shlink. If you want to learn everything you can do with it, visit the full searchable documentation.

Docker image

Starting with version 1.15.0, an official docker image is provided. You can learn how to use it by reading the docs.

The idea is that you can just generate a container using the image and provide the custom config via env vars.

Self hosted

First, make sure the host where you are going to run shlink fulfills these requirements:

  • PHP 7.4 with JSON, curl, PDO, intl and gd extensions enabled (PHP 8.0 support is coming).
    • apcu extension is recommended if you don't plan to use swoole.
    • xml extension is required if you want to generate QR codes in svg format.
  • MySQL, MariaDB, PostgreSQL, Microsoft SQL Server or SQLite.
  • The web server of your choice with PHP integration (Apache or Nginx recommended).

Download

In order to run Shlink, you will need a built version of the project. There are two ways to get it.

  • Using a dist file

    The easiest way to install shlink is by using one of the pre-bundled distributable packages.

    Go to the latest version and download the shlink_x.x.x_dist.zip file you will find there.

    Finally, decompress the file in the location of your choice.

  • Building from sources

    If for any reason you want to build the project yourself, follow these steps:

    • Clone the project with git (git clone https://github.com/shlinkio/shlink.git), or download it by clicking the Clone or download green button.
    • Download the Composer PHP package manager inside the project folder.
    • Run ./build.sh 1.0.0, replacing the version with the version number you are going to build (the version number is only used for the generated dist file).

    After that, you will have a shlink_x.x.x_dist.zip dist file inside the build directory, that you need to decompress in the location fo your choice.

    This is the process used when releasing new shlink versions. After tagging the new version with git, the Github release is automatically created by a GitHub workflow, attaching the generated dist file to it.

Configure

Despite how you built the project, you now need to configure it, by following these steps:

  • If you are going to use MySQL, MariaDB, PostgreSQL or Microsoft SQL Server, create an empty database with the name of your choice.
  • Recursively grant write permissions to the data directory. Shlink uses it to cache some information.
  • Setup the application by running the bin/install script. It is a command line tool that will guide you through the installation process. Take into account that this tool has to be run directly on the server where you plan to host Shlink. Do not run it before uploading/moving it there.
  • Generate your first API key by running bin/cli api-key:generate. You will need the key in order to interact with shlink's API.

Using shlink

Once shlink is installed, there are two main ways to interact with it:

  • The command line. Try running bin/cli and see all the available commands.

    All of those commands can be run with the --help/-h flag in order to see how to use them and all the available options.

    It is probably a good idea to symlink the CLI entry point (bin/cli) to somewhere in your path, so that you can run shlink from any directory.

  • The REST API. The complete docs on how to use the API can be found here, and a sandbox which also documents every endpoint can be found in the API Spec portal.

    However, you probably don't want to consume the raw API yourself. That's why a nice web client is provided that can be directly used from https://app.shlink.io, or hosted by yourself.

Both the API and CLI allow you to do the same operations, except for API key management, which can be done from the command line interface only.

Contributing

If you are trying to find out how to run the project in development mode or how to provide contributions, read the CONTRIBUTING doc.


This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com