installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%

brew install flyway

local Homebrew formula metadata

MacPortsvérifié · 94%

sudo port install flyway

MacPorts ports tree · java/flyway/Portfile · Source: api.github.com

Linux

Nixvérifié · 92%

nix profile install nixpkgs#flyway

nixpkgs package indexes · pkgs/by-name/fl/flyway/package.nix · Source: api.github.com

Windows

Scoopvérifié · 92%

scoop install main/flyway

Scoop official bucket manifest trees · bucket/flyway.json · Source: api.github.com

aperçu

Résumé du paquet

Database version control to control migrations

Liens du projet

Commandes et alias

flyway

historique

Historique du projet et usages

Redgate Flyway is a database migration and schema versioning tool for command-line, API, Maven, Gradle, Docker, and desktop workflows. It applies versioned migrations, records them in a schema history table, and is used to bring database change management into application-style CI/CD pipelines.

Historique du projet

The open-source repository identifies Flyway as a Redgate project and carries copyright from 2010 through 2026. The README emphasizes a simple, focused migration model and lists support across Windows, macOS, Linux, Docker, Java, Maven, and Gradle.

Redgate documentation presents Flyway as part of a wider product family that includes Flyway Command Line, Flyway Desktop, APIs, build-tool integrations, and Redgate editions. The GitHub README also notes that Flyway is a registered trademark of Boxfuse GmbH owned by Red Gate Software Ltd.

Historique d'adoption

Flyway's adoption is tied to the rise of database DevOps: its own documentation says it extends DevOps to databases, automates database deployments, and is commonly used from the command line in CI/CD systems. The README lists support for 50-plus DBMS products and many community or third-party integrations, including Spring Boot, SBT, Ant, Grails, Play, DropWizard, Grunt, Griffon, and Ninja.

Modes d'utilisation

The standard workflow is to create ordered SQL, Java, or scripting migrations, run Flyway against a database, and let it create or update the `flyway_schema_history` table as migrations are applied. It can be used directly through the CLI, embedded through the Java API, or driven through Maven and Gradle.

Pourquoi les passionnés de paquets s'y intéressent

Flyway matters to package ecosystems because it is both a standalone CLI and a Java library/plugin stack. It bridges application release tooling and mutable database state, so packaging has to serve local developer installs, CI runners, containers, build plugins, and enterprise editions without confusing the open-source command-line engine with Redgate's commercial surfaces.

Chronologie

2010: The Flyway open-source repository's copyright period begins.
2021: Redgate Flyway documentation was published in its current documentation space.
2022: Redgate published the Flyway Engine release-notes page in the current documentation system.
2024: The GitHub release stream included Flyway 10.x releases.
2026: Redgate documentation listed Flyway 12.10.0 as a current engine release.

Related projects

Related official surfaces include Flyway Desktop, Flyway Command Line, Flyway Java API, the Maven and Gradle plugins, flyway-community-db-support, and Redgate's commercial Flyway editions.

Sources

posture de sécurité

Aucune couverture d'outil protégé trouvée pour le moment

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour flyway. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.

Comportement d'installation

Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
Les métadonnées de bottle Homebrew sont disponibles pour 1 plateformes.
S’installe avec 1 dépendances d’exécution.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: ./flyway.toml./flyway.conf~/flyway.conf<flyway-install-dir>/conf/flyway.conf

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: ~/flyway.conf

exécutables

Exécutables installés

Commande	Type	Exposition	Note
`flyway`	cli	exécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-08

version du gestionnaire12.10.0

gestionnaire mis à jour2026-06-30

données localesOK

amontnot checked

dernière version détectéenon détecté

https://github.com/flyway/flyway

infoNo cached GitHub release or tag data was available.https://github.com/flyway/flywayconfiance none

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	brew:flyway
Version	12.10.0
Gestionnaire de paquets	Homebrew
Page du gestionnaire de paquets	https://formulae.brew.sh/formula/flyway
Page d'accueil	https://www.red-gate.com/products/flyway/community/
Dépôt	https://github.com/flyway/flyway
Docs amont	https://documentation.red-gate.com/flyway
Licence	Apache-2.0
Archive source	https://github.com/flyway/flyway/releases/download/flyway-12.10.0/flyway-commandline-12.10.0.tar.gz
Dernière mise à jour	2026-06-30T12:28:44Z
Pulse	updated
Dépendances	openjdk
Bouteille	disponible (sur all)
post-install Homebrew	non défini
Service	aucun déclaré

faits du registre

Détails de la base source

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	flyway
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

flyway

nix profile install nixpkgs#flyway

normalized package name match
Correspondance par : Flyway

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/fl/flyway/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

MacPorts95%

flyway

sudo port install flyway

normalized package name match
Correspondance par : Flyway

MacPorts ports tree · api.github.com · MacPorts ports tree: java/flyway/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Scoop95%

main/flyway

scoop install main/flyway

normalized package name match
Correspondance par : Flyway

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/flyway.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/flyway.yml

Sources utilisées

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Installer flyway avec Homebrew, MacPorts, Nix, scoop