A React-based client application for Shlink
Find a file
2020-02-17 18:21:52 +01:00
.github Added github funding 2019-10-22 19:33:59 +02:00
config Updated nginx.conf (optimization for future) 2020-01-31 01:36:17 +01:00
dist Created dist dir 2018-08-05 11:39:49 +02:00
public Update .htaccess 2020-01-31 01:29:41 +01:00
scripts Updated dev dependencies 2019-10-05 19:08:50 +02:00
src Ensured domain is dispatched when modifying a short URL somehow 2020-02-08 10:46:11 +01:00
test Uninstalled jest-each and replaced by jest's native each 2020-02-17 18:21:52 +01:00
.dockerignore Dockerignored .gihub folder 2019-04-11 22:03:53 +02:00
.eslintrc When handling API errors, use the type prop and fallback to error if not found 2020-01-11 12:24:45 +01:00
.gitignore Catched error when loading servers from a servers.json file 2019-04-28 13:07:55 +02:00
.scrutinizer.yml Updated project to node 12.14.1 2020-01-28 18:40:33 +01:00
.stylelintrc Added stylelint config 2018-08-25 10:22:25 +02:00
.travis.yml Updated project to node 12.14.1 2020-01-28 18:40:33 +01:00
CHANGELOG.md Updated changelog 2020-02-08 10:47:44 +01:00
docker-compose.override.yml.dist Replaced yarn by npm 2019-04-14 21:58:10 +02:00
docker-compose.yml Updated project to node 12.14.1 2020-01-28 18:40:33 +01:00
Dockerfile Updated project to node 12.14.1 2020-01-28 18:40:33 +01:00
indocker Created Storage service test 2018-12-19 20:43:55 +01:00
jest.config.js Updated coding styles and test configs 2019-01-05 23:16:13 +01:00
LICENSE Updated date on license file 2020-01-19 21:20:32 +01:00
package-lock.json Updated dev dependencies 2019-10-05 19:08:50 +02:00
package.json Uninstalled jest-each and replaced by jest's native each 2020-02-17 18:21:52 +01:00
README.md Updated documentation 2020-01-31 20:37:50 +01:00
stryker.conf.js Updated travis to run mutations on changed files only 2019-04-22 10:04:41 +02:00

shlink-web-client

Build Status Docker build status Code Coverage Scrutinizer Code Quality GitHub release GitHub license Paypal Donate

A ReactJS-based progressive web application for Shlink.

Installation

There are three ways in which you can use this application.

The easiest way to use shlink-web-client is by just going to https://app.shlink.io.

The application runs 100% in the browser, so you can safely access any shlink instance from there.

Docker image

If you want to deploy shlink-web-client in a container-based cluster (kubernetes, docker swarm, etc), just pick the shlinkio/shlink-web-client image and do it.

It's a lightweight nginx:alpine image serving the static app on port 80.

Self-hosted

If you want to self-host it yourself, get the latest release and download the distributable zip file attached to it (shlink-web-client_X.X.X_dist.zip).

The package contains static files only, so just put it in a folder and serve it with the web server of your choice.

Considerations:

  • Provided dist files are configured to be served from the root of your domain. If you need to serve shlink-web-client from a subpath, you will have to build it yourself following these steps.
  • The app has a client-side router that handles dynamic paths. Because of that, you need to configure your web server to fall-back to the index.html file when requested files do not exist.
    • If you use Apache, you are covered, since the project includes an .htaccess file which already does this.
    • If you use nginx, you can see how it's done for the docker image and do the same.

Pre-configuring servers

The first time you access shlink-web-client from a browser, you will have to configure the list of shlink servers you want to manage, and they will be saved in the local storage.

Those servers can be exported and imported in other browsers, but if for some reason you need some servers to be there from the beginning, starting with shlink-web-client 2.1.0, you can provide a servers.json file in the project root folder (the same containing the index.html, favicon.ico, etc) with a structure like this:

[
  {
    "name": "Main server",
    "url": "https://doma.in",
    "apiKey": "09c972b7-506b-49f1-a19a-d729e22e599c"
  },
  {
    "name": "Local",
    "url": "http://localhost:8080",
    "apiKey": "580d0b42-4dea-419a-96bf-6c876b901451"
  }
]

The list can contain as many servers as you need.

If you are using the shlink-web-client docker image, you can mount the servers.json file in a volume inside /usr/share/nginx/html, which is the app's document root inside the container.

docker run --name shlink-web-client -p 8000:80 -v ${PWD}/servers.json:/usr/share/nginx/html/servers.json shlinkio/shlink-web-client

Serve project in subpath

Official distributable files have been built so that they are served from the root of a domain.

If you need to host shlink-web-client yourself and serve it from a subpath, follow these steps:

  • Download shlink-web-client source code for the version you want to build.
  • Decompress the file and cd into the resulting folder.
  • Open the package.json file in the root of the project, locate the homepage property and replace the value (which should be an empty string) by the path from which you want to serve shlink-web-client.
    • For example: "homepage": "/my-projects/shlink-web-client",.
  • Build the project:
    • For classic hosting:
      • Download node 10.15 or later.
      • Install project dependencies by running npm install.
      • Build the project by running npm run build.
      • Once the command finishes, you will have a build folder with all the static assets you need to run shlink-web-client. Just place them wherever you want them to be served from.
    • For docker image:
      • Download docker.
      • Build the docker image by running docker build . -t shlink-web-client.
      • Once the command finishes, you will have an image with the name shlink-web-client.