[Feature Request] .filesyncignore file

[rasentry]

First of all, I would like to express my gratitude for this amazing tool you’ve created.

I have many projects with numerous auxiliary files and folders that I don't need to sync. I would like to have a feature similar to .gitignore, for example, a .filesyncignore file. I could create and place this file within a project, then define the rules for the files and folders I want to exclude from synchronization.

In my opinion, this is a feature that would be great to have.

[xCSxXenon]

Is placing a ".ignore" file any less work than adding an exclusion?

[rasentry]

I can easily include the root folder for all projects in the sync configuration without customizing the exclusion list for each one. This can be done by editing the .ignore file individually for each project, similar to how Git handles it.

[Plerry]

You can edit, copy and paste in the FFS Include and Exclude Filter in the FFS GUI.

Alternatively:
FFS sync configurations are saved as *.ffs_gui or *.ffs_batch files.
These files are XML-files, in which you can find the
<Filter>...</Filter> section, which comprises the
<Include>...</Include>and <Exclude>...</Exclude> sections,
each comprising one or more <Item>...</Item> 's to be Included, respectively Excluded.

You can edit the *.ffs_gui or *.ffs_batch XML files with any suitable editor, e.g. Notepad++

[xCSxXenon]

I can easily include the root folder for all projects in the sync configuration without customizing the exclusion list for each one. This can be done by editing the .ignore file individually for each project, similar to how Git handles it.

Oh I see! I was incorrectly thinking about something else that you place per-folder!

[rasentry]

You can edit, copy and paste in the FFS Include and Exclude Filter in the FFS GUI.

Alternatively:
FFS sync configurations are saved as *.ffs_gui or *.ffs_batch files.
These files are XML-files, in which you can find the
<Filter>...</Filter> section, which comprises the
<Include>...</Include>and <Exclude>...</Exclude> sections,
each comprising one or more <Item>...</Item> 's to be Included, respectively Excluded.

You can edit the *.ffs_gui or *.ffs_batch XML files with any suitable editor, e.g. Notepad++

It’s inconvenient to update the backup configuration (*.ffs_gui file) every time I modify an existing project or add a new one.

[Plerry]

It’s inconvenient to update the backup configuration (*.ffs_gui file) every time I modify an existing project or add a new one.

Your use of "the" suggests there is/can be only a single *.fss_gui (or *.ffs_batch) sync configuration file.
However, you can create and save as many sync configuration files as you like, and name each one as you like.

[rasentry]

Your use of "the" suggests there is/can be only a single *.fss_gui (or *.ffs_batch) sync configuration file.
However, you can create and save as many sync configuration files as you like, and name each one as you like.

My proposal isn't about naming *.ffs_gui files or managing hundreds of them. It's about handling exclusions in individual subfolders within a folder included in the *.ffs_gui, exactly as Git does.