Best answer: use a web app that creates public HTTPS share links. Do not expose CasaOS or SMB to strangers. Choose Nextcloud for a full personal cloud, or Pingvin Share X for lightweight temporary download links.
Choose the sharing model first
| Goal | Better fit |
|---|---|
| Long-lived folders, accounts, mobile sync | Nextcloud |
| Temporary download links | Pingvin Share X |
| Your own remote access | VPN |
Nextcloud supports public link shares with passwords, expiration dates, upload permissions, and separate links with different rights.
The original Pingvin Share project is archived. Its own README points users toward the maintained Pingvin Share X, which supports link sharing, expiry, passwords, visitor limits, reverse shares, email recipients, and local/S3 storage.
Linkwarden is not the same tool
Linkwarden is primarily bookmark/web-archive software. It can preserve URLs, but that is different from hosting arbitrary files for someone else to download. A tool that creates links is not automatically a file-transfer service.
Publish only the file app
Once the app works on your LAN, expose that application over HTTPS. An outbound application tunnel is one option when you do not want inbound router ports.
Deployment checklist
- Mount a dedicated host folder into the app.
- Test a share on the LAN.
- Set a strong admin password.
- Set public-link expiry and passwords.
- Publish only the app through HTTPS.
- Test from mobile data.
- Confirm expired links stop working.
The self-hosted app catalog helps compare file/cloud apps. The private NAS access model explains why personal remote access and public sharing are different problems.
For multi-drive storage, ZimaCube 2 is relevant hardware, but share security remains an application/network decision.
Mount a dedicated share directory
Do not give a public file-transfer app unrestricted access to all of /DATA. Create a dedicated host directory, for example /DATA/PublicShares, and mount only that path into the app. This limits accidental exposure and makes backup/retention policy easier to reason about.
Choose link controls based on the data
- Expiration: use short-lived links for one-time transfers.
- Password: add one when the URL itself should not be enough.
- Download/view limits: useful for controlled handoffs when the app supports them.
- Upload permission: keep it off unless you intentionally want a file-drop workflow.
- Retention: decide whether expired files are deleted or merely made inaccessible.
A public URL should be treated as a credential. Anyone who receives or leaks it may be able to access the content until the link expires or is revoked.
Nextcloud is better when sharing is ongoing
Nextcloud becomes worthwhile when the same users return repeatedly, need shared folders, mobile clients, WebDAV, collaboration, or account-based permissions. It is heavier than a transfer tool, but the richer permission model is the point.
Pingvin Share X is better for handoffs
For “send these files to someone and let the link expire,” a transfer-oriented app is simpler. The maintained fork also supports local disk or S3-style storage, which lets you separate the application server from the file backend if needed.
Test from outside your LAN
After publishing the service, switch your phone to mobile data and test:
- the public hostname resolves;
- TLS is valid;
- the link opens without exposing the admin panel;
- password/expiry rules work;
- large downloads complete;
- an expired or revoked link fails as expected.
Back up the application state too
The shared files may live on a data disk, while user accounts, link metadata, expiration settings, and passwords live in an application database. Back up both if the shares need to survive a server failure.
FAQ
Can I expose a CasaOS folder with a public URL?
Use a file-sharing web application in front of the storage rather than exposing raw SMB or the dashboard.
Nextcloud or Pingvin Share X?
Nextcloud fits ongoing cloud-style collaboration; Pingvin Share X fits temporary transfers.
