This major update introduces a robust, multi-faceted networking
capability, allowing backups to be managed through a central server or
via direct peer-to-peer connections.
Add serve command: Implemented a new serve command that runs a
persistent HTTP server. This allows for a centralized backup management
workflow where multiple clients can upload and download archives. - HTTP Client Mode: The create and restore commands can now
function as HTTP clients, targeting a serve instance using the ip:port/filename address format.
Restore P2P Mode: The original peer-to-peer streaming
functionality (where restore acts as a TCP server and create as a
client) has been fully restored and integrated into the new, more robust
command architecture. - Accurate Network Progress: Fixed a critical
bug where network progress bars would not display correctly. The serve
command now sends a Content-Length header, and restore is refactored
to handle asynchronous state updates correctly. - Smart Address
Parsing: The application now automatically distinguishes between HTTP
mode (ip:port/filename) and P2P mode (ip:port), providing a seamless
user experience.
Update README.md: The project's README has been completely
rewritten to document all three operating modes (Local, HTTP Server,
P2P) with clear usage examples. - Add Gitea Actions Workflow: A new
CI pipeline (.gitea/workflows/build-and-test.yml) has been added to
automatically build and test the application on every push and pull
request.
This major update introduces a robust, multi-faceted networking
capability, allowing backups to be managed through a central server or
via direct peer-to-peer connections.
- **Add `serve` command**: Implemented a new `serve` command that runs a
persistent HTTP server. This allows for a centralized backup management
workflow where multiple clients can upload and download archives. -
**HTTP Client Mode**: The `create` and `restore` commands can now
function as HTTP clients, targeting a `serve` instance using the
`ip:port/filename` address format.
- **Restore P2P Mode**: The original peer-to-peer streaming
functionality (where `restore` acts as a TCP server and `create` as a
client) has been fully restored and integrated into the new, more robust
command architecture. - **Accurate Network Progress**: Fixed a critical
bug where network progress bars would not display correctly. The `serve`
command now sends a `Content-Length` header, and `restore` is refactored
to handle asynchronous state updates correctly. - **Smart Address
Parsing**: The application now automatically distinguishes between HTTP
mode (`ip:port/filename`) and P2P mode (`ip:port`), providing a seamless
user experience.
- **Update `README.md`**: The project's README has been completely
rewritten to document all three operating modes (Local, HTTP Server,
P2P) with clear usage examples. - **Add Gitea Actions Workflow**: A new
CI pipeline (`.gitea/workflows/build-and-test.yml`) has been added to
automatically build and test the application on every push and pull
request.
This major update introduces a robust, multi-faceted networking
capability, allowing backups to be managed through a central server or
via direct peer-to-peer connections.
- **Add `serve` command**: Implemented a new `serve` command that runs a
persistent HTTP server. This allows for a centralized backup management
workflow where multiple clients can upload and download archives. -
**HTTP Client Mode**: The `create` and `restore` commands can now
function as HTTP clients, targeting a `serve` instance using the
`ip:port/filename` address format.
- **Restore P2P Mode**: The original peer-to-peer streaming
functionality (where `restore` acts as a TCP server and `create` as a
client) has been fully restored and integrated into the new, more robust
command architecture. - **Accurate Network Progress**: Fixed a critical
bug where network progress bars would not display correctly. The `serve`
command now sends a `Content-Length` header, and `restore` is refactored
to handle asynchronous state updates correctly. - **Smart Address
Parsing**: The application now automatically distinguishes between HTTP
mode (`ip:port/filename`) and P2P mode (`ip:port`), providing a seamless
user experience.
- **Update `README.md`**: The project's README has been completely
rewritten to document all three operating modes (Local, HTTP Server,
P2P) with clear usage examples. - **Add Gitea Actions Workflow**: A new
CI pipeline (`.gitea/workflows/build-and-test.yml`) has been added to
automatically build and test the application on every push and pull
request.
wt
merged commit f2e670f66a into main2025-08-03 10:46:57 +07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This major update introduces a robust, multi-faceted networking
capability, allowing backups to be managed through a central server or
via direct peer-to-peer connections.
Add
servecommand: Implemented a newservecommand that runs apersistent HTTP server. This allows for a centralized backup management
workflow where multiple clients can upload and download archives. -
HTTP Client Mode: The
createandrestorecommands can nowfunction as HTTP clients, targeting a
serveinstance using theip:port/filenameaddress format.Restore P2P Mode: The original peer-to-peer streaming
functionality (where
restoreacts as a TCP server andcreateas aclient) has been fully restored and integrated into the new, more robust
command architecture. - Accurate Network Progress: Fixed a critical
bug where network progress bars would not display correctly. The
servecommand now sends a
Content-Lengthheader, andrestoreis refactoredto handle asynchronous state updates correctly. - Smart Address
Parsing: The application now automatically distinguishes between HTTP
mode (
ip:port/filename) and P2P mode (ip:port), providing a seamlessuser experience.
Update
README.md: The project's README has been completelyrewritten to document all three operating modes (Local, HTTP Server,
P2P) with clear usage examples. - Add Gitea Actions Workflow: A new
CI pipeline (
.gitea/workflows/build-and-test.yml) has been added toautomatically build and test the application on every push and pull
request.