[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.

[Countryen]

Hey there,
I want to join the discussion because I wanted to propose the same - or at least a very similar - feature request just now, and want to give a 👍+1 (not sure if I can vote or anything).

I use FFS since years and love it. I use it for various tasks including a full backup of my

C:\Users\Countryen


folder.

As the OP, I have several folders and projects, and they get moved around a lot because I am always restructuring.
I also create new folders/projects that I want to omit from my routine backup that runs every day/week/month (depending on my activity). Reason: Insdie those folders are either files that I don't need or absolutely don't want on my backup (like secrets and stuff).

Currently I have to add every single folder to the config file either via GUI or XML.
And this every time I move them.
This is very time consuming and tedious.

A feature like

.ffsignore


would be much better by just popping that file in the folder to be SAFELY ignored from the backup. Also it would make duplicating projects easier as I just copy-paste the project folder and have a new project (like a template) but currently I'd need to not forget to add the ignore files/folders again.

Note: Although OP is asking for path-rules inside the

.ffsignore


I just ask for a "ignore this folder / ignore all folder that contain a file named

.ffsignore


ignoring the content" (a sub-feature perhabs). I think what I require is more like an inversed

.gitkeep


.

As said, I move around files and rename files frequently but want to make sure they are excluded. By just seeing the

.ffsignore


inside the folder I would be reassured that everything is fine.
A similar thing could be done with extra file properties but afaik there's not really a convenient way to edit those on Windows. As a workaround I am using a wrapper-folder like

__FFSIGNORE__


but this is not always possible (depends on the situation) or makes it harder to work with.

As an alternative to excluding them (I assume that's tricky because of pattern matching against siblings would be awfully slow, especially when done async), maybe it would help enough to just highlight them in the overwiew after the search or have a warning or an extra button to exclude them afterwards - meaning the search algorithm doesn't need to change, just another button that scans the list afterwards. This would at least make it much easier to be sure, I did not miss any folder. From the table it's also easy to add the folder with the

.ffsignore


file directly.

Still, I really want that sub-feature, too, as this would make my workflow much smoother.

[Edit: Changed the Markdown-Syntax to BBCodes]