Releases

What shipped.

Each Farwing release is published on farwing.io/download with signed Windows builds and SHA-256 checksums.

Farwing 0.7.0

An administrator can make, rename and delete folders while setting up a space or a storage location. The command line can copy to and from a machine that is listening, without SSH. Farwing notices a virus scanner installed on the same machine.

Folders. When you choose a folder for a space, or browse to the folder a storage location should serve, you can add a folder, open the ones already there, rename one, or delete one. A folder that a space, hot folder, sync job, receive link, package or server link still uses cannot be deleted until those are moved or removed. Deleting a folder that holds files, inside a storage location, asks you to type its name first. A folder elsewhere on the server can be deleted only when it is empty. Renaming updates the spaces, access, hot folders, sync jobs, receive links and packages that use that folder. An event rule matches paths by pattern, so check it still matches. The other end of a server link keeps its own copy of the folder name.
Command line. On a machine where you do not want to sign in over SSH, run farwing listen and copy with farwing://host/path. The listener can send a file out of its folder as well as receive one. An SSH password is asked once for a copy, not once for every file.
Virus scanning. When ClamAV is installed on the server, Farwing finds it and shows it on the scanning page, including what happens when a file cannot be scanned. Administrators are emailed when that scanner stops answering or its definitions go stale. See Virus scanning.
Farwing Desktop. An upload into a space starts. Uploads, finished transfers and settings are laid out so each is easier to find, and several finished transfers can be removed together. The installers show the Farwing name.
Documentation. The menu opens one section at a time, so the list stays on the screen.

What administrators need to know:

Use 0.7.0 of the command line and Farwing Desktop with this server. Older apps keep working: they connect, send and receive as before. A listener from 0.6.0 still receives files. Sending a file out of a listener's folder, and saving an upload into a named folder there, needs 0.7.0 on both sides. Farwing Desktop older than 0.2.0 is still asked to update before it can send through a receive link.
Upgrading from 0.6.0: the data folder does not change. Back up first, as for any upgrade. docker compose pull and docker compose up -d are the whole upgrade. Farwing 0.6.0 still starts on this data folder. Folders you added or renamed on 0.7.0 stay where you left them.

Farwing 0.6.0

Hot folders and sync jobs send to a destination you save once. A package sends files that are already on the server to people without an account. When an authenticator app is required, that setup finishes before a session exists.

Destinations. Save a place files can go: another Farwing server, an FTP or FTPS server, an SFTP server, or a cloud bucket. Test it before you rely on it. A hot folder, a sync job or an event rule uses that saved destination. One that is still in use cannot be deleted until those are changed.
Server links. To send to another Farwing server, pair with it. The other administrator makes a pairing code. You enter that code and the other server’s address, then confirm the identity code matches what they read to you. An incoming link chooses which folders the other server may read, write or delete.
Hot folders. A hot folder watches a folder and sends each file once it has stopped changing. After the destination confirms the file is stored, you can keep it, move it into a sent folder, or delete it. Moving or deleting happens only after that confirmation. Deleting the hot folder stops the watch and leaves the files where they are. See Hot folders and sync.
Sync jobs. A sync job keeps a folder copied to a destination on a schedule: every hour, every day, every week, or only when you ask. It never changes the files here. A preview shows what would change and copies nothing. Removing files at the destination stays off until you have previewed the job, the destination allows removing, and you have confirmed it. Every run that removes files stops before removing more than the percent or the number of files you set. If the source looks empty, Farwing copies what it can still read and removes nothing.
Packages. Send files and folders that are already on the server. Each person gets their own link, with an optional passcode that is not put in the email. They can download a ZIP, take files one by one, receive the package in Farwing Desktop, or run farwing get with the link. A folder is read again when someone collects it, and empty folders are included. You can see who opened a link and what they collected. See Packages.
Service accounts and API keys. A service account cannot sign in. It is for a script or a server link, and it keeps working when a person leaves. A key belongs to a person or a service account and can do only what it was given, never more than its owner.
Sign-in. When an authenticator app is required, that setup finishes before a session exists. A person who forgets a Farwing password can set a new one from a link. An administrator can reset a lost authenticator so the person sets it up again at the next sign-in. Accounts that sign in through single sign-on, SAML or a directory keep that directory’s password; Farwing does not reset those.
Receive links. The list can be filtered and paged. End stops a link taking files and keeps the record of what was sent. Delete removes the link and that history. Files already saved stay in their folder.
Files. Click a file or folder row to select it, and send the selection as a package.
Speed check. A cloud bucket you include is shown while the check runs and listed in the finished report. A larger copy that was left out after a smaller one had already stalled is reported as stalled. In a container, the note that the network card has no link speed stays information, not a failed check.
Farwing Desktop and the command line. When the portal is not on port 443, Desktop opens the address the transfer link names, including that port. farwing get creates empty folders that were part of a package.

What administrators need to know:

Sync jobs that ran more often than once an hour now run hourly. A job set to every 15 minutes or every 6 hours is kept, and it runs every hour. The job says that its rhythm changed. The shortest schedule is one hour.
Use 0.6.0 of the command line and Farwing Desktop with this server. Older apps keep working: they connect, send and receive as before. A transfer link may include the portal’s HTTPS port when that port is not 443. Older apps ignore that field and still transfer. Farwing Desktop 0.6.0 is the one that opens a portal on a port other than 443. Farwing Desktop older than 0.2.0 is still asked to update before it can send through a receive link.
Upgrading from 0.5.0: the server updates its data folder on first start, so it can store destinations, hot-folder and sync-job details, service accounts, package folders and sign-in resets. Nothing is removed, and everyone keeps the access they had. Back up the data folder first, as for any upgrade. docker compose pull and docker compose up -d are the whole upgrade. Farwing 0.5.0 will not start on this updated data folder. To go back, restore the backup taken before the upgrade.

Farwing 0.5.0

Farwing Server, the command line and Farwing Desktop now share one version. This release is 0.5.0 for all three. Farwing Desktop moves from 0.3.0 to 0.5.0; there is no Desktop 0.4.0.

One version everywhere. The command line, the server, Farwing Desktop's About box and the portal all show the same version and build, for example 0.5.0.
See which app each person last used. People and API keys show the Farwing app and version that account last connected with, and when.
Older downloads stay available. Previous versions remain on the download site, so an install can ask for a specific version.

What administrators need to know:

Use 0.5.0 of the command line and Farwing Desktop with this server. Older apps keep working: they connect, send and receive as before. Farwing Desktop older than 0.2.0 is still asked to update before it can send through a receive link.
Upgrading from 0.4.0: the server updates its data folder on first start, so it can remember the app each account last used. Nothing is removed, and everyone keeps the access they had. Back up the data folder first, as for any upgrade. docker compose pull and docker compose up -d are the whole upgrade.

Farwing 0.4.0

Some features below depend on your plan. See farwing.io/pricing.

A new admin menu. The admin pages are grouped into six areas: User management, Storage, Transfers, Security & audit, Branding & email, and System. Each area is one page with tabs. Old admin addresses and bookmarks open the same page in its new tab, and typing a setting's name in the search box takes you to the tab that holds it.
Storage locations and spaces. A storage location is where files live: a folder or a bucket, its credentials, health and speed. A space is what people open, and access is now given on spaces only. When you add a storage location, Farwing offers to share it as a space and walks you through the folder, the kind of space, its name and who gets it. Each storage location lists the spaces that use it.
Servers that showed "No spaces yet" repair themselves. On 0.3.0 and 0.3.1, access given on a storage location without a space could leave people with an empty Files page. On first start, 0.4.0 makes the missing spaces and files that access under them. Nobody gains or loses access, and you do not need to give it again.
A searchable access picker. Find people and groups by typing, and give the same folder and access to several of them in one go. Administrators are listed too.
Receive-link wizard fixes. Every step keeps its name in the step bar, including when you edit a link and in a narrow window. A button that cannot go on yet says why and puts the cursor in the field that needs attention.
Clearer speed check results. When a storage location is not tested, the check says exactly why, such as a missing folder, a full disk, or a bucket that refused the key, and links to the fix. A bucket is tested when you include it, and a bucket you left out says so instead of being called a folder the server cannot reach. A saved check keeps the UDP buffer size it measured, with today's setting on a separate line.
Maintenance holds event rules. An event rule that sends files to another server or sends a package now waits while maintenance is on and starts once it ends, instead of failing.
Certificate renewals no longer ask for a restart. A renewed certificate is used by new connections as soon as it is installed. A new or uploaded certificate still offers to restart.
A send fails when the file was not saved. If a bucket refused the final step of an upload, the command line and Farwing Desktop used to report success. The send now fails with a message to send it again, the transfer is recorded as failed, and the unfinished upload is removed from the bucket.
Bucket clean-up touches only Farwing's own uploads. The 7-day clean-up now aborts only unfinished uploads that Farwing started and that no transfer is still sending. Other programs' uploads in the same bucket are left alone.
Removing a space tells you first who loses access and what they lose. Access that another space also covers is kept. The files stay on the storage location.

What administrators need to know:

Security fix for personal spaces. On 0.3.0 and 0.3.1, a person's private folder could be given a folder that already existed with the same name, such as a shared folder or a folder left by a deleted user. That person then had full control of it and other people lost access. 0.4.0 always gives a private folder a name that is not already in use. It does not move folders that were handed out before. If you use personal spaces, open each person's private folder from Admin, Storage, Spaces and check that it holds that person's own files. Only servers with a personal space are affected.
Use Farwing Desktop 0.3.0 and the command line 0.4.0 with this server. Older versions keep working with it: they connect, send and receive as before. One fix needs the new versions: if the server cannot save a file and its error does not reach an older app, that app can still report the send as complete. Farwing Desktop 0.3.0 and the command line 0.4.0 report it as failed. Farwing Desktop older than 0.2.0 is still asked to update before it can send through a receive link.
Upgrading from 0.3.x: the server updates its data folder on first start. Nothing is removed, and everyone keeps the access they had. Back up the data folder first, as for any upgrade.

Farwing Desktop 0.3.0

A send fails, with a message to send it again, when the server does not confirm that it saved the file. Before, Farwing Desktop could report such a send as complete.

Farwing 0.3.1

While maintenance is on, new uploads, transfers and packages are paused for everyone, including administrators. Transfers already running carry on.
The speed check reads the host UDP buffer each time the page opens, so a limit you have already raised is not stuck as a warning from the last saved check.
Past speed checks are on their own tab. You can page through them, filter by date and delete one.

Farwing 0.3.0

Some features below depend on your plan. See farwing.io/pricing.

Storage spaces: named shared folders and a personal folder for each person, inside your storage locations. Home shows each person their spaces as cards, with My files first. Only administrators see disk paths and bucket names.
Receive links, redesigned: create a link step by step, then copy it, show a QR code or send it by email. Each person you email gets a personal link that already proves their address, so they are not asked for a code. Senders choose between the browser and Farwing Desktop, which sends at full speed.
Fast S3 storage: files go straight into the bucket while they arrive, in many parts at once, each part checked by the bucket. A file appears only once the whole file has been checked. Large files are read back in parallel. Each bucket has its own performance settings.
Speed check now tests every storage location. A cloud bucket is tested only after you agree, because the test writes data your provider may charge for. In a container, where the network card reports no link speed, the check says so instead of treating it as a limit.
Features your license does not include are shown read-only, greyed out, with one note saying which license they need. Password and lockout rules move to their own Sign-in rules page and can be changed on every plan.
The Traffic page shows download and upload limits side by side for each scope, and can look up the limit that applies to anyone.
An API reference for every call an API key can make.
Event rules can start on a new file stored event, once a file is in its final storage.
After you save a new certificate, the certificate page asks whether to restart now so open connections use it.

What administrators need to know:

Farwing Desktop 0.2.0 or later is needed to send through a receive link with Farwing Desktop. A sender with an older version is asked to update, and can always send from the browser instead.
Uploads to an S3 bucket go straight into the bucket (Direct mode). Nothing is copied to the server's disk on the way, and parts wait in server memory until they are uploaded. See Memory to size it.
Unfinished bucket uploads are cleaned up. Farwing aborts every unfinished upload under a bucket's prefix that was started more than 7 days ago, including uploads another program started. If other software writes to the same bucket, give Farwing its own bucket or prefix.
Upgrading from 0.2.x: the server updates its data folder on first start. Nothing is removed, and everyone keeps the access they had. Back up the data folder first, as for any upgrade.

Farwing Desktop 0.2.0

Opens from a receive link on a Send files to screen that shows the link's limits, checks your files against them and sends them at full speed.
The speed limit is a switch with a choice of Mbit/s or Gbit/s, so turning a limit off keeps the number for next time.

Farwing 0.2.1

The first 0.2 release of the command-line client on the download page. The server image was also published as 0.2.0, with the same features. Some features below depend on your plan. See farwing.io/pricing.

Receive links: people outside your organization send you files from their browser, with no account. Large files go up in pieces and pick up where they stopped after a dropped connection. On a phone, the drop zone comes first.
Virus scanning of files sent through receive links, with ClamAV, an ICAP scanner or a command of your own. Infected files go to a quarantine that only administrators can see.
Event rules run a script, call a webhook or send a notification when files arrive.
SAML single sign-on and LDAP / Active Directory sign-in, with groups taken from the directory.
Email templates: write the emails Farwing sends in your own words, with your logo and in several languages. Preview them, send a test, and go back to any earlier version.
Speed check measures the server's disks, CPU, memory and network, and can email administrators when a scheduled check finds a problem.
Traffic schedules and priorities, a live view of the bytes each transfer is moving, and usage reports by email.
Every button and field in the web portal is easy to tap on a phone, in dialogs and menus too.

Upgrading from 0.1.x: the server updates its data folder on first start. Nothing is removed. Back up the data folder first, as for any upgrade.

Install a specific version

Linux / macOS:

curl -fsSL -o farwing-install.sh https://farwing.io/install.sh
bash ./farwing-install.sh --version vX.Y.Z

Omit --version (or use latest) for the current release. Windows:

Invoke-WebRequest -UseBasicParsing https://farwing.io/install.ps1 -OutFile farwing-install.ps1
powershell -File .\farwing-install.ps1 --version vX.Y.Z

Farwing Desktop

Farwing Desktop has its own versions. Its installers for Windows, macOS and Linux, with their SHA-256 checksums, are on farwing.io/download.

Signing

The command-line client’s Windows binaries and its PowerShell installer are Authenticode-signed.
Every archive is listed with its SHA-256 on the download page. The installer checks that hash before it installs.