Self-hosted file/media sharing website.

Yes, though the repo may be old, it's still active and I'll try and fix any major issues that occur with my limited time.

You can see what it looks like using the demo: https://put.icu/. (IMPORTANT NOTICE: this demo isn't mine, and it's not running the latest updates of this repo)

• CLI: linx-client - Source

• Android: LinxShare - Source | Google Play
• CLI: golinx - Source

• Display common filetypes (image, video, audio, markdown, pdf).
• Display syntax-highlighted code with in-place editing.
• Documented API with keys for restricting uploads.
• Torrent download of files using web seeding.
• File expiry, deletion key, file access key, and random filename options.

1. Create a directory named _data and change its ownership chown -R 65534:65534 _data (65534 is the nobody user & group).
2. Create a config file named linx-server.conf (check linx-server.conf.example) inside that _data directory.

docker run -p 8080:8080 -v ./_data/linx-server.conf:/data/linx-server.conf -v ./_data/meta:/data/meta -v ./_data/files:/data/files -v ./_data/custom_pages:/data/custom_pages ghcr.io/m-primo/linx-server:latest -config /data/linx-server.conf

Check compose.yml, update it and remove this block:

build:
  context: .

Then change the image value from m-primo/linx-server:latest to ghcr.io/m-primo/linx-server:latest.

1. Download the latest binary from the releases.
2. Extract the archive tar -xvzf linx-server.tar.gz.
3. Run linx.sh -config /path/to/linx-server.conf.

Ideally, you would use a reverse proxy such as Nginx, Caddy, or Apache to handle TLS certificates and act as a high performance web server.

All configuration options are accepted either as arguments or can be placed in a file as such (see example file linx-server.conf.example in repo):

bind = 127.0.0.1:8080
sitename = myLinx
maxsize = 4294967296
maxexpiry = 86400
# ... etc

...and then run linx-server -config path/to/linx-server.conf

When files expire, access is disabled immediately, but the files and metadata will persist on disk until someone attempts to access them. You can set the following option to run cleanup every few minutes. This can also be done using a separate utility found the linx-cleanup directory.

A helper utility linx-genkey is provided which hashes keys to the format required in the auth files.

The following storage backends are available:

Linx-server supports being deployed in a subdirectory (ie. example.com/mylinx/) as well as on its own (example.com/).

A suggested deployment is running nginx in front of linx-server serving through fastcgi. This allows you to have nginx handle the TLS termination for example.
An example configuration:

server {
  ...
  server_name yourlinx.example.org;
  ...
  client_max_body_size 4096M;
  location / {
    fastcgi_pass 127.0.0.1:8080;
    include fastcgi_params;
  }
}

And run linx-server with the fastcgi = true option.

Run linx-server with the certfile = path/to/cert.file and keyfile = path/to/key.file options.

Run linx-server normally.

Any help is welcome, PRs will be reviewed and merged accordingly.

git pull https://github.com/m-primo/linx-server.git
cp -r linx-server /go/src/github.com/andreimarcu/
cd /go/src/github.com/andreimarcu/linx-server/
go mod download
go build -o /go/bin/linx-server .
cp /go/bin/linx-server /usr/local/bin/linx-server
mkdir -p /data/files && mkdir -p /data/meta && mkdir -p /data/locks && mkdir -p /data/custom_pages && chown -R 65534:65534 /data

(You might want to adjust a command or two)

or using Docker.

git pull https://github.com/m-primo/linx-server.git
docker compose build --no-cache
docker compose up -d

It's better to use Docker Compose for both development and deployment, since this is my method of contributing to this project.

ZizzyDizzyMC/linx-server

Copyright (C) 2015 Andrei Marcu

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Andrei Marcu, https://andreim.net/