Skip to content
Elixir JavaScript CSS HTML Other
Branch: master
Clone or download
anaPerezGhiglia and bcardiff Fix cancel survey tests (#1553)
* SurveyController.cancel_messages_and_respondents: return list of consumers pids instead of producer pid

* Cancelling Survey: extract logic of starting producer and consumers to Ask.SurveyCanceller
Latest commit d542042 Nov 13, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib Fix cancel survey tests (#1553) Nov 13, 2019
locales Allow surveys to be terminated in background processes (#1539) Nov 6, 2019
priv Merge branch 'release/0.22' Sep 5, 2019
.babelrc WIP: Adding Flow Nov 29, 2016
.eslintrc Fixed warnings generated from survey charts. Removed react-d3-library… Aug 3, 2017
.flowconfig Tag strings in ConfirmationModal (for #1245) Mar 5, 2018
.iex.exs Added some imports to IEx environment Sep 15, 2016
Dockerfile Enable remote shell for Elixir process (closes #1511) Sep 5, 2019
Vagrantfile Migrated JS building to webpack Jun 7, 2017
package-lock.json Feature/floip (#1232) Apr 24, 2018
package.json Updated surveda d3 components to version 1.0.13 and modified calculat… Oct 1, 2019
webpack.config.js Workaround for erratic dropdown controls in Chrome (fixes #1491) Sep 5, 2019


Dockerized development

To get started checkout the project, then execute ./

To run the app: docker-compose up

Now you can visit localhost:4000 from your browser.

To open a shell in a container: docker-compose exec db bash, where db is the service name. You can list the services docker-compose ps --services.

To start an Elixir console in your running Phoenix app container: docker-compose exec app iex -S mix.

Exposing your containers as *

You can use dockerdev to access the web app at and ngrok at

Just follow the instructions at the README of dockerdev.

WARNING: You should install dockerdev before creating your stack's network in Docker. If you have already run ./, you may want to run docker-compose down -v to delete every container, data and other artifacts from the project and start from scratch after running dockerdev.

Linting and Formatting

To help us keep a consistent coding style, we're using StandardJS. Follow their instructions to install it:

If you're using Sublime, you can setup a Build System that will use StandardJS to format your code when you hit Ctrl+B. To do so:

  1. In Sublime, go to Tools -> Build System -> New Build System...
  2. A file will open, replace its contents with:
  "cmd": ["standard", "--fix", "$file"],
  "selector": "source.js"
  1. Save. That's it. When you want to format, just hit Ctrl+B. Note that the formatter is a bit slow, so it's not a good idea to format on save.

IVR channels with Verboice

To setup a channel you need to create it using the console. For that you need to create a channel with the folowing settings:

%Ask.Channel{name: "Channel name",
  provider: "verboice",
  settings: %{
    "channel" => "Verboice Channel name in Verboice",
    "username" => "Your Verboice username",
    "password" => "Your Verboice password",
    "url" => ""
  type: "ivr",
  user_id: your ask user id

In order for it to work, that Verboice channel must be associated to a dummy flow of a dummy Verboice project. Otherwise it will fail and won't log anything.


You need GUISSO to access Verboice and/or Nuntium channels.

Get a working GUISSO instance (online, or hosted on your development machine) and create a new Application. If it's a local Guisso instance, use as the domain, and this two redirect URIs:

To work with a cloud GUISSO, make sure your ngrok service is running (docker-compose up ngrok), and get your ngrok domain visiting Fill the Application information as for the local case, but using the ngrok domain instead. When you restart your ngrok service, you will need to update this information before approving new authorizations in GUISSO.

On your local surveda directory, create a config/local.exs file like below, including the client ID & secret from your Application in GUISSO:

use Mix.Config

config :alto_guisso,
  enabled: true,
  base_url: "", # or for a cloud GUISSO
  client_id: "<your app's client id in guisso>",
  client_secret: "<your app's client secret in guisso>",

config :ask, Ask.Endpoint,
  url: [host: ""] # or "" for a cloud GUISSO

Verboice Channel

Once you have GUISSO enabled on Surveda, you can connect a Verboice instance that's already registered with GUISSO by adding this fragment to your config/local.exs:

config :ask, Verboice,
  base_url: "", # or the URL for your Verboice instance
  channel_ui: true,
  guisso: [
    base_url: "", # or the URL for your GUISSO
    client_id: "<Surveda's client id>",
    client_secret: "<Surveda's client secret>",
    app_id: "" # or your Verboice APP ID in GUISSO



We're using Coherence to support registration, authorization, and other user management flows. If you need to upgrade the version of Coherence that Ask uses, there are some steps that you need to mind. Please check them out here:

Coherence Mails

Coherence uses Swoosh as it's mailer lib. In development, we use Swoosh's local adapter, which mounts a mini email client that displays sent emails at {BASE_URL}/dev/mailbox. That comes handy to test flows which depend on email without having to send them in development.


Surveda supports Intercom as its CRM platform. To load the Intercom chat widget, simply start Surveda with the env variable INTERCOM_APP_ID set to your Intercom app id (

Surveda will forward any conversation with a logged user identifying them through their email address. Anonymous, unlogged users will also be able to communicate.

If you don't want to use Intercom, you can simply omit INTERCOM_APP_ID or set it to ''.

To test the feature in development, add the INTERCOM_APP_ID variable and its value to the environment object inside the app service in docker-compose.yml.

InSTEDD's url shortener

Surveda uses InSTEDD's shorter for sending urls to respondents when web-mobile mode is used.

Is necessary to configure an api-key in surveda to use this service. If no api-key is provided, surveda works fine but full-urls are sent to respondents

For editing/creating a new api-key:

  1. Go to AWS console
  2. Go to API Gateway service
  3. Select Usage-Plans
  4. Select "Surveda Shorter" plan
  5. Edit or create under "API Keys" tab
You can’t perform that action at this time.