1. 24 Jan, 2015 2 commits
  2. 03 May, 2014 2 commits
    • Sriram Karra's avatar
      Remove code added for tracking server sync state · 5a682fed
      Sriram Karra authored
      As explained in previous commit comments we cannot use Exchange
      server side sync state completely for our bi-dirctional sync
      use case. In view of the fact that we have reimplemented this
      manually, let's get rid of the stuff that was added for supporting
      the Exchange sync folder stuff.
    • Sriram Karra's avatar
      Add ability to save the sync state from server to state.json · d78b9ef5
      Sriram Karra authored
      If we want to use the exchnage sync state support for synching we will need
      abilityt to store collection level sync state inthe state.json
      With this commit we add the requried support as well use that infra
      to retreive and store the state during sync operations.
      Note that there is a problem with this approach, as the exchange
      sync state cannot be fetched after a push to the server... making
      it virtually useless. Need to figure out the best way to work aroud
  3. 02 May, 2014 1 commit
  4. 01 May, 2014 1 commit
  5. 29 Apr, 2014 1 commit
    • Sriram Karra's avatar
      Ability to create profiles contaiing Exchnage · c2a05d80
      Sriram Karra authored
      - Refactor some of the authentication code
      - enable 'ex' as a valid option while create-profiles
      Now I am abel to create a testbbex profile, and also to list the
      avaiable folders in an exchange store.
  6. 16 Dec, 2013 1 commit
  7. 12 Dec, 2013 1 commit
  8. 14 Sep, 2013 1 commit
  9. 25 Aug, 2013 1 commit
  10. 21 Aug, 2013 1 commit
  11. 12 Aug, 2013 1 commit
  12. 19 Jul, 2013 1 commit
  13. 18 Jun, 2013 1 commit
  14. 15 May, 2013 1 commit
    • Sriram Karra's avatar
      Auto migrate user custom json system to config.py based system · f03e1dba
      Sriram Karra authored
      The existing config.json system is not very amenable to changes.
      We realzed this when the carddav branch made some changes an
      introduced v5 of the json. PUshing out major updates like this
      can be intrusive to those users who have made customizations to
      their copy of the config.json file. To address this issue, The
      modified protocol will be as follows:
      - Teh system will load the stock version of the latest config json
      - the parsed config dictionary will be passed to the user in
        user_dir/config.py which can be any python code. It is expected
        that the user modifies the config idctionary and sends it back
      This way we can keep pushing updates to teh config json while
      seamlessly retaining the user customizations.
      In this patch, the auto migrate will work if the user has not
      made any changes to his json. If we identify any changes then
      The auto migrate will stop and user will be asked to manually
      migrate his changes.
  15. 19 Apr, 2013 1 commit
  16. 16 Apr, 2013 1 commit
  17. 15 Apr, 2013 3 commits
  18. 10 Apr, 2013 1 commit
  19. 09 Apr, 2013 1 commit
  20. 04 Apr, 2013 1 commit
  21. 01 Apr, 2013 1 commit
  22. 31 Mar, 2013 1 commit
    • Sriram Karra's avatar
      Support ~/.netrc entries for specifying gmail passwords · 9dcdbde7
      Sriram Karra authored
      Currently ASynK does not store any passwords (for your gmail profiles).
      The user is prompted for the password at the right time, and the
      password is echoed on the screen. It is done this way because
      getpass does not work well with input redirection, so someone who
      wants to avoid typing the password everytime faces an issue.
      With this fix we leverage the age-old ~/.netrc file format to store
      credentials needed by ASynK. Here is how it works:
      - Add an entry in ~/.netrc with machine as 'gc_xxxx' where xxxx is the
        name of your sync profile
      - For your gc_xxxx machine, add a login that is your gmail id
      - Also give a password in cleartext that is your gmail password.
      A sample entry will look like this:
      machine gc_testbbgc
        login yyyy
        password xxxx
      Here we have a sync profile called testbbgc, which is syching your
      bbdb to yyyy@gmail.com and your password is xxxx
      Note following behaviours:
      - If your profile is configured with a differnet login id, then this
        ~/.netrc entry is ignored
      - If you provide a password on the command line, this ~/.netrc entry
        is ignored
      If you have no matching entry in netrc and nothing is provided on the
      command line, then the current behaviour will be retained. (this can
      now be changed to getpass...)
  23. 27 Mar, 2013 1 commit
  24. 24 Mar, 2013 2 commits
  25. 21 Mar, 2013 2 commits
  26. 19 Mar, 2013 1 commit
    • Sriram Karra's avatar
      Bugfix: Ensure sync_dir option of SYNC1WAY does the right thing · 355247fa
      Sriram Karra authored
      Due to erroneos initialization of profile settings after reading
      from config file / command line, a state.json configuration setting
      was not working as expected when sycn_dir was set to SYNC1WAY. If hte
      --sync-dir=1way was set, it should have worked as expected.
      This is now fixed.
      Noted that the same issue was present with the conflict_resolve
      option. This is also fixed now.
  27. 05 Jan, 2013 1 commit
  28. 29 Nov, 2012 1 commit
  29. 16 Oct, 2012 1 commit
  30. 05 Jul, 2012 2 commits
  31. 02 Jul, 2012 2 commits
    • Sriram Karra's avatar
      Use sane defaults for store and folder ids if they are null in config · b7276b54
      Sriram Karra authored
      This is the final step needed to support a 'sane' sync option
      with minimal configuration.
      Basically, if a user has just fetched ASynK, the most likely common case
      scenario will be to just sync his entire BBDB to the My Contacts folder
      in Google Contacts, or defaults contacts folder in Outlook to Google.
      With this commit that is possible.
      The way this is enabeld is any gc sync profile without a folder id is
      synhed to the My Contacts folder. If a store id is also missing a
      google contacts username is prompted for, and stored in the default storeid
      field. A similar "logical" thing is done with Outlook.
    • Sriram Karra's avatar
  32. 01 Jul, 2012 1 commit
    • Sriram Karra's avatar
      Make ASynK installable in a central directory and have per-user config dirs · 4d8e5b5f
      Sriram Karra authored
      With this change, ASynK will try to use ~/.asynk/ as the configuration
      directory to contain config.json and state.json. Also the logs and backups
      directory will be stored here.
      Note that this cannot be changed through a config.json variabel as this
      directory itself is needed to locate config.json. The following
      heuristic is used:
      Asynk user directory is set to either ~/.asynk or the value of --user-dir
      command line argument. If ~/.asynk/ is empty then the state.json and
      config.json files are copied from the asynk application root directory.
      This will help older users to transparently migrate their config and state
      files to the new location without havign to do anything else.
      Finally, made asynk.py executable so it can be executed directly.