Skip to content

docs: use STORAGE_TYPE_* enum names in deployment storage example #268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hippi345 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: use STORAGE_TYPE_* enum names in deployment storage example #268

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/docs/configuration/deployment-configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ category: configuration
tags: ["configuration", "self-hosting", "docker", "kubernetes"]
difficulty: advanced
estimatedTime: 15 minutes
lastUpdated: "2026-09-06"
lastUpdated: "2026-10-06"
---

Memos 0.30 and later can load selected configuration from JSON files mounted under `/etc/secrets`. Use this when settings such as SSO, storage credentials, or registration policy should be controlled by Docker Compose, Kubernetes, GitOps, or a secret manager instead of the admin UI.
Expand Down Expand Up @@ -164,7 +164,7 @@ Use `memos-instance-setting-general.json` with `key: "GENERAL"`. The complete fo

### Storage

For 0.31, use named entries in `storages` and select one with `defaultStorageId`. Types are `DATABASE`, `LOCAL`, and `S3`. Each entry has a stable ID; existing attachments continue to use the configuration identified at upload time.
For 0.31, use named entries in `storages` and select one with `defaultStorageId`. Types are `STORAGE_TYPE_DATABASE`, `STORAGE_TYPE_LOCAL`, and `STORAGE_TYPE_S3`. Each entry has a stable ID; existing attachments continue to use the configuration identified at upload time.

```json
{
Expand All @@ -177,7 +177,7 @@ For 0.31, use named entries in `storages` and select one with `defaultStorageId`
{
"id": "team-assets",
"name": "Team assets",
"type": "S3",
"type": "STORAGE_TYPE_S3",
"s3Config": {
"accessKeyId": "access-key",
"accessKeySecret": "secret-key",
Expand Down