[PR #644] add FaynoSync #623

New Issue

GiteaMirror · 2025-11-06T17:04:51-06:00

GiteaMirror commented

2025-11-06 17:04:51 -06:00

📋 Pull Request Information

Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/644
Author: @ku9nov
Created: 9/23/2025
Status: 🔄 Open

Base: master ← Head: patch-1

📝 Commits (3)

6fb7422 add FaynoSync
05822c5 add faynosync dashboard to Clients
c0b3ac1 add docker tag

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Related to: https://github.com/awesome-selfhosted/awesome-selfhosted-data/pull/1610

To ensure your PR is dealt with swiftly please check the following:

Your additions are Free software
Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
Submit one item per pull request. This eases reviewing and speeds up inclusion.
Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
You have searched the repository for any relevant issues or PRs, including closed ones.
Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Why is it awesome?

Because it’s a server that provides an alternative to the existing client application update flow, offering much more flexibility and capabilities.

Have you used it? For how long?

Yes, it’s my pet project, so I use it. I’ve been developing it in my free time.

Is this in a personal or professional setup?

Personal, but it’s also used at work by the teams I collaborate with.

How many devices/users/services/... do you manage with it?

As far as I know, several development teams are using it.

Biggest pros/cons compared to other solutions?

Unlike the standard flow that relies on files hosted on a CDN for updating client applications, using faynoSync provides more flexibility and convenience. The application owner can both revoke or publish app versions and manage the update process with intermediate versions, and much more.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/awesome-foss/awesome-sysadmin/pull/644 **Author:** [@ku9nov](https://github.com/ku9nov) **Created:** 9/23/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (3) - [`6fb7422`](https://github.com/awesome-foss/awesome-sysadmin/commit/6fb74226d1773603689d5465d290edba7d9f08ba) add FaynoSync - [`05822c5`](https://github.com/awesome-foss/awesome-sysadmin/commit/05822c5ebddcf1302cb590a22d2970b6572e32b4) add faynosync dashboard to Clients - [`c0b3ac1`](https://github.com/awesome-foss/awesome-sysadmin/commit/c0b3ac1330084d4cda8b37a95af6ef4f9fb45fde) add docker tag ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description  Related to: https://github.com/awesome-selfhosted/awesome-selfhosted-data/pull/1610 To ensure your PR is dealt with swiftly please check the following: - [x] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [ ] Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [x] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [x] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [x] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [x] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [ ] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. --------------  - **Why is it awesome?** Because it’s a server that provides an alternative to the existing client application update flow, offering much more flexibility and capabilities. - **Have you used it? For how long?** Yes, it’s my pet project, so I use it. I’ve been developing it in my free time. - **Is this in a personal or professional setup?** Personal, but it’s also used at work by the teams I collaborate with. - **How many devices/users/services/... do you manage with it?** As far as I know, several development teams are using it. - **Biggest pros/cons compared to other solutions?** Unlike the standard flow that relies on files hosted on a CDN for updating client applications, using faynoSync provides more flexibility and convenience. The application owner can both revoke or publish app versions and manage the update process with intermediate versions, and much more. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-06 17:04:51 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#623