MythicBeasts :: Let’s Encrypt client and ACME library written in Go.
Author: Lego Team
Description: Configuration for MythicBeasts.
Date: 2019-03-03T16:39:46+01:00

# MythicBeasts

Configuration for MythicBeasts.

- Code: `mythicbeasts`
- Since: v0.3.7

Here is an example bash command using the MythicBeasts provider:

    MYTHICBEASTS_USERNAME=myuser \
    MYTHICBEASTS_PASSWORD=mypass \
    lego --email you@example.com --dns mythicbeasts -d '*.example.com' -d example.com run

## Credentials

Environment Variable Name | Description
--- | ---
`MYTHICBEASTS_PASSWORD` | Password
`MYTHICBEASTS_USERNAME` | User name

The environment variable names can be suffixed by `_FILE` to reference a file instead of a value. More information here.

## Additional Configuration

Environment Variable Name | Description
--- | ---
`MYTHICBEASTS_API_ENDPOINT` | The endpoint for the API (must implement v2)
`MYTHICBEASTS_AUTH_API_ENDPOINT` | The endpoint for Mythic Beasts’ Authentication
`MYTHICBEASTS_HTTP_TIMEOUT` | API request timeout in seconds (Default: 10)
`MYTHICBEASTS_POLLING_INTERVAL` | Time between DNS propagation check in seconds (Default: 2)
`MYTHICBEASTS_PROPAGATION_TIMEOUT` | Maximum waiting time for DNS propagation in seconds (Default: 60)
`MYTHICBEASTS_TTL` | The TTL of the TXT record used for the DNS challenge in seconds (Default: 120)

The environment variable names can be suffixed by `_FILE` to reference a file instead of a value. More information here.

If you are using specific API keys, then the username is the API ID for your API key, and the password is the API secret.

Your API key name is not needed to operate lego.

## More information

- API documentation