-
Notifications
You must be signed in to change notification settings - Fork 31
Internal API usage overview
Stellan Lagerström edited this page Jun 11, 2019
·
4 revisions
- The app writes each form instance answers into a JSON file.
- The JSON file is then packed into a zip file.
- The zip file is stored in the S3 bucket, /devicezip folder, using the awsXxx credentials.
- Any media files are stored in the /images folder.
- The app then triggers the ingestion process by calling GET /processor?action=submit&formID=nnnn&fileName=5174ef3c-f2ba-4a32-a4f6-b2ad7d82d0ce.zip{+device-identifying info}
- ProcessorServlet checks that the formID exists, and forks to a task (on the default queue) at /app_worker/task?action=processFile&fileName=xxxx{+device-identifying info}
- TaskServlet tries to fetch and extract the file from the zipfile. If that fails, it will retry 7 times at 20-second intervals.
- A DeviceFile entity is created in the DS, and the answers are parsed.
About Akvo Flow
Akvo Flow API
Developer Guides
- Deployments
- Development tools
- Android emulator setup
- Creating New Dashboard Instances
- Disabling Dashboard Instances
- Adding Translations to Dashboards
- Setup your development environment with IntelliJ IDEA
- Setup your development environment on Windows OS
Technical Specification
Regression Tests