"Could not create note..." #87

# docker-compose.yml

version: '3.8'

services:
  redis:
    image: redis:7-alpine
    restart: always
    # Set a size limit. See link below on how to customise.
    # https://redis.io/docs/manual/eviction/
    command: redis-server --maxmemory 1gb --maxmemory-policy allkeys-lru

  app:
    image: cupcakearmy/cryptgeon:latest
    depends_on:
      - redis
    environment:
      # Size limit for a single note.
      SIZE_LIMIT: 100 MiB
      VERBOSITY: debug
    ports:
      - 8536:8000
    restart: always

[2023-05-20T02:25:15Z INFO  actix_server::builder] Starting 2 workers
[2023-05-20T02:25:15Z INFO  actix_server::server] Actix runtime found; starting in Actix runtime
[2023-05-20T02:25:34Z INFO  actix_web::middleware::logger] "GET /api/status/ HTTP/1.1" 200 173 0.001038

1:C 20 May 2023 02:19:56.016 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 20 May 2023 02:19:56.016 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 20 May 2023 02:19:56.016 # Configuration loaded
1:M 20 May 2023 02:19:56.020 * monotonic clock: POSIX clock_gettime
1:M 20 May 2023 02:19:56.023 * Running mode=standalone, port=6379.
1:M 20 May 2023 02:19:56.023 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 20 May 2023 02:19:56.023 # Server initialized
1:M 20 May 2023 02:19:56.023 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 20 May 2023 02:19:56.024 * Ready to accept connections