(define-module (skylar services)
  #:use-module (skylar packages)
  #:use-module (gnu services)
  #:use-module (gnu services configuration)
  #:use-module (gnu services shepherd)
  #:use-module (guix gexp)
  #:export (gotosocial-configuration
        gotosocial-service-type))

(define (yaml-serialize field-name value)
  #~(string-append #$field-name ": " #$value))

(define (gts-serialize-string field-name value)
  (yaml-serialize field-name (string-append  "\"" value "\"")))
(define (gts-serialize-boolean field-name value)
  (yaml-serialize field-name (if value "true" "false")))
(define (gts-serialize-integer field-name value)
  (yaml-serialize field-name (number->string value)))
(define (gts-serialize-list-of-strings field-name value)
  (yaml-serialize field-name (apply string-append
                    (map (lambda (s) (string-append "\n  - \"" s "\""))
                     value))))

(define-configuration gotosocial-configuration
  (log-level
   (string "info")
   "String. Log level to use throughout the application. Must be lower-case.
Options: @code{[\"trace\",\"debug\",\"info\",\"warn\",\"error\",\"fatal\"]}")
  (log-db-queries
   (boolean #f)
   "Boolean. Log database queries when log-level is set to debug or trace. This setting produces verbose logs, so it's better to only enable it when you're trying to track an issue down.
Default: #f")
  (application-name
   (string "gotosocial")
   "String. Application to use internally.
Examples: @code{[\"My Application\", \"gotosocial\"]}
Default: \"gotosocial\"")
  (landing-page-user
   (string "")
   "String. The user that will be shown instead of the landing page. An empty string means that the landing page will be shown.
Example: \"admin\"
Default: \"\"")
  (host
   (string "localhost")
   "String. Hostname this server will be reachable at. Defaults to localhost for local testing, but you should @emph{definitely} change this when running for real, or your server won't work at all.
DO NOT change this after your server has already run once, or you will break things!
Examples: [\"gts.example.org\", \"some.server.com\"]
Default: \"localhost\"")
  (account-domain
   (string "")
   "String. Domain to use when federating profiles. This is useful when you want your server to be at eg., \"gts.example.org\", but you want the domain on accounts to be \"example.org\" because it looks better or is just shorter/easier to remember.

To make this setting work properly, you need to redirect requests at \"example.org/.well-known/webfinger\" to \"gts.example.org/.well-known/webfinger\" so that GtS can handle them properly.

You should also redirect requests at \"example.org/.well-known/nodeinfo\" in the same way. An empty string (ie., not set) means that the same value as 'host' will be used.

DO NOT change this after your server has already run once, or you will break things!

Please read the appropriate section of the installation guide before you go messing around with this setting: @{url https://docs.gotosocial.org/installation_guide/advanced/#can-i-host-my-instance-at-fediexampleorg-but-have-just-exampleorg-in-my-username}

Examples: [\"example.org\",\"server.com\"]
Default: \"\"")
  (protocol
   (string "https")
   "String. Protocol to use for the server. Only change to http for local testing!
This should be the protocol part of the URI that your server is actually reachable on. So even if you're running GoToSocial behind a reverse proxy that handles SSL certificates for you, instead of using built-in letsencrypt, it should still be https.
Options: [\"http\",\"https\"]
Default: \"https\"")
  (bind-address
   (string "0.0.0.0")
   "String. Address to bind the GoToSocial server to. This can be an IPv4 address or an IPv6 address (surrounded in square brackets), or a hostname. The default value will bind to all interfaces, which makes the server accessible by other machines. For most setups there is no need to change this.
If you are using GoToSocial in a reverse proxy setup with the proxy running on the same machine, you will want to set this to \"localhost\" or an equivalent, so that the proxy can't be bypassed.
Examples: [\"0.0.0.0\", \"172.128.0.16\", \"localhost\", \"[::]\", \"[2001:db8::fed1]\"]
Default: \"0.0.0.0\"")
  (port
   (integer 8080)
   "Int. Listen port for the GoToSocial webserver + API. If you're running behind a reverse proxy and/or in a docker, container, just set this to whatever you like (or leave the default), and make sure it's forwarded properly.
If you are running with built-in letsencrypt enabled, and running GoToSocial directly on a host machine, you will probably want to set this to 443 (standard https port), unless you have other services already using that port.
This *MUST NOT* be the same as the letsencrypt port specified below, unless letsencrypt is turned off.
Examples: [443, 6666, 8080]
Default: 8080")
  (trusted-proxies
   (list-of-strings '("127.0.0.1/32" "::1"))
   "List of strings. CIDRs or IP addresses of proxies that should be trusted when determining real client IP from behind a reverse proxy.
If you're running inside a Docker container behind Traefik or Nginx, for example, add the subnet of your docker network, or the gateway of the docker network, and/or the address of the reverse proxy (if it's not running on the host network).
Example: [\"127.0.0.1/32\", \"172.20.0.1\"]
vDefault: [\"127.0.0.1/32\", \"::1\"] (localhost ipv4 + ipv6)")
  (db-type
   (string "postgres")
   "String. Database type.
Options: [\"postgres\", \"sqlite\"]
Default: \"postgres\"")
  (db-address
   (string "")
   "String. Database address or parameters.

For Postgres, this should be the address or socket at which the database can be reached.

For Sqlite, this should be the path to your sqlite database file. Eg., /opt/gotosocial/sqlite.db. If the file doesn't exist at the specified path, it will be created. If just a filename is provided (no directory) then the database will be created in the same directory as the GoToSocial binary.

If address is set to :memory: then an in-memory database will be used (no file). WARNING: :memory: should NOT BE USED except for testing purposes.

Examples: [\"localhost\",\"my.db.host\",\"127.0.0.1\",\"192.111.39.110\",\":memory:\", \"sqlite.db\"]
Default: \"\"")
  (db-port
   (integer 5432)
   "Integer. Port for database connection.
Default: 5432")
  (db-user
   (string "")
   "String. Username for the database connection.
Examples: [\"mybduser\", \"postgres\", \"gotosocial\"]
Default: \"\"")
  (db-password
   (string "")
   "String. Password to use for the database connection.
Default: \"\"")
  (db-database
   (string "gotosocial")
   "String. Name of the database to use within the provided database type.
Default: \"gotosocial\"")
  (db-tls-mode
   (string "disable")
   "String. Disable, enable, or require SSL/TLS connection to the database.
If \"disable\" then no TLS connection will be attempted.
If \"enable\" then TLS will be tried, but the database certificate won't be checked (for self-signed certs).
If \"require\" then TLS will be required to make a connection, and a valid certificate must be presented.
Default: \"disable\"")
  (db-tls-ca-cert
   (string "")
   "String. Path to a CA certificate on the host machine for db certificate validation. If this is left empty, just the host certificates will be used. If filled in, the certificate will be loaded and added to host certificates.")
  (db-max-open-conns-multiplier
   (integer 8)
   "Integer. Number to multiply by CPU count to set permitted total of open database connections (in-use and idle).
You can use this setting to tune your database connection behavior, though most admins won't need to touch it.

Example values for multiplier 8:

1 cpu = 08 open connections
2 cpu = 16 open connections
4 cpu = 32 open connections

Example values for multiplier 4:

1 cpu = 04 open connections
2 cpu = 08 open connections
4 cpu = 16 open connections

A multiplier of 8 is a sensible default, but you may wish to increase this for instances running on very performant hardware, or decrease it for instances using v. slow CPUs.

If you set the multiplier to less than 1, only one open connection will be used regardless of cpu count.

PLEASE NOTE!!: This setting currently only applies for Postgres. SQLite will always use 1 connection regardless pof what is set here. This behavior will change in future when we implement better SQLITE_BUSY handling.
See @url{https://github.com/superseriousbusiness/gotosocial/issues/1407 for more details.}

Examples: [16, 8, 10, 2]
Default: 8")
  (db-sqlite-journal-mode
   (string "WAL")
   "String. SQLite journaling mode. SQLite only -- unused otherwise. If set to empty string, the sqlite default will be used. See: @url{https://www.sqlite.org/pragma.html#pragma_journal_mode}
Examples: [\"DELETE\", \"TRUNCATE\", \"PERSIST\", \"MEMORY\", \"WAL\", \"OFF\"]
Default: \"WAL\"")
  (db-sqlite-synchronous
   (string "NORMAL")
   "String. SQLite synchronous mode. SQLite only -- unused otherwise. If set to empty string, the sqlite default will be used. See: @url{https://www.sqlite.org/pragma.html#pragma_synchronous}
Examples: [\"OFF\", \"NORMAL\", \"FULL\", \"EXTRA\"]
Default: \"NORMAL\"")
  (db-sqlite-cache-size
   (string "8MiB")
   "String describing a valid byte size. SQLite cache size. SQLite only -- unused otherwise. If set to empty string or zero, the sqlite default (2MiB) will be used.
See: @url{https://sqlite.org/pragma.html#pragma_cache_size}
Examples: [\"0\", \"2MiB\", \"8MiB\", \"64MiB\"]
Default: \"8MiB\"")
  (db-sqlite-busy-timeout
   (string "5m")
   "Duration. SQlite busy timeout. SQLite only -- unused otherwise. If set to empty string or zero, the sqlite default will be used. See: @url{https://www.sqlite.org/pragma.html#pragma_busy_timeout}
Examples: [\"0s\", \"1s\", \"30s\", \"1m\", \"5m\"]
Default: \"5m\"")
  ;;
  ;; TODO: database cache
  ;;
  (web-template-base-dir
   (string "./web/template/")
   "String. Directory from which gotosocial will attempt to load html templates (.tmpl files).
Default: \"./web/template/\"")
  (web-asset-base-dir
   (string "./web/assets/")
   "String. Directory from which gotosocial will attempt to serve static web assets (images, scripts.
Defualt: \"./web/assets/\"")
  (instance-expose-peers
   (boolean #f)
   "Boolean. Allow unauthenticated users to make queries to /api/v1/instance/peers?filter=open in order to see a list of instances that this instance 'peers' with. Even if set to 'false', then authenticated users (members of the instance) will still be able to query the endpoint.
Default: #f")
  (instance-expose-suspended
   (boolean #f)
   "Boolean. Allow unauthenticated users to make queries to /api/v1/instance/peers?filter=suspended in order to see a list of instances that this instance blocks/suspends. This will also allow unauthenticated users to see the list through the web UI. Even if set to 'false', then authenticated users (members of the instance) will still be able to query the endpoint.
Default: #f")
  (instance-expose-suspended-web
   (boolean #f)
   "Boolean. Allow unauthenticated users to view /about/suspended, showing the HTML rendered list of instances that this instance blocks/suspends.
Default: #f")
  (instance-expose-public-timeline
   (boolean #f)
   "Boolean. Allow unauthenticated users to make queries to /api/v1/timelines/public in order to see a list of public posts on this server. Even if set to 'false', then authenticated users (members of this instance) will still be able to query the endpoint.
Default: #f")
  (instance-deliver-to-shared-inboxes
   (boolean #t)
   "Boolean. This flag tweaks whether GoToSocial will deliver ActivityPub messages to the shared inbox of a recipient, if one is available, instead of delivering each message to each actor who should receive a message individually.

Shared inbox delivery can significantly reduce network load when delivering to multiple recipients share an inbox (eg., on large Mastodon instances).

See: @url{https://www.w3.org/TR/activitypub/#shared-inbox-delivery}

Default: #t")
  (accounts-registration-open
   (boolean #t)
   "Boolean. Do we want people to be able to just submit sign up requests, or do we want invite only?
Default: #t")
  (accounts-approval-required
   (boolean #t)
   "Boolean. Do sign up requests require approval from an admin/moderator before an account can sign in/use the server?
Default: #t")
  (accounts-reason-required
   (boolean #t)
   "Boolean. Are sign up requests required to submit a reason for the request (eg., an explanation of why they want to join the instance)?
Default: #t")
  (accounts-allow-custom-css
   (boolean #f)
   "Boolean. Allow accounts on this instance to set custom CSS for their profile pages and statuses. Enabling this setting will allow accounts to upload custom CSS via the /user settings page, which will then be rendered on the web view of the account's profile and statuses.

For instances with public sign ups, it is **HIGHLY RECOMMENDED** to leave this setting on 'false', since setting it to true allows malicious accounts to make their profile pages misleading, unusable or even dangerous to visitors. In other words, you should only enable this setting if you trust the users on your instance not to produce harmful CSS.

Regardless of what this value is set to, any uploaded CSS will not be federated to other instances, it will only be shown on profiles and statuses on *this* instance.

Default: #f")
  (media-image-max-size
   (integer 10485760)
   "Integer. Maximum allowed upload size in bytes.
Default: 10485760 -- aka 10MB")
  (media-video-max-size
   (integer 41943040)
   "Integer. Maximum allowed video upload size in bytes.
Default: 41943040 -- aka 40MB")
  (media-description-min-chars
   (integer 0)
   "Integer. Minimum amount of characters required as an image or video description.
Default: 0 (not required)")
  (media-description-max-chars
   (integer 500)
   "Integer. maximum amount of characters permitted in an image or video description.
Default: 500")
  (media-remote-cache-days
   (integer 30)
   "Integer. Number of days to cache media from remote instances before they are removed from the cache. A job will run every day at midnight to clean up any remote media older than the given amount of days.

When remote media is removed from the cache, it is deleted from storage but the database entries for the media are kept so that it can be fetched again if requested by a user.

If this is set to 0, then media from remote instances will be cached indefinitely.
Examples: [30, 60, 7, 0]
Default: 30")
  (media-emoji-local-max-size
   (integer 51200)
   "Integer. Max size in bytes of emojis uploaded to this instance via the admin API. The default is the same as the Mastodon size limit for emojis (50kb), which allows for good interoperability. Raising this limit may cause issues with federation of your emojis to other instances, so beware.
Default: 51200")
  (media-emoji-remote-max-size
   (integer 102400)
   "Int. Max size in bytes of emojis to download from other instances. By default this is 100kb, or twice the size of the default for media-emoji-local-max-size. This strikes a good balance between decent interoperability with instances that have higher emoji size limits, and not taking up too much space in storage.
Default: 102400")
  (storage-backend
   (string "local")
   "String. Type of storage backend to use for user-created uploads (videos, images, etc).
Examples: [\"local\", \"s3\"]
Default: \"local\" (storage on local disk")
  (storage-local-base-path
   (string "/gotosocial/storage")
   "String. Directory to use as a base path for storing files. Make sure whatever user/group gotosocial is running as has permission to access this directory, and create new subdirectories and files within it.
Only required when running with the local storage backend.
Examples: [\"/home/gotosocial/storage\", \"/opt/gotosocial/datastorage\"]
Default: \"/gotosocial/storage\"")
  (storage-s3-endpoint
   (string "")
   "String. API endpoint of the S3 compatible service. Only required when running with the s3 storage backend.
Default: \"\"")
  (storage-s3-proxy
   (boolean #f)
   "Boolean. If data stored in S3 should be proxied through GoToSocial instead of redirecting to a presigned URL.
Default: #f")
  (storage-s3-use-ssl
   (boolean #t)
   "Boolean. Use SSL for S3 connections. Only set to #f when testing locally.
Default: #t")
  (storage-s3-access-key
   (string "")
   "String. Access key part of the S3 credentials. Consider setting this value using environment variables to avoid leaking it via the config file. Only required when running with the s3 storage backend.
Default: \"\"")
  (storage-s3-secret-key
   (string "")
   "String. Secret part of the S3 credentials. Consider setting this value using environment variables to avoid leaking it via the config file. Only required when running with the s3 storage backend.
Default: \"\"")
  (storage-s3-bucket
   (string "")
   "String. Name of the storage bucket. If you have already encoded your bucket name in the storage-s3-endpoint, this value will be used as a directory containing your data. This bucket must exist prior to starting GoToSocial. Only required when running with the s3 storage backend.
Default: \"\"")
  (statuses-max-chars
   (integer 5000)
   "Integer. Maximum amount of characters permitted for a new status. Note that going way higher than the default might break federation.
Default: 5000")
  (statuses-cw-max-chars
   (integer 100)
   "Integer. Maximum amount of characters allowed in the CW/subject header of a status. Note that going way higher than the default might break federation.
Default: 100")
  (statuses-poll-max-options
   (integer 6)
   "Integer. Maximum amount of options to permit when creating a new poll. Note that going way higher than the default might break federation.
Default: 6")
  (statuses-poll-option-max-chars
   (integer 50)
   "Integer. Maximum amount of characters to permit per poll option when creating a new poll. Note that going way higher than the default might break federation.
Default: 50")
  (statuses-media-max-files
   (integer 6)
   "Integer. Maximum amount of media files that can be attached to a new status. Note that going way higher than the default might break federation.
Default: 6")
  (letsencrypt-enabled
   (boolean #f)
   "Boolean. Whether or not letsencrypt should be enabled for the server. If false, the rest of the letsencrypt settings will be ignored. If you serve GoToSocial behind a reverse proxy like nginx or traefik, leave this turned off. If you don't, then turn it on so that you can use https.

Default: #f")
  (letsencrypt-port
   (integer 80)
   "Int. Port to listen for letsencrypt certificate challenges on. If letsencrypt is enabled, this port must be reachable or you won't be able to obtain certs. If letsencrypt is disabled, this port will not be used.
This *must not* be the same as the webserver/API port specified above.
Default: 80")
  (letsencrypt-cert-dir
   (string "/gotosocial/storage/certs")
   "String. Directory in which to store LetsEncrypt certificates. It is a good move to make this a sub-path within your storage directory, as it makes backup easier, but you might wish to move them elsewhere if they're also accessed by other services.
In any case, make sure GoToSocial has permissions to write to / read from this directory.
Default: \"/gotosocial/storage/certs\"")
  (letsencrypt-email-address
   (string "")
   "String. Email address to use when registering LetsEncrypt certs. Most likely, this will be the email address of the instance administrator. LetsEncrypt will send notifications about expiring certificates etc to this address.
Default: \"\"")
  (oidc-enabled
   (boolean #f)
   "Boolean. Enable authentication with external OIDC provider. If set to true, then the other OIDC options must be set as well. If this is set to false, then the standard internal oauth flow will be used, where users sign in to GtS with username/password.
Default: #f")
  (oidc-idp-name
   (string "")
   "String. Name of the oidc idp (identity provider). This will be shown to users when they log in.
Examples: [\"Google\", \"Dex\", \"Auth0\"]
Default: \"\"")
  (oidc-skip-verification
   (boolean #f)
   "Boolean. Skip the normal verification flow of tokens returned from the OIDC provider, ie. don't check the expiry or signature. This should only be used in debugging or testing, never ever in a production environment as it's extremely unsafe!
Default: #f")
  (oidc-issuer
   (string "")
   "String. OIDC issuer URI. This is where GtS will redirect users to for login. Typicallythis will look like a standard web URL.
Default: \"\"")
  (oidc-client-id
   (string "")
   "String. The ID for this client as registered with the OIDC provider.
Default: \"\"")
  (oidc-client-secret
   (string "")
   "String. The secret for this client as registered with the OIDC provider.
Default: \"\"")
  (oidc-scopes
   (list-of-strings '("openid" "email" "profile" "groups"))
   "List of strings. Scopes to request from the OIDC provider. The returned values will be used to populate users created in GtS as a result of the authentication flow. 'openid' and 'email' are required. 'profile' is used to extract a username for the newly created user. 'groups' is optional and can be used to determine if a user is an admin (if they're in the group 'admin' or 'admins').
Default: [\"openid\", \"email\", \"profile\", \"groups\"]")
  (oidc-link-existing
   (boolean #f)
   "Boolean. Link OIDC authenticated users to existing ones based on their email address. This is mostly intended for migration purposes if you were running previous versions of GTS which only correlated users with their email address. Should be set to false for most usecases.
Default: #f")
  (smtp-host
   (string "")
   "String. The hostname of the smtp server you want to use. If this is not set, smtp will not be used to send emails, and you can ignore the other settings.
Default: \"\"")
  (smtp-port
   (integer 0)
   "Integer. Port to use to connect to the smtp server.
Default: 0")
  (smtp-username
   (string "")
   "String. username to use when authenticating with the smtp server. This should have been provided to you by your smtp host. This is often, but not always, an email address.
Default: \"\"")
  (smtp-password
   (string "")
   "String. Password to use when authenticating with the smtp host. This should have been provided to you by your smtp host.
Default: \"\"")
  (smtp-from
   (string "")
   "String. 'From' address for sent emails.
Default: \"\"")
  (syslog-enabled
   (boolean #f)
   "Boolean. Enable the syslog logging hook. Logs will be mirrored to the convigured destination.
Default: #f")
  (syslog-protocol
   (string "udp")
   "String. Protocol to use directing logs to syslog. Leave empty to connect to local syslog.
Default: \"udp\"")
  (syslog-address
   (string "localhost:514")
   "String. Address:port to send syslog logs to. Leave empty to connect to local syslog.
Default: \"localhost:514\"")
  (advanced-cookies-samesite
   (string "lax")
   "String. Value of the SameSite attribute of cookies set by GoToSocial. Defaults to 'lax' to ensure that the OIDC flow does not break, which is fine in most cases. If you want to harden your instance against CSRF attacks and don't mind if some login-related things might break, you can set this to 'strict' instead.

For an overview of what this does, see: @url{https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite}

Options: [\"lax\", \"strict\"]
Default: \"lax\"")
  (advanced-rate-limit-requests
   (integer 300)
   "Integer. Amount of requests to permit per router grouping from a single IP address within a span of 5 minutes. If this amount is exceeded, a 429 HTTP error code will be returned.

If you find yourself adjusting this limit because it's regularly being exceeded, you should first verify that your settings for `trusted-proxies` (above) are correct. In many cases, when the rate limit is exceeded it is because your instance sees all incoming requests as coming from the *same IP address* (you can verify this by looking at the client IPs in your instance logs). If this is the case, try adding that IP address to your `trusted-proxies` *BEFORE* you go adjusting this rate limit setting!

If you set this to 0 or less, rate limiting will be disabled entirely.

Default: 300")
  (advanced-throttling-multiplier
   (integer 8)
   "Integer. Amount of open requests to permit per CPU, per router grouping, before applying http request throttling. Any requests beyond the calculated limit are held in a backlog queue for up to 30 seconds before either being processed or timing out. Requests that don't fit in the backlog queue will have status 503 returned to them, and the header 'Retry-After' will be set to 30 seconds.

Open request limit is available CPUs * multiplier; backlog queue limit is limit * multiplier.

Example values for multiplier 8:

1 cpu = 08 open, 064 backlog
2 cpu = 16 open, 128 backlog
4 cpu = 32 open, 256 backlog

Example values for multiplier 4:

1 cpu = 04 open, 016 backlog
2 cpu = 08 open, 032 backlog
4 cpu = 16 open, 064 backlog

A multiplier of 8 is a sensible default, but you may wish to increase this for instances running on very performant hardware, or decrease it for instances using v. slow CPUs.

If you set this to 0 or less, http request throttling will be disabled entirely.

Default: 8")
  (prefix gts-))

(define (gotosocial-serialize-configuration configuration)
  (mixed-text-file
   "gotosocial.yaml"
   (serialize-configuration configuration gotosocial-configuration-fields)))

(define (gotosocial-shepherd-service config)
  (shepherd-service
   (documentation "Run GoToSocial.")
   (provision '(gotosocial))
   (requirement '(user-processes))
   (start #~(make-forkexec-constructor
         (list #$(file-append gotosocial "/bin/gotosocial")
           "--config-path" #$(gotosocial-serialize-configuration config))))
   (stop #~(make-kill-destructor))))

(define gotosocial-service-type
  (service-type
   (name 'gotosocial)
   (extensions
    (list (service-extension shepherd-root-service-type
                 (compose list gotosocial-shepherd-service))))
   (default-value (gotosocial-configuration))
   (description "Runs GoToSocial, a lightweight ActivityPub server.")))

=============
         (service gotosocial-service-type
              (gotosocial-configuration
               (protocol "http")))
=============

Backtrace:
           7 (primitive-load "/gnu/store/h5xlrgv8hg90nnaak7n669v5plx?")
In ice-9/ports.scm:
   433:17  6 (call-with-output-file _ _ #:binary _ #:encoding _)
In ice-9/eval.scm:
    159:9  5 (_ #(#(#<directory (guile-user) 7ffff5fdbc80>) #<outp?>))
    155:9  4 (_ #(#(#<directory (guile-user) 7ffff5fdbc80>) #<outp?>))
   173:39  3 (_ #(#(#<directory (guile-user) 7ffff5fdbc80>) #<outp?>))
    163:9  2 (_ #(#(#<directory (guile-user) 7ffff5fdbc80>) #<outp?>))
   223:20  1 (proc #(#(#<directory (guile-user) 7ffff5fdbc80>) #<o?>))
In unknown file:
           0 (%resolve-variable (7 . log-level) #<directory (guile-u?>)

ERROR: In procedure %resolve-variable:
Unbound variable: log-level