Pushing to the mobile application (The Org Manual)

Next: Pulling from the mobile application, Previous: Setting up the staging area, Up: Org Mobile [Contents][Index]

#### 16.16.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 directory152.

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

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 checksums154 have changed.

#### Footnotes

### (152)

Symbolic links in `org-directory` need to have the same name as their targets.

### (153)

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.

### (154)

Checksums are stored automatically in the file ‘`checksums.dat`’.