# Format of the progress bars used. # See https://docs.rs/indicatif/0.15.0/indicatif/#templates # for how to customize this. # # Note that 40 is a nice width for the bar itself here, because that's 63 # characters before the actually {msg}, which gives the message enough space to # fit a 80 or 100 character wide terminal! # # This is also the default if the setting is not present. progress_format = "[{elapsed_precise}] ({percent:>3}%): {bar:40.cyan/blue} | {msg}" # The shebang line used when compiling the packaging scripts # Default if this value is not set is "#!/bin/bash". # Can be overwritten temporarily via CLI script_shebang = "#!/bin/bash" # The theme for the highlighting engine when printing the script that ran inside # a container. # # Valid values: # "base16-ocean.dark" # "base16-eighties.dark" # "base16-mocha.dark" # "base16-ocean.light" # "InspiredGitHub" # "Solarized (dark)" # "Solarized (light)" # # If the value is not set, highlighting is disabled. script_highlight_theme = "Solarized (dark)" # The format to print the found packages with. # # Possible tokens are: # i - Incrementing number of package that is printed # p - The package data # print_system_deps - boolean flag to use in format string, true if user wants to see system deps # print_system_runtime_deps - boolean flag to use in format string, true if user wants to see system runtime deps # print_build_deps - boolean flag to use in format string, true if user wants to see build deps # print_runtime_deps - boolean flag to use in format string, true if user wants to see runtime deps # # Handlebars modifiers are available. package_print_format = "" # The position of the release binaries # # butido checks this location for packages when installing dependencies # releases = "/tmp/releases" # The position of the staging binaries # butido rolls a dice for each submitted build and generates a # per-process-staging directory here to store intermediate builds. # staging = "/tmp/staging" # Enable strict script interpolation # # If this is set to true, the variable interpolation for the packaging script # will be done in strict mode. # Strict mode means, that referencing a variable that does not exist, will # result in a rendering error. # # Default if this setting is missing is true # strict_script_interpolation = true # #### # # Log database configuration # # #### # The database to use # # Can be overridden via environment vairbale BUTIDO_DATABASE_URI or set via CLI. database_host = "localhost" database_port = 5432 database_user = "pgdev" database_password = "password" database_name = "butido" # Phases which can be configured in the packages # This also defines the _order_ in which the phases are executed # Each phase gets a pre_ and a post_ phase added automatically. # So for [ "foo", "bar" ], the phases are executed in this order: # pre_foo # foo # post_foo # pre_bar # bar # post_bar # # Phases which are not listed here are not executed at all. available_phases = [ "unpack", "patch", "configure", "build", "fixup", "pack" ] [docker] # Images which can be used to build # images not listed here are automatically rejected images = [ "debian:bullseye" ] # # Verify whether the requested images are present # # This setting is twofold: # First, it checks whether the image requested on the commandline (when # building) is actually in the whitelist (`docker.images` setting in the # configuration file). # Second, it checks that every used endpoint actually has the requested image # present. # This check is done when setting up the connection to the endpoints, so this # will fail _before_ any actual building starts. # verify_images_present = true # List of docker endpoints [[docker.endpoints]] name = "testhostname" uri = "http://0.0.0.0:8095" endpoint_type = "http" speed = 1 maxjobs = 1 [containers] # environment variables which are allowed during container start # This way, errors (typos) when passing environment to a build can be prevented allowed_env = [ "PATH" ]