Just curious, what about scp-ing to your server is less than ideal for you? I would think a static server with nginx or similar would be an easy one time setup and then you do a single command to scp to it whenever you want to add images. No redeploy necessary. I would almost consider that easier than other bespoke solutions that you would have to learn
post
Can you encode them as base64 URL?
There is also copyparty. Spin up the docker container, upload your images, copy/paste the links, boom.
You could throw Garage or Minio in a container and upload the images to a public bucket.
Yes, you can expose a bucket as a website for easy access.
Yep) My program for that purpose: https://codeberg.org/nykula/imgie - resurrected three months ago because another person on PieFed reminded me of it. Should just work. Ping me if it doesn't.
Doood. npm in production is a bad pattern in this age of supply-chain sploits. Best vendor that into the artifact when ya ship .... Nevermind.
(See: iso27002, SLSA.dev)
I can make a Docker image, like the one I made for Lanquiz. It's not high on my to do list, though. Before that, I want to update integration tests (working draft still not committed), and store data under system-specific paths not in repo subdirectories (breaking change).
Things like Immich or Nextcloud are far too much for what I need, I basically just need a password-protected upload interface and the ability to grab the direct links to the images to embed them.
Why do you care that they do things you don't need if they also do what you need?
Because these do just what you need and do it well.
On my homelab I don't mind so much as I have 64gb of ram and and 8tb of storage, but on my vps I want everything to be relatively lightweight
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| SFTP | Secure File Transfer Protocol for encrypted file transfer, over SSH |
| SSH | Secure Shell for remote terminal access |
| VPS | Virtual Private Server (opposed to shared hosting) |
| nginx | Popular HTTP server |
[Thread #45 for this comm, first seen 7th Jul 2026, 08:30] [FAQ] [Full list] [Contact] [Source code]
I personally do ShareX, with an SFTP destination for an nginx webserver. It has an image editor built in as part of the workflow if you enable it, and it can automatically copy the clipboard URL.
You could certainly go the extra mile and setup an image sharing manager or a more complicated solution if you wanted to though, if that makes overall administration easier.
Honestly, filebrowser or filebrowser quantum are what you need. Essentially a web UI frontend for sftp / sshfs. Really simple light weight.
https://github.com/andrii-kryvoviaz/slink from https://selfh.st/apps/?tag=Image+Sharing
https://github.com/mtlynch/picoshare from https://selfh.st/apps/?tag=File+Sharing
Seems like these could fit the bill.
Thanks, I decided to go with Slink. It looks lightweight enough, easy to set up and while not quite as minimal as I was imagining, that image resize ability when generating shared links could come in useful
@SpatchyIsOnline @darcmage that’s a great choice. Any plan how will you deploy it on your server and keep watch for CPU?
I already have it up and running! They have a good docker-compose example on their site.
As for monitoring, my approach is to use it and if it works, then there's nothing to worry about 😅
all 28 comments