pkg.soopen package index

brew / rang 6709

Installer payara avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de payara pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install payara

local Homebrew formula metadata

aperçu

Résumé du paquet

Java EE application server forked from GlassFish

Commandes et alias

  • letsencrypt.py

historique

Historique du projet et usages

Payara Server is an open-source Jakarta EE and MicroProfile application server derived from GlassFish and developed for reliable development and deployment across on-premises, cloud, and hybrid environments.

Historique du projet

Payara Server began in 2014, derived from GlassFish 4.1 after commercial support for GlassFish changed. It was developed as a compatible application server with continued fixes, features, and production support.

The project subsequently evolved with newer GlassFish generations and the Java EE-to-Jakarta EE transition. Payara Server now describes itself as an open-source middleware platform for Jakarta EE and MicroProfile applications deployed on premises, in cloud environments, or in hybrid environments.

Payara Micro complements the full server with a lightweight runtime for command-line, containerized, and embedded deployments, while Payara Server retains domain administration and full application-server workflows.

Historique d'adoption

Payara Server was positioned as a supported, production-oriented successor for GlassFish users while retaining familiar Java EE administration and deployment concepts.

Its scope broadened with Jakarta EE, MicroProfile, cloud, container, and hybrid deployment support. The project is available as a community edition, while Payara also provides commercially supported enterprise distributions.

For application teams, its GlassFish lineage reduced migration friction; for operators, Payara added a maintained release and support model around the familiar domain-based server architecture.

Modes d'utilisation

Developers deploy WAR and EAR applications to Payara Server, administer domains with `asadmin` or the administration console, and configure resources in the domain model.

Operators use `domain.xml` as the central domain configuration, with adjacent logging and environment configuration files. Clusters, instances, data sources, security settings, and application deployments are managed through the server's administration facilities.

Payara Micro is used when the same ecosystem is needed in a smaller command-line or container-oriented runtime.

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

Payara is notable because it packages a large standards-driven Java runtime whose behavior is shaped by Jakarta EE compatibility, MicroProfile support, domain configuration, Maven artifacts, container images, and the GlassFish code lineage.

Its packaging history also captures the enterprise-Java transition from Java EE to Jakarta EE and the practical difference between an upstream reference implementation and a production-focused downstream distribution.

Chronologie

  • 2014: Payara Server began as a project derived from GlassFish 4.1.
  • 2015: The early Payara 4 line followed GlassFish-style versioning and compatibility.
  • 2018: Payara Server 5 adopted the GlassFish 5 and Java EE 8 generation.
  • Jakarta EE era: Payara evolved its platform around Jakarta EE, MicroProfile, containers, and cloud deployment.

Related projects

  • Eclipse GlassFish is the upstream lineage and closest migration reference point.
  • Jakarta EE and Eclipse MicroProfile define the principal application-platform APIs implemented by Payara.
  • Payara Micro is the lightweight runtime in the broader Payara Platform.

posture de sécurité

Niveau de risque : orange

formula declares a Homebrew service.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • formula declares a Homebrew service

Signaux

  • metadata:service

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de formule déclarent un service ou daemon.
  • 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
domain-dir/config/domain.xmlas-install/lib/templates/domain.xml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
domain-dir/master-passwordas_install/nodes/<node-name>/agent/master-password

exécutables

Exécutables installés

CommandeTypeExpositionNote
letsencrypt.pycliexé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-11-04
version du gestionnaire7.2026.10
gestionnaire mis à jour2026-10-14
données localesOK
amontnot checked
dernière version détectéenon détecté

https://www.payara.fish

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:payara
Version7.2026.10
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/payara
Page d'accueilhttps://www.payara.fish
Docs amonthttps://www.payara.fish
LicenceCDDL-1.1 OR (GPL-2.0-only WITH Classpath-exception-2.0)
Archive sourcehttps://search.maven.org/remotecontent?filepath=fish/payara/distributions/payara/7.2026.10/payara-7.2026.10.zip
Dernière mise à jour2026-10-14T13:06:56Z
Pulseupdated
Dépendancesopenjdk
Bouteilledisponible (sur all)
post-install Homebrewnon défini
Servicedeclared
PrécautionsYou may want to add the following to your .bash_profile: export GLASSFISH_HOME=$HOMEBREW_PREFIX/opt/payara/libexec/glassfish export PATH=${PATH}:${GLASSFISH_HOME}/bin

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namepayara
Version Scheme0
Revision0
Conflicts With
  • glassfish
Requirements
  • macos
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

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.

Sources utilisées

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation