Summary
The current self-hosted Docker setup relies on outdated and archived localstack/localstack:3.0.
Not only is LocalStack well past version 3 (it's now on v4+), meaning it may be missing important security patches, it is now a public archive. For a privacy-focused application, depending on an outdated stack feels inconsistent with the project's values.
Questions
- Is there any plan to modernize or update the self-hosted stack?
- Are there plans to replace or remove the dependency on LocalStack?
- If self-hosting is no longer a priority, would the team consider officially documenting this so users know what to expect?
Why This Matters
For users who specifically choose Standard Notes because of its strong privacy stance, running the self-hosted version on outdated infrastructure undermines trust. Many of us are happy to maintain our own instances, but we need the underlying components to remain reasonably current.
Summary
The current self-hosted Docker setup relies on outdated and archived
localstack/localstack:3.0.Not only is LocalStack well past version 3 (it's now on v4+), meaning it may be missing important security patches, it is now a public archive. For a privacy-focused application, depending on an outdated stack feels inconsistent with the project's values.
Questions
Why This Matters
For users who specifically choose Standard Notes because of its strong privacy stance, running the self-hosted version on outdated infrastructure undermines trust. Many of us are happy to maintain our own instances, but we need the underlying components to remain reasonably current.