Download the PHP package ramon/backup without Composer
On this page you can find all versions of the php package ramon/backup. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package backup
📦 Backup & Migration — Portable Backups for Flarum
A complete backup, export and import system for Flarum 2.x
About the Project
Backup & Migration is a full-featured backup and migration extension I've been
building for Flarum, inspired by All-in-One WP Migration but written from
scratch with a Flarum-native format. It bundles your forum into a single
portable .flarum file — database, uploads, storage, and any installed
extensions (workbench or vendor) — and restores it on the same install or a
different one with one click.
It started from my own need to migrate forums between hosts without the manual mysqldump-and-zip dance, and grew into a complete suite covering encryption, cross-server transfer, per-extension picking, and automatic URL rewriting.
✨ Highlights
- Single portable
.flarumfile — custom streaming format (not.wpress, not zip), forward-only so multi-GB backups never need to fit in memory - Pick what to bundle — database,
public/assets,storage, and individual extensions, with a tag on each row showing whether it lives inworkbench/or invendor/(composer-managed) composer.json+composer.locktravel along — vendor extensions stay reproducible on the destination- Resumable, chunked progress on both export and import (~4 MB per HTTP
request), with live progress bars and an upload
%indicator - Command-line export & import — run a full backup or restore from
php flarum backup:export/backup:import, with nomax_execution_timeormemory_limitworries and no browser tab to keep open; ideal for large forums, cron jobs and scripted server-to-server transfer - Optional asymmetric encryption — libsodium hybrid scheme: sealed-box
wraps a per-archive XChaCha20-Poly1305 stream key. Public key in the database,
private key only in
config.php - Cross-server transfer — encrypt to a foreign public key, paste the matching private key at import time
- Automatic URL rewriting — the source URL is recorded in the archive
header and rewritten across
settings,posts.contentandposts.parsed_contentwhen restoring on a different host - Selectable restore — per-section and per-extension checkboxes populated from the archive's manifest
- Foreign-key-safe restore — disables FK checks per tick so DDL referencing not-yet-created tables succeeds without ordering dance
- Smart pruning while scanning (
node_modules,.git,.idea, nestedvendor/…) so workbench scans stay seconds-fast - Dedicated "you've been logged out" screen when a DB restore replaces the admin's session
🛠️ Technologies
- PHP 8.1+ — resumable export / import jobs, libsodium crypto, MySQL dumper
- TypeScript + Mithril — admin panel UI
- LESS — styling (theme-aware via Flarum's CSS variables)
- libsodium — sealed-box + secretstream chunked encryption
Installation
Then enable Backup & Migration under the Extensions page in the admin panel.
🖥️ Command-line interface (CLI)
Export and import are also available as console commands. A CLI run has no HTTP
request timeout, no memory_limit pressure from a web worker, and doesn't
depend on keeping a browser tab open — so the CLI is the most reliable way to
back up or migrate large forums, and the natural fit for cron jobs and
scripted server-to-server transfer. Under the hood it drives the exact same
engine as the admin panel, simply looped to completion in a single process.
Export — backup:export
Options: --db/--no-db (default on), --assets, --storage,
--extensions[=LIST] (omit the value for all installed extensions),
--all, --target=mysql|mariadb|postgres|sqlite (defaults to the source
engine), --encrypt, --public-key=…, -o, --output=PATH.
Import — backup:import
⚠️ A restore replaces the destination database and files, so
backup:importrefuses to run without the explicit--yesflag.
Options: -y, --yes (required), --private-key=…, --db/--no-db,
--assets/--no-assets, --storage/--no-storage, --extensions[=LIST]. With no
selection flags, the entire archive is restored.
A typical server-to-server migration:
Links
- GitHub: github.com/ram0ng1/backup
- Packagist: packagist.org/packages/ramon/backup
- Issues: github.com/ram0ng1/backup/issues
- Donate: Stripe
License
MIT
Built with ❤️ by Ramon Guilherme
A personal project focused on making it easier to back up, move and restore Flarum communities — without leaving the admin panel.
