Introduction
This package provides information about the host you are running buildout on.
Exposed Parameters
- hostname
The hostname of the machine buildout is running on, as returned by socket.gethostname()
- fqdn
The fully qualified domain of the machine buildout is running on, as return by socket.getfqdn(). If no fqdn is available, this will be the same as hostname.
- interface.X.address
The IP address of the network interface X.
- user.name
The name of the account running buildout
- user.uid
The uid running buildout. Numerical.
- user.gid
The gid running buildout. Numerical.
- user.home
The home directory of the user running buildout
- vcs.type
The type of checkout that buildout is being run from. Supports Mercurial (‘hg’), Git (‘git’) or Subversion (‘svn’), otherwise will be ‘unknown’.
- vcs.branch
The branch or that that buildout is being run from. Will be ‘unknown’ for unsupported VCS.
Using facts
This example uses the missingbits echo recipe to print information about the current machine:
[buildout]
parts = echo
[facts]
recipe = isotoma.recipe.facts
[echo]
recipe = missingbits:echo
echo =
The hostname is ${facts:hostname}
The fdqn is ${facts:fdqn}
The main IP address is ${facts:interface.eth0.address}
The VCS type is ${facts:vcs.type} and branch is ${facts:vcs.branch}
The user is ${facts:user.name} and their home dir is ${facts:user.home}
Changelog
0.0.8 (2015-04-15)
Nothing changed yet.
0.0.7 (2014-03-12)
fix bug when using without any vcs [djay]
fix bug when interface name includes a ‘:’ [djay]
0.0.6 (2012-02-10)
Added support for Mercurial VCS
0.0.5 (2012-02-03)
Force english locale so the ‘svn info’ output is parseable everywhere
0.0.4 (2012-02-03)
Set lsb.codename and other lsb properties so we can make decisions base on the distro version.
0.0.3 (2011-08-30)
Set user.name, user.home, user.uid and user.gid facts
Set vcs.branch and vcs.type even if the cwd isn’t Git or SVN.
0.0.2 (2011-08-22)
Add Git branch detection
0.0.1 (2011-08-11)
Detect information about vcs
0.0.0 (2011-08-09)
Initial version
Ability to get fqdn, hostname and ip addresses (by eth name)
Metadata
Release files for isotoma.recipe.facts 0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| isotoma.recipe.facts-0.0.8.zip | 9.5 kB | Without provenance | Details for isotoma.recipe.facts-0.0.8.zip |
Release files / isotoma.recipe.facts-0.0.8.zip
| Download URL | isotoma.recipe.facts-0.0.8.zip |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d18de48d223cc6275d230c5269e17dff2435c5c88807c2bafb80a5baa4fcabf
|
|
BLAKE2b-256 checksum How to use checksums |
8d60b8a174029c2e0e7e9ef1e81849e9a20033555013999fc94b7153132471a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for isotoma.recipe.facts 0.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.