Questions about the 6.0.10 update process, and a few suggestions

Admin Talk Upgrade
1

As an old-time on-premise Seatable user, I’m using the 6.0.10 update (from 5.3.12) to clean up some old, outdated (file-based) configurations to come as close to the standard as possible. Specifically, I want to move from file-based configurations to environment one as much as possible. To achieve this, I created a new installation from scratch (also to debug [SOLVED] Update from 5.3.12 to 6.0.10 fails because of failed auto upgrade of MariaDB from 11.6-noble to >= 11.7-noble - #5 by abaer :slight_smile: ), which in turn created all the neccessary minimal config files in /conf.

After reading the documentation for a bit, I’d like to have a few explicit confirmations before I move on cleaning up my old configurations. Maybe this serves others as a link collection for best practice:

  1. The variables in Environment variables - SeaTable Admin Manual are the current ones that get dynamically handed down to containers, and will stay environment-based in the future?
    1. Suggestion 1: Mark the exception(s) (currently the only one I found - SEATABLE_SERVER_HOSTNAME is initially written into dtable_web_settings.py, making the dynamic configuration void) which do not stay environment-based after the first startup.
    2. Suggestion 2: Add ENABLE_PYTHON_SCRIPT to the list :slight_smile:
  2. Did you prune the “configuration files“ section of the documentation (e.g. dtable_web_settings.py - SeaTable Admin Manual ) so there is no overlap (with the exception of SEATABLE_SERVER_HOSTNAME)?
    1. Suggestion 1: You might mark the ones from the environment variables list which may still be overwritten by config files, and how long this will last (e.g. the whole email config) (including deprecation warnings if file-based entries will be replaced by environment-based ones)
    2. Thinking of it, a master list of config variables would be nice, with a classification
      1. Purely environment - based, no file-based equivalent
      2. Environment, can per overwritten by config file manually
      3. Environment, is automatically written into config file
      4. Purely file-based only
    3. Suggestion 2: For some optional config file entries like “Embed into websites“ see dtable_web_settings.py - SeaTable Admin Manual , it is not clear to me what the default is.
    4. Suggestion 3: In the file-based rundown of settings, you might want to set cross reference links to other theme-related settings (like “Permissions and Roles” linked from dtable_web_settings.py - SeaTable Admin Manual )

My main theme is: Currently, the documentation makes it easy for first time Admins to set up and configure a clean system according to you standards. Keeping an old installation up-to-date and modern can be improved.

Final question: What is this Caddy entry for?

      caddy_0.header.Set-Cookie: '(.*) "$1; SameSite=None; Secure"'