Unclaimed project
Are you a maintainer of syncthing? Claim this project to take control of your public changelog and roadmap.
Changelog
Open Source Continuous File Synchronization
Get up and running with Kimi-K2.5, GLM-4.7, DeepSeek, gpt-oss, Qwen, Gemma and other models.
Production-Grade Container Scheduling and Management
A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
Gin is a high-performance HTTP web framework written in Go. It provides a Martini-like API but with significantly better performance—up to 40 times faster—thanks to httprouter. Gin is designed for building REST APIs, web applications, and microservices.
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...
Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per...