LANraragi
GithubDemoDocker HubDiscord Server
Nightly Release
Nightly Release
  • LANraragi Documentation
  • Installing LANraragi
    • ❓Which installation method is best for me?
    • πŸͺŸLRR for Windows (Win10)
    • 🍎Homebrew (macOS)
    • 🐳Docker (All platforms)
    • πŸ› οΈSource Code (Linux/macOS)
    • 🐧Community (Linux)
    • πŸ‘ΏJail (FreeBSD)
  • Basic Operations
    • πŸš€Getting Started
    • πŸ“šReading Archives
    • βœ’οΈAdding Metadata
    • πŸ”ŽSearching the Archive Index
    • πŸ“ˆStatistics and Logs
    • πŸ–ŒοΈThemes
  • Advanced Usage
    • πŸ¦‡Batch Operations
    • πŸ“‚Categories
    • ⬇️Downloading Archives
    • πŸ’ΎBackup and Restore
    • πŸ“±Using External Readers
    • 🌐Network Interface Setup
    • πŸ•΅οΈProxy Setup
    • πŸ“Tag Rules
  • Developer Guide
    • πŸ—οΈSetup a Development Environment
    • πŸ›οΈArchitecture & Style
    • 🈁Translating LANraragi to other languages
  • API Documentation
    • πŸ”‘Getting started
    • Search API
    • Archive API
    • Database API
    • Category API
    • Tankoubon API
    • Shinobu API
    • Minion API
    • Miscellaneous other API
  • Writing Plugins
    • 🧩Getting started
    • Login Plugins
    • Metadata Plugins
    • Downloader Plugins
    • Generic Plugins ("Scripts")
    • Code Examples
Powered by GitBook
On this page
  • Building your network location string
  • Source Installs
  • Docker
  • Docker with SSL

Was this helpful?

  1. Advanced Usage

Network Interface Setup

PreviousUsing External ReadersNextProxy Setup

Last updated 3 years ago

Was this helpful?

By default, LRR listens on all IPv4 Interfaces on port 3000. To change this, you have to specify a different network location when starting the app.

Building your network location string

The network location format accepted by LRR looks like this: http(s)://*:(port)

All listen locations are valid.

For example, if you want to listen on port 5555 with SSL only, the string would look like: https://*:5555?cert=/path/to/server.crt&key=/path/to/server.key

Once you have your string ready, you can assign it to the environment variable LRR_NETWORK. It'll be picked up automagically.

If you're using Docker, remember to mount your cert and keys to a path reachable by the container: The arguments above will resolve within the container's filesystem!

Source Installs

export LRR_NETWORK=http://127.0.0.1:8000
npm start

> lanraragi@0.6.0 start /mnt/c/Users/tiki/Desktop/lrr
> perl ./script/launcher.pl -f ./script/lanraragi

キタ━━━━━━(οΎŸβˆ€οΎŸ)━━━━━━!!!!!
[LANraragi] [info] LANraragi 0.6.0-BETA.2 (re-)started. (Debug Mode)
[...]
[Mojolicious] Listening at "http://127.0.0.1:8000"
Server available at http://127.0.0.1:8000

Docker

docker run --name=lanraragi -p 8000:8000 \
--mount type=bind,source=[YOUR_CONTENT_DIRECTORY],\
target=/home/koyomi/lanraragi/content \
-e LRR_NETWORK=http://*:8000 difegue/lanraragi

Docker with SSL

docker run --name=lanraragi-ssl -p 3333:3333 \
--mount type=bind,source=[YOUR_CONTENT_DIRECTORY],\
target=/home/koyomi/lanraragi/content \
--mount type=bind,source=[DIRECTORY_CONTAINING_SSL_CERT],target=/ssl \
-e LRR_NETWORK="https://*:3333?cert=/ssl/crt.crt&key=/ssl/crt.key" difegue/lanraragi

Notice that the certificate and key must come from your host filesystem and henceforth might need a second --mount command.

🌐
supported by "listen" in Mojo::Server::Daemon