☁
JEPFX CLOUD
Free unlimited hosting
Direct download · No expiry

Upload files, share direct links

Every link auto-downloads the file — perfect for scripts, installers, and assets.

📜
Files
0
💾
Storage used
0 B
⇩
Status
Checking…
⚠ Termux server offline. This link waits for your phone — start ./start.sh and it'll reconnect automatically, no need to refresh.
jepfx@cloud:~$
↑
Drop files here or click to browse
Any file type · Multiple files supported
🔍
0 selected
files tap a file to preview · ⋯ for more
⚙ Settings — API & Integration
Max upload size
—
Stored right now
—
This is everything another app, backend, or AI assistant needs to talk to this storage server: the endpoint plus the username/password sent as HTTP Basic Auth. Point any of your other websites here instead of relying on their own (wipeable) disk.
Changing this here updates the running server and is saved to a local config file, so it survives a normal restart. If this server runs on a host that wipes its disk on every redeploy (like Render's free tier), set JEPFX_USER / JEPFX_PASSWORD as real environment variables there instead so it sticks.
Paste the copied guide straight into an AI assistant (Claude, ChatGPT, etc.) along with something like "use this as the file storage backend for my app" — it has everything needed to wire up uploads/downloads without you explaining the API by hand.
Users you add can sign in with their own username/password, but only inside their own private folder — they never see yours or each other's.
Device storage
📱 Termux storage
Loading…
Pending requests Declined history
Loading…
Users
Loading…
Browse this project's own files below, just like GitHub's file browser, and upload a replacement for any file — it overwrites whatever already has that name in the folder you're viewing. Your uploaded files, user accounts, and login are never shown here and can never be touched from this tab.
Uploading a file with a name that already exists here backs it up first (to .jepfx-update/backups/) and then replaces it. A backend file like server.js needs Restart server afterwards to take effect — front-end files under public/ just take effect on next page load.
No files replaced yet.
Package this whole setup into a single .tar.gz you can pull onto another phone with one curl command — for moving to a new phone, cloning a spare one, or just keeping an offline backup. Admin only.
  1. On this phone: tick the box below if you want a full clone (your files, user accounts, and login) — leave it unticked to send over just the app.
  2. Copy the one-line migrate & deploy command further down this tab.
  3. On the new phone: install Termux (the F-Droid build, not Play Store), open it, and run pkg install curl tar once if either command isn't found yet.
  4. Paste the copied command into that Termux session and run it. It downloads the archive, extracts it into a fresh jepfx-cloud folder, runs install.sh (Node.js, cloudflared, npm install), and starts the server — all in one line.
  5. When it finishes you'll see the same local-address / public-link output as any normal ./start.sh — the new phone is now a live, independent copy. If you chose the full clone, your files and logins carried over too; otherwise it starts fresh with the default admin login (change it from this same Settings panel).
Package size
—
Items included
—
Both commands carry your admin password in plain text — paste them straight into the new phone's terminal and nowhere else. Use whichever address that phone can reach: your local network address on the same Wi-Fi, or the public/relay link from anywhere else. The migrate command already extracts, runs install.sh, and starts the server for you; the plain download just saves the .tar.gz so you can move/extract it yourself later.
A self-contained written copy of everything on this tab — the steps, both commands, and troubleshooting notes. Handy to send to yourself (chat/email/notes app) before you switch phones, or to paste into an AI assistant if something doesn't go as expected on the new end.