Version History

Version 0.1.3 - 2024-02-26

Changed

(Memos) Bundled version: v0.20.0.
Updated UI wording and color scheme.

Added

(Memos) Handle Memos versions with loose front-end files (sidecar dist folder; v0.18.2+) - (a385616).
(Memos) Disable Memos metrics (metrics were removed from Memos v0.20+).
Add database checkpoint on closing: ensures changed data is persisted.
Database migrator: It makes the database and assets portable between any system. 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 can migrate 300k resources in less than 30 seconds on a modern machine. If you see the “Something went wrong” message, just wait a minute and click the “Check again” button.

This feature was added to address issues with the built-in Memos database migration system, which was really slow to the point the related migration was completely removed at some point.
Database backup system: Runs automatically before database migrations. Backups are created using a zip file container, but compression is in Zstandard format (due to a better speed/compression ratio). If needed, you can decompress those files with WinRAR, 7-Zip-zstd, or p7zip.

(Memos) Lots of new settings: allows using a custom folder for Memos data and allows fine-grained control of the server.

Sample memospot.yaml file:

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

Removed

(Memos) No more output logging: log is now available only for debugging Memospot itself.