Platform User Manual
[Legacy v3] User Manual
[Legacy v3] User Manual
  • [Legacy v3] Ushahidi Platform User Manual
  • Navigating the Ushahidi Platform User Manual
  • About Ushahidi
  • Overview of Ushahidi Platform v3.0
    • Technical Specifications
  • 1. Installing Ushahidi Platform
  • 2. Setting up a deployment
    • 2.1 Upgrading/Downgrading your deployment plan
  • 3. Configuring your deployment
    • 3.1 Accessing your deployment
    • 3.2 General Settings
    • 3.3 Surveys
    • 3.4 Data Sources
    • 3.5 Categories
  • 4. Managing People on your deployment
    • 4.1 Roles
    • 4.2 Users
  • 5. Modes for visualizing and managing data on your deployment
    • 5.1 Map View
    • 5.2 Data view
    • 5.3 Activity view
  • 6. Managing Data in your deployment
    • 6.1 Viewing Posts
    • 6.2 Filtering Posts
    • 6.3 Adding Posts
    • 6.4 Editing Posts
    • 6.5 Translating Posts
    • 6.6 Publishing Posts
    • 6.7 Deleting Posts
    • 6.8 Importing Data
    • 6.9 Exporting Data
      • 6.10 HDX integration
  • 7. Managing your Donations
    • 7.1 Donations
  • 8. Analysing Data on your deployment
    • 8.1 Saved Searches
    • 8.2 Collections
  • 9. Additional Links
Powered by GitBook
On this page
  1. Overview of Ushahidi Platform v3.0

Technical Specifications

PreviousOverview of Ushahidi Platform v3.0Next1. Installing Ushahidi Platform

Better development stack

Ushahidi 3.x is built on a modern PHP stack: dependencies are managed with composer, we’re using Kohana 3 but phasing that out, and we’ve isolated the core logic of the platform standalone Entity and Usecase classes.

The user interface of Ushahidi 3.x is now a separate app (the client) built purely in JS, HTML + CSS using AngularJS and a collection of other libraries. Again this uses a modern stack, with a build pipeline using gulp and browserify.

What’s new (and improved)?

  • Dependencies are properly managed and easier to update or replace needed.

  • We’re using our own API to build the app, it gets first class support.

  • You can work on just the UI without delving into the API code

  • Modern libraries mean they’re still being supported, we don’t have the burden of supporting legacy libraries ourselves.

Code is easier to customize

  • It’s more structured making it easier to find what you want

  • It doesn’t repeat itself so a change can be made in one place, not need to be copied everywhere else

  • UI is isolated to the client, allowing work on just the UI without having to delve into the API code

The stack

  • Back-end: , , /, or PostgreSQL

  • Front-end: , , , . Built with and . Using for mapping, and a collection of other frontend libraries

Linux
PHP
Apache
Nginx
MySQL
AngularJS
Javascript
Html
CSS
NodeJS
Browserify
Leaflet