{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/436", "result": {"data":{"issuesJson":{"id":"b9683483-acb2-5098-8905-f15b543a22bc","title":"mtlynch/picoshare: 可建立文件共享服务，支持多种类型，部署简单，易于使用","number":436,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposmtlynch/picoshare
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n

PicoShare

\n

\"CircleCI\"
\n\"Docker
\n\"Docker
\n\"GitHub
\n\"GitHub
\n\"Contributors\"
\n\"License\"

\n

Overview

\n

PicoShare is a minimalist service that allows you to share files easily.

\n\n

\"PicoShare

\n

Why PicoShare?

\n

There are a million services for sharing files, but none of them are quite like PicoShare. Here are PicoShare's advantages:

\n\n

Run PicoShare

\n

From source

\n
PS_SHARED_SECRET=somesecretpass PORT=4001 \\\n  go run cmd/picoshare/main.go
\n

From Docker

\n

To run PicoShare within a Docker container, mount a volume from your local system to store the PicoShare sqlite database.

\n
docker run \\\n  --env \"PORT=4001\" \\\n  --env \"PS_SHARED_SECRET=somesecretpass\" \\\n  --publish 4001:4001/tcp \\\n  --volume \"${PWD}/data:/data\" \\\n  --name picoshare \\\n  mtlynch/picoshare
\n

From Docker + cloud data replication

\n

If you specify settings for a Litestream-compatible cloud storage location, PicoShare will automatically replicate your data.

\n

You can kill the container and start it later, and PicoShare will restore your data from the cloud storage location and continue as if there was no interruption.

\n
PORT=4001\nPS_SHARED_SECRET=\"somesecretpass\"\nLITESTREAM_BUCKET=YOUR-LITESTREAM-BUCKET\nLITESTREAM_ENDPOINT=YOUR-LITESTREAM-ENDPOINT\nLITESTREAM_ACCESS_KEY_ID=YOUR-ACCESS-ID\nLITESTREAM_SECRET_ACCESS_KEY=YOUR-SECRET-ACCESS-KEY\n\ndocker run \\\n  --publish \"${PORT}:${PORT}/tcp\" \\\n  --env \"PORT=${PORT}\" \\\n  --env \"PS_SHARED_SECRET=${PS_SHARED_SECRET}\" \\\n  --env \"LITESTREAM_ACCESS_KEY_ID=${LITESTREAM_ACCESS_KEY_ID}\" \\\n  --env \"LITESTREAM_SECRET_ACCESS_KEY=${LITESTREAM_SECRET_ACCESS_KEY}\" \\\n  --env \"LITESTREAM_BUCKET=${LITESTREAM_BUCKET}\" \\\n  --env \"LITESTREAM_ENDPOINT=${LITESTREAM_ENDPOINT}\" \\\n  --name picoshare \\\n  mtlynch/picoshare
\n

Notes:

\n\n

Using Docker Compose

\n

To run PicoShare under docker-compose, copy the following to a file called docker-compose.yml and then run docker-compose up.

\n
version: \"3.2\"\nservices:\n  picoshare:\n    image: mtlynch/picoshare\n    environment:\n      - PORT=4001\n      - PS_SHARED_SECRET=dummypass # Change to any password\n    ports:\n      - 4001:4001\n    command: -db /data/store.db\n    volumes:\n      - ./data:/data
\n

Parameters

\n

Command-line flags

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
FlagMeaningDefault Value
-dbPath to SQLite database\"data/store.db\"
\n

Environment variables

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Environment VariableMeaning
PORTTCP port on which to listen for HTTP connections (defaults to 4001).
PS_BEHIND_PROXYSet to \"true\" for better logging when PicoShare is running behind a reverse proxy.
PS_SHARED_SECRET(required) Specifies a passphrase for the admin user to log in to PicoShare.
\n

Docker environment variables

\n

You can adjust behavior of the Docker container by specifying these Docker-specific variables with docker run -e:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Environment VariableMeaning
LITESTREAM_BUCKETLitestream-compatible cloud storage bucket where Litestream should replicate data.
LITESTREAM_ENDPOINTLitestream-compatible cloud storage endpoint where Litestream should replicate data.
LITESTREAM_ACCESS_KEY_IDLitestream-compatible cloud storage access key ID to the bucket where you want to replicate data.
LITESTREAM_SECRET_ACCESS_KEYLitestream-compatible cloud storage secret access key to the bucket where you want to replicate data.
LITESTREAM_RETENTIONThe amount of time Litestream snapshots & WAL files will be kept (defaults to 72h).
\n

Docker build args

\n

If you rebuild the Docker image from source, you can adjust the build behavior with docker build --build-arg:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Build ArgMeaningDefault Value
litestream_versionVersion of Litestream to use for data replication0.3.9
\n

PicoShare's scope and future

\n

PicoShare is maintained by Michael Lynch as a hobby project.

\n

Due to time limitations, I keep PicoShare's scope limited to only the features that fit into my workflows. That unfortunately means that I sometimes reject proposals or contributions for perfectly good features. It's nothing against those features, but I only have bandwidth to maintain features that I use.

\n

Deployment

\n

PicoShare is easy to deploy to cloud hosting platforms:

\n\n

Tips and tricks

\n

Reclaiming reserved database space

\n

Some users find it surprising that when they delete files from PicoShare, they don't gain back free space on their filesystem.

\n

When you delete files, PicoShare reserves the space for future uploads. If you'd like to reduce PicoShare's usage of your filesystem, you can manually force PicoShare to give up the space by performing the following steps:

\n
    \n
  1. Shut down PicoShare.
    2. \n
  2. Run sqlite3 data/store.db 'VACUUM' where data/store.db is the path to your PicoShare database.
    3. \n
\n

You should find that the data/store.db should shrink in file size, as it relinquishes the space dedicated to previously deleted files. If you start PicoShare again, the System Information screen will show the smaller size of PicoShare files.

","updatedAt":"2025-05-21T16:15:48Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"Sync-Tools","color":"2f12e5"}},{"node":{"name":"mtlynch","color":"000506"}}]},"comments":{"edges":[]}}},"pageContext":{"number":436,"previous":{"title":"hipages/php-fpm_exporter: 用于 PHP-FPM 指标的 Prometheus Exporter","number":435},"next":{"title":"OpenAtomFoundation/pika: Pika 是一个以 RocksDB 为存储引擎的的大容量、高性能、多租户、数据可持久化的弹性 KV 数据存储系统，完全兼容 Redis 协议，支持其常用的数据结构。","number":437}}}, "staticQueryHashes": ["151096407","2861350382"]}