syrys

New Members
  • Posts

    5
  • Joined

  • Last visited

syrys's Achievements

New User

New User (1/3)

  1. Hey Guys, Im curious, can BT Sync be installed on a server/vps (running ubuntu or centos or similar OS)? If so, is there any good guides i can follow to do so? Is there a good interface i can then use to manage it? Sorry, the reason im asking is, i want to setup my library on a server. I know that this defeats the point, but for my use, this adds a level of redundancy and since if everything is synced to the server, i can still access the data on my phone (or new computer) while all my computers are off. Cheers.
  2. Hey Helen, Oh really? Sorry, im new to BTSync, i didnt actually realise that the old .SyncIgnore file didnt actually sync between the clients. When i googled around, i came across few comments implying that it was synced across the clients, thus my assumption. You have a fair point, but i think one of us understands the ignore file (the current .sync/IgnoreList) incorrectly (likely me, but clarify for me if you can). You, and I have a share folder. If you add "bob" to your IgnoreList on your computer, does that mean: 1. if you create a folder called bob in our shared folder, bob and its content will NOT be shared/synced to MY client/computer. 2. If I added folder called bob in to our shared folder, bob and its content will not sync to YOUR client/computer. Assuming the answer is 1 (i hope), then your example seems invalid. Because adding *.txt to B's ignore list means If B creates txt files, A and C will not see them, and adding "my secrets" to C's list means, A and B wont see "my secrets" folder and its content if added/created by C. But if the answer is 2, then well... Shouldn't the point of an "Ignore List" is a list of stuff you dont SEND, not a list of stuff you refuse to RECEIVE/DOWNLOAD? If a client doesnt want to download these folders, shouldnt this be a feature of selective sync and not added as an "ignore list"? I might be wrong, but im under the impression that if you look at almost all file share platforms (lets take git/svn/seafile as an example), the ignore list is a list of items that the client does not send (outgoing), not a list of items that the client rejects (incoming). Does BTSync really does it the other way around?
  3. +1 Can we please have a Synced Ignore file, similar to the old .SyncIgnore or git's .gitignore. Its is a huge pain to have to copy paste .sync/IgnoreList across every shared folder on every device (this is asking for trouble/accidents). Imagine if you use git for a project, and the .gitignore file is not automatically synced. I understand the .sync/IgnoreList solved a problem of having client specific ignore files, which is great. But i completely disagree with removing the project (im going to call a shared folder a project) specific ignore file (like the .SyncIgnore). Can we please have such feature again? heck, you can add a .sync/SyncIgnoreList (or /.SyncIgnoreList), a file that syncs across all shared devices and combines with the client specific .sync/IgnoreList when looking for files to ignore. Heck, if anyone has a problem with a Synced Ignore file, you can build a feature so that users can add .SyncIgnoreList to the client specific .sync/IgnoreList file to ignore the rules of the Synced .SyncIgnoreList file.
  4. Thanks for the reply. Yeah, i guessed as much, with the .SyncIgnore being superseded by .sync/IgnoreList. However, besides what you said (which is a fair point, but only affects the minority), there are no real other explanations to why the .SyncIgnore was ditched (not that i can easily find anyway). I can understand adding client specific ignore file, but removing the shared ignore file to do so feels to me like accidents waiting to happen (if you share a project folder with someone and they forget to update the ignore file for example, as opposed to the ignore file coming with the project. git projects/usage are a very good example of this, imagine if .gitIgnore didnt sync with git projects?). Just to recap what im trying to say: Current implementation solves a problem, but i disagree with removing a core feature (Synced Ignore List) to add a "different/new" feature (Unsynced Ignore List) rather than appending the said new feature while retaining the original feature. I will make a post in the suggestions thread you mentioned, but i probably shouldn't hold my breath, since the point seems to have been raised 3 years ago, and still no real update? Are you aware if this "feature" is actually being considered (or under development even), or are the developers busy with different issues/features?
  5. Hey Guys, Im new to BT Sync, but after using it for couple of days, im trying to figure out how this ignorelist works. I have come across the documentation here. However, the problem im having is, say you have 3 computers syncing a folder "F1". if you want to add say "*.txt" to the ignore list, you have to goto EVERY computer and edit /.sync/IgnoreList file and add "*.txt". Is there really no other alternative to this, where you can SYNC the Ignore List? As you can tell, this is a real pain. I have quite few folders synced with few computers, and i need to add IDE folders, build folders and other folder/wildcards to ignore list depending on projects stored on these folders, and doing this manually for every folder on every computer (and every time i need to make a change), well, is painful. For example, what im getting to is similar to git's .gitignore. If such exists, can someone please show me? I have also come across mentions of .SyncIgnore (here), which i think essentially does what im wanting, but this was removed in the newer versions? My main questions are, am i missing something (or mistaken)? If not, how come such feature does not exists (removed even)? Was there a huge issue with such implementation? Is there any plans of adding such feature in the near future? Cheers