Preface

Recently, I’ve been looking into home media libraries, and most tutorials focus on NAS, but most of the applications actually run on Docker.

Now, I have the following demands for reading manga/doujinshi:

  • I have a large collection of manga archives on my computer and want various devices able to access these resources. —— A server capable of transmitting images via HTTP.
  • I want to manage the manga directory according to my preferences, not the rules of the server software.
  • When browsing manga on my phone/tablet, I want an easy-to-use interface. —— A user-friendly client or a Web UI.
  • The client should have a random manga selection feature. —— Due to the abundance of collected manga, randomly picking one for leisure is the most convenient.

Considering these, I chose LANraragi. Although Komga, Kavita, and Tachidesk (Sorayomi) are also open-source manga servers, they didn’t quite meet my expectations.

This article includes some excerpts from the official documentation and my own insights.

Read more »

pip

  1. Install script-house, version 0.0.2.

    1
    pip install script-house==0.0.2

    If you want to install the latest version by default, you can omit ==0.0.2.

    To install multiple dependencies in one line:

    1
    pip install script-house==0.0.2 pydantic==2.5.3 pymongo==4.6.1
Read more »

Preface

The Remote SSH extension in VS Code provides the functionality to connect to other remote hosts. While the basic way of connection requires a username and password, using a key allows for direct login without the effort to type the password every time.

However, it’s crucial to understand that VS Code merely provides a GUI, and how to use a SSH key to login is a separate matter. These two aspects should not be confused.

This article will primarily explain how to configure SSH keys on both the local machine and the remote machine. Subsequently, it will delve into the usage of the VS Code Remote SSH extension.

Read more »

Preface

Python is renowned for its rich set of modules. However, unlike in Java development where Maven uses group Id, artifact Id, and version to uniquely identify a dependency, in practice, most Python projects differentiate modules solely by their names. Run pip install <module>, and you’ve got the module. But what about the module version? Most project requirements do not specify versions, leading to constant errors for those who run the project later.

Hence, the concept of a weakened version number undoubtedly does more harm than good. How to solve this issue? By using venv (virtual environment).

If you directly use pip install, all Python projects share these modules, leading to potential compatibility issues. Venv copies the original Python environment. The virtual environment runs only on the copied Python, and the installed modules exist only in that virtual environment. Multiple virtual environments are isolated from each other.

Usage

1️⃣Create venv:

1
python -m venv C:\Users\Gustav\Desktop\test\venv

The directory C:\Users\Gustav\Desktop\test\venv is the virtual environment.

Read more »
0%