Skip to content

Latest commit

 

History

History
334 lines (244 loc) · 11.5 KB

README.md

File metadata and controls

334 lines (244 loc) · 11.5 KB
Raw

LittleLink Custom

Pull, deploy, enjoy!


About • About LittleLink Custom • Pull • Supported Architectures • Deployment • Updating • Build • Persistent storage • Reverse Proxy


Live Demo

Docker Hub

About

The official docker version of LittleLink Custom. This docker image is a simple to set up solution, containing everything you need to run LittleLink Custom.

The docker version of LittleLink Custom retains all the features and customization options of the original version.

This docker is based on Alpine Linux, a Linux distribution designed to be small, simple and secure. The web server is running Apache2, a free and open-source cross-platform web server software. The docker comes with PHP 8.0 for high compatibility and performance.

Using the docker is as simple as pulling and deploying.


About LittleLink Custom

LittleLink Custom is a highly customizable link sharing platform with an intuitive, easy to use user interface.

LittleLink Custom allows you to create a personal profile page. Many social media platforms only allow for one link. With this, you can have all the links you want clickable on one site. Set up your personal site on your own server in a few clicks.


Learn more about LittleLink Custom, and all the features here:


About


Pull

docker pull julianprieber/littlelink-custom


Supported Architectures


Deployment

You may change port 80, 443 to your preferred values.

Both HTTP and HTTPS are supported and exposed by default.

Optional environment variables


Deploy


Read more about persistent storage


Create a new volume:

docker volume create llc

docker run --detach \
    --name littlelink-custom \
    --publish 80:80 \
    --publish 443:443 \
    --restart unless-stopped \
    --mount source=llc,target=/htdocs \
    julianprieber/littlelink-custom

Custom deployment

docker run --detach \
    --name littlelink-custom \
    --hostname littlelink-custom \
    --env HTTP_SERVER_NAME="www.example.xyz" \
    --env HTTPS_SERVER_NAME="www.example.xyz" \
    --env SERVER_ADMIN="[email protected]" \
    --env TZ="Europe/Berlin" \
    --env PHP_MEMORY_LIMIT="512M" \
    --env UPLOAD_MAX_FILESIZE="16M" \
    --publish 80:80 \
    --publish 443:443 \
    --restart unless-stopped \
    --mount source=llc,target=/htdocs \
    julianprieber/littlelink-custom

Docker Compose

Example config.

version: "3.8"

services:

  littlelink-custom:
    hostname: 'littlelink-custom'
    image: 'julianprieber/littlelink-custom:latest'
    environment:
      TZ: 'Europe/Berlin'
      SERVER_ADMIN: '[email protected]'
      HTTP_SERVER_NAME: 'yourdomain.com'
      HTTPS_SERVER_NAME: 'yourdomain.com'
      LOG_LEVEL: 'info'
      PHP_MEMORY_LIMIT: '256M'
      UPLOAD_MAX_FILESIZE: '8M'
    volumes:
      - '/opt/docker/configs/littlelink/config/.env:/htdocs/.env:rw'
      - '/opt/docker/configs/littlelink/config/advanced-config.php:/htdocs/config/advanced-config.php:rw'
      - '/opt/docker/configs/littlelink/config/img:/htdocs/img:rw'
    ports:
      - '8088:80'
      - '8090:443'
    restart: unless-stopped
    networks:
      - 'mariadb'
      - 'misc'
      - 'redis'
networks:
  misc:
    external: true
    name: 'misc'
  mariadb:
    external: true
    name: 'db-mariadb'
  redis:
    external: true
    name: 'db-redis'

Optional configuration:

Optionally, you can change the app name in your ".env" file in the root directory of your LittleLink Custom installation. At the moment this is set to APP_NAME="LittleLink Custom" you can change "LittleLink Custom" to what ever you like. This setting defines the page title and welcome message.

For more configuration options, refer to the documentation.


Updating

When a new version is released, you will get an update notification on your Admin Panel.

Automatic one click Updater

This updater allows you to update your installation with just one click.


How to use the Automatic Updater:

  • To update your instance, click on the update notification on your Admin Panel.

  • Click on “Update automatically” and the updater will take care of the rest.


Build

If you wish to build or modify your own docker version of LittleLink Custom, you can do so with the instructions below:

  • Download this GitHub repository as well as the latest release of LittleLink Custom from here.
  • Place the downloaded release files directly into the littlelink-custom folder from this repository.

From the docker directory, run the command:

docker build -t littlelink-custom .
You can now set up your application on your defined ports.

Persistent storage

Persistent storage for docker containers is storage that is not lost when the container is stopped or removed.

This is advantageous since it means that data may be saved even if the container is removed. This is especially crucial when dealing with data that must be retained throughout restarts, such as a database.

All files important to run LittleLink Custom are stored in the "htdocs" folder found in the root directory of your docker container.

We recommend mounting that entire folder to an external volume.


However, some user may prefer to preserve only individual files.
Expand the details section below to read more about this:

If you wish to save only selective files, you may save the following files and folders: 
/htdocs/.env
/htdocs/database/database.sqlite
/htdocs/config/advanced-config.php
/htdocs/littlelink/images/avatar.png
/htdocs/themes (folder)
/htdocs/img (folder)

This might change with future releases.


Reverse Proxy


❌ Invalid setup ❌

⚠️ Incorrect ⚠️ ✅ Correct ✅
Invalid header configuration Valid header configuration

NGINX:

Below is an example NGINX setup for a reverse proxy.

server {
listen        443 ssl;
listen        [::]:443 ssl;
listen        80;
listen        [::]:80;
server_name   your.domain.name;


location / {
# Replace with the IP address and port number of your Docker container.
proxy_pass                          https://127.0.0.1:443;
proxy_set_header Host               $host;
proxy_set_header X-Real-IP          $remote_addr;


proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto  https;
proxy_set_header X-VerifiedViaNginx yes;
proxy_read_timeout                  60;
proxy_connect_timeout               60;
proxy_redirect                      off;

# Specific for websockets: force the use of HTTP/1.1 and set the Upgrade header
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-Proto $scheme;

# Fixes Mixed Content errors.
add_header 'Content-Security-Policy' 'upgrade-insecure-requests';



}
}