Skip to main content

16.17.2 Pushing to the mobile application

The command org-mobile-push copies files listed in org-mobile-files into the staging area. Files include agenda files (as listed in org-agenda-files). Customize org-mobile-files to add other files. File names are staged with paths relative to org-directory, so all files should be inside this directory1.

Push creates a special Org file ‘agendas.org’ with custom agenda views defined by the user2.

Finally, Org writes the file ‘index.org’, containing links to other files. The mobile application reads this file first from the server to determine what other files to download for agendas. For faster downloads, it is expected to only read files whose checksums3 have changed.

  1. Symbolic links in org-directory need to have the same name as their targets.↩
  2. While creating the agendas, Org mode forces ‘ID’ properties on all referenced entries, so that these entries can be uniquely identified if Org Mobile flags them for further action. To avoid setting properties configure the variable org-mobile-force-id-on-agenda-items to nil. Org mode then relies on outline paths, assuming they are unique.↩
  3. Checksums are stored automatically in the file ‘checksums.dat’.↩