RemoteRetro alternatives and similar packages
Based on the "Applications" category.
Alternatively, view RemoteRetro alternatives based on common mentions on social networks and blogs.
8.0 0.0 RemoteRetro VS AlloyCIContinuous Integration, Deployment, and Delivery coordinator, written in Elixir.
7.6 5.2 RemoteRetro VS CaptainFact🔎 CaptainFact - API. The one that serves and process all the data for https://captainfact.io
4.7 0.0 RemoteRetro VS QueerlinkA simple yet efficient URL shortening service written in Elixir
2.3 0.0 RemoteRetro VS medexMedical Examination - application for register health check callbacks and represent their state via HTTP.
Do you think we are missing an alternative of RemoteRetro or a related project?
This repository houses the application code for RemoteRetro.org, a free web app that allows distributed teams to conduct Agile retrospectives. It is written in Elixir/Phoenix/React/Redux, and is sponsored by Stride Consulting.
Table of Contents
- Project Management
- Dev Environment Setup
- Code of Conduct
To see the project's current feature pipeline, simply install the wonderful ZenHub Chrome Extension.
- visit ZenHub.com, install the ZenHub Chrome Extension, and authorize when prompted
- Note: this installation assumes you visit zenhub.com using Chrome
- once the extension is installed, you should be able to visit the boards by typing 'b', or, if clicking is more your speed, simply click the "Boards" tab on the repo's homepage
Dev Environment Setup
- Install Homebrew
- Note: You'll be prompted to install the command-line developer tools. Do it.
- Install PostgreSQL via Homebrew:
brew install postgresql # (follow directions supplied by brew output upon successful installation) createdb # depending on how you installed postgres, this user may already exist createuser -s postgres # make sure you can log in to default database psql -h localhost
- Install the asdf version manager
- Install Erlang, Elixir, and their dependencies by running
- Create the "remote_retro_dev" database and migrate via
mix ecto.create && mix ecto.migrate
- Create the "remote_retro_test" database and migrate via
MIX_ENV=test mix ecto.create && mix ecto.migrate
- Ensure you have the asdf version manager installed
- Install the project's Node version and Node dependencies by running
Authentication within Remote Retro relies on Google OAuth and the Google+ API. To set this up, navigate to the Google API console and create a new project: https://console.developers.google.com/apis
Next, click on "Credentials" in the left sidebar nav. On the right hand side, click on the "Create Credentials" button and select "OAuth client ID".
- Application type: Web application
- Authorized redirect URIs:
Click on the Create button. Using the information Google provides, add the following lines to your profile and source (or open a new terminal).
export REMOTE_RETRO_GOOGLE_OAUTH_CLIENT_ID="<Client Id>" export REMOTE_RETRO_GOOGLE_OAUTH_CLIENT_SECRET="<Client secret>" export REMOTE_RETRO_GOOGLE_OAUTH_REDIRECT_URI="http://localhost:4000/auth/google/callback"
Finally, enable the Google+ API for your project.
Start Phoenix endpoint with
Now you can visit
localhost:4000 from your browser.
To continually execute the backend unit tests on file change:
To execute the backend unit tests manually:
To execute the end-to-end tests:
To continually execute the client-side unit tests on file change:
To execute the client-side unit tests manually:
To run the local eslint:
Code of Conduct
[The Contributor Covenant](CODE_OF_CONDUCT.md)
Many thanks to the project's contributors for devoting their time, energy, and passion, and additional thanks go out to the leadership of Stride Consulting for giving this project the opportunity it needed to bloom.
*Note that all licence references and agreements mentioned in the RemoteRetro README section above are relevant to that project's source code only.