Skip to main content
A site can hold named values for its functions: an API key for another service, a webhook signing secret, a feature switch. Set them once and every function of the site receives them.
You can set and list values today, but site functions aren’t available yet, so nothing reads them until functions ship.

​
Set a value

  • --stdin reads the value from standard input, so a secret never appears in your shell history.
  • unset asks before it removes a value. --yes skips the question, for example in CI.
  • A secret can be set and removed, but never read back: fluid sites env list shows its name only. Use it for keys and passwords.
  • A plain value can be read back by anyone who can publish the site.
  • --folder names the site’s folder when you’re not in it. The other env commands take the folder as their last argument.

​
Names

A name is capital letters, digits and underscores, starts with a letter, and is at most 64 characters, such as NEWSLETTER_LIST_ID. Names that start with FLUID_ are reserved. A value is at most 5 KB, and a site holds at most 64 values.

​
Use them

Every value, secret or not, is for the site’s functions. None is ever sent to the browser, so a page can’t read one.

​
Through the API

  • For a site you own: list, set and remove a site’s environment variables.
  • As an admin: list, set and remove a company site’s environment variables.