The free version of mapbox has request limits. If anybody who deploys Ushahidi uses the same shared mapbox key, this might lead to reaching these limits quickly? @sameroom-bot
[David Losada, Ushahidi] Dear @ptandler:[matrix.org](http://matrix.org) , that’s a great question. The folks at Mapbox have been very gracious with us and our mission, and as such the limits of the keys we have with them are a bit more generous than usual.
As long as each individual deployer keeps the usage to normal levels and there are no cases of egregious abuse, there shouldn’t be any problems. In case of heavy traffic due to just organic success due to great civic impact, we would work with you and Mapbox to find a solution. If cases of abuse are detected, we would work with Mapbox to blacklist the offending domains.
In addition to that, in case you are looking to make commercial use of Ushahidi technology with Mapbox maps, we would very much encourage that you assumed Mapbox license costs in your own budget :pray:
1 reply
[Unknown] @dcardinal , if you are specifically referring to downloads, you are exactly right, platform-release is the combination of platform and platform-client , pre-arranged in an opinionated way to install them together at once.
A more flexible installation would result from downloading and setting up platform and platform-client separately , but the product functions would be the same.
@ChiefObiorah_twitter This came up last year:
[David Losada, Ushahidi] for the mobile app, I think the Ushahidi branding files are not included in the open source repository . The branding folder contains the following files:
android_banner.png: PNG image data, 1280 x 720, 8-bit/color RGB, non-interlaced android_feature.png: PNG image data, 1024 x 500, 8-bit/color RGB, non-interlaced android_icon.png: PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced android_promo.png: PNG image data, 180 x 120, 8-bit/color RGB, non-interlaced build.json: JSON data icon.png: PNG image data, 1024 x 1024, 8-bit/color RGBA, non-interlaced splash.png: PNG image data, 2732 x 2732, 8-bit/color RGBA, non-interlaced
you would have those files underprojects/<your project name>in the mobile source repo . And then set the environment variable PROJECT=<your project name> as the ionic commands are invoked
[John Obiorah] [1656331230] Sameroom: [David Losada, Ushahidi] that’s https://github.com/ushahidi/platform-mobile , @John Obiorah
<<< Thank you guys.
[John Obiorah] [1658129695] Sameroom: [Unknown] hi @John Obiorah . It should just be a matter of having the configured the proper URL pointing at the API endpoint /sms/smssync , and the same shared secret key of your choosing
<<< So how exactly would I get this accomplished. Do you have a documentation on how to achieve this or could you please tell the file to edit in order to achieve this.
[29:1agDuUpPv4NZQXHZ6x99TzTPjm3Ue7Gqi_BoRWTLFs04] [1658129695] Sameroom: [Unknown] hi @John Obiorah . It should just be a matter of having the configured the proper URL pointing at the API endpoint /sms/smssync , and the same shared secret key of your choosing
<<< So how exactly would I get this accomplished? Do you have a documentation on how to achieve this or could you please tell the file to edit in order to achieve this?
[John Obiorah] [1658154394] Sameroom: [David Losada, Ushahidi] @John Obiorah please take a look at the Platform user manual, if you haven’t yet: https://docs.ushahidi.com/ushahidi-platform-user-manual/3.-configuring-your-deployment/3.4-data-sources#3-4-5-smssync
<<< Many thanks David Losada. The link you shared is quite helpful. The Ushahidi mobile app on Google Play upon download to android devices renders the survey forms broken. I dunno whether this experience has been reported by others using self-hosted platform-release system. Another question I have is what could be to make the Ushahidi deployment to be stunningly fast? Could this be achieved with Redis?
First time we are hearing. @John Obiorah could you please create an issue here : https://github.com/ushahidi/platform/issues ?
There are some bottlenecks we are working on, which makes the stunning bit not really so.. stunning . But yes, any sort of caching, Redis or Memcached will help a great deal. The other thing is the client, make sure your hosting of the client assets is configured for high performance : compression, client-side caching, http/2 are keywords there
https://www.meetup.com/ushahidi-community/events/287071242/
https://www.meetup.com/ushahidi-community/events/287266433/