memospot/memospot v0.1.3

on GitHub

What's Changed

• Bundled with Memos v0.20.0
• Compatible with newer Memos releases with loose front-end files (dist folder)
• Disabled Memos metrics (metrics were removed from Memos v0.20+)
• Added database checkpoint on closing: ensures changed data is persisted
• New database migrator: makes the database and assets portable
• Introduced a database backup system
• Lots of new settings: allows using a custom folder for Memos data and allows fine-grained control of server
• Updated UI wording and color scheme
• Disabled Memos logging capabilities: log is currently available only for debugging Memospot itself

Full Changelog: v0.1.2...v0.1.3
Release changelog: 2360702

Post-upgrade issues

If you see an error while Memos's interface is loading, just press F5 or right-click the window and click reload. This is caused by a stale webview cache and also affects Memo's Docker instances.

Migration

The internal resource path migration will run only once when you first start this new version. It will create a new table memospot_migrations to keep track of migrations. This won't affect Memos at all.

The path migrator is relatively fast. It can migrate 300k resources in less than 30 seconds on a modern machine. If you see a Something went wrong message, just wait a minute and click the Check again button.

Backups

The backup system is in a preliminary stage, currently only used before migrations.
Backups are created using a zip file container, but compression is in Zstandard format (due to the speed/compression ratio being much better). If needed, you can decompress those files with WinRAR, 7-Zip-zstd, or p7zip.

Configuration

For advanced usage only. Most of the settings are optional or auto-managed.

The most prominent new setting is memos.data, which allows you to change the data storage (database, assets, and thumbnails) to a folder synced by a cloud storage provider client, like OneDrive, Dropbox, Google Drive, etc.

• Path-related settings support home directory ~/ expansion.

• File is located at ~/.memospot (POSIX systems) or %LocalAppData%\memospot (Windows).

Sample memospot.yaml:

memos:
  # Use this to spawn a custom Memos binary.
  binary_path: null

  # Memos working dir. This is where the `dist` folder must reside.
  working_dir: null

  # Memos data storage. Where the database and assets are stored.
  data: null

  # Mode: [prod] | dev | demo. This affects the database used on startup.
  mode: prod

  # Address where Memos will listen for connections.
  addr: 127.0.0.1

  # Memos port. Managed by Memospot. You can set a custom port, but it
  # will be automatically changed if the port is in use at Memospot startup.
  port: 0

  # Custom environment variables for Memos. Custom keys will be automatically uppercased and prefixed with "MEMOS_". Make sure to always quote custom env values, so they get parsed as strings.
  # env:
  #   NEW_ENV_VAR: "my value"
  env: null
memospot:
  backups:
    # Enable backups [true]. Currently, backups only run before
    # database migrations and there's no retention management.
    enabled: true
    # Backup directory.
    path: null
  migrations:
    # Enable migrations [true]. Currently, there's one migration available that will change local resource paths from absolute to relative, making your data fully portable.
    enabled: true
  log:
    # Enable logging [false]. Used for advanced debugging.
    # A new file called `logging_config.yaml` will be created next to this file.
    # You can change `root.level` from `info` to `debug` to increase the logging level.
    enabled: true