Skip to content

INNER_DTABLE_STORAGE_SERVER_URL - #902

Open
SkywalkerSpace wants to merge 1 commit into
masterfrom
INNER_DTABLE_STORAGE_SERVER_URL
Open

SkywalkerSpace wants to merge 1 commit into
masterfrom
INNER_DTABLE_STORAGE_SERVER_URL

Conversation

@SkywalkerSpace

Copy link
Copy Markdown
Contributor

No description provided.

@seafile-dev seafile-dev left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: Comment

Warnings:

  • The configuration-key rename drops existing DTABLE_STORAGE_SERVER_URL YAML/environment deployments; see inline comment.
    Suggested fix: retain the old key as a fallback while preferring INNER_DTABLE_STORAGE_SERVER_URL, then document the new variable and migration in seatable-admin-docs.


# storage server
DTABLE_STORAGE_SERVER_URL = configs.get('DTABLE_STORAGE_SERVER_URL', default='http://127.0.0.1:6666')
INNER_DTABLE_STORAGE_SERVER_URL = configs.get('INNER_DTABLE_STORAGE_SERVER_URL', default='http://127.0.0.1:6666')

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Warning] Preserve existing storage configuration

Why this matters:
This replaces the established DTABLE_STORAGE_SERVER_URL setting rather than adding an environment override. Existing YAML deployments that set that key now resolve to the loopback default, so a distributed deployment can silently start using the wrong storage server after upgrading.

Suggested fix: prefer INNER_DTABLE_STORAGE_SERVER_URL, but fall back to DTABLE_STORAGE_SERVER_URL when it is unset; document the new name and migration path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants