Flick is a simple Elixir / Phoenix LiveView app that helps capture ranked votes. You can see this project in action at https://rankedvote.app/.
This project was built to help the Elixir Book Club pick books, but it is open to all.
- No accounts are needed to create ballots or cast votes.
- Votes are ranked votes that help find a better overall consensus.
- Individual voters can be weighted.
- A ballot can be closed, stopping future votes from being cast.
- The project is very trusting and has no aggressive security against people voting more than once. Flick is intended for honest polling.
- See Issues for more.
YouTube: https://www.youtube.com/watch?v=pxE6AbaQuUM
This project is built using Elixir and Erlang, and as such we define specific version targets using .tool-versions a file format of the asdf project. Please refer to it for various installation options. Once installed, run the following from the project root to make sure you have the required versions.
$ asdf installThis project requires a Postgres database for storage and a Docker Compose file to run a containerized version is provided via compose.yml. You are not required to run Postgres via a container, and a standard on metal installation should work fine too.
Before attempting to run the Phoenix app, be sure to start the Docker container with:
$ docker compose up -dTo shutdown you can run:
$ docker compose down -dTo start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Flick is set up for worktrunk (wt), which creates git worktrees so that several copies of the app, or several coding agents, can run side by side. Nothing above depends on it. A normal checkout ignores these files and keeps port 4000 and the flick_dev database.
A worktree made with wt gets its own copy of _build and deps, its own port, and its own dev and test databases. The port and database names are in the worktree's .env.worktree, which config/runtime.exs reads.
Set up each machine once with the runbook's setup steps. Flick's .config/wt.toml calls a hook script installed by those steps. Without it, wt reports an error and leaves the worktree without its databases, and mix in that worktree refuses to start rather than fall back to flick_dev.
Create and remove these worktrees only with wt, because its hooks create the databases and drop them again. A worktree removed any other way leaves its databases behind. The worktree runbook in zorn/dotfiles covers the full flow: setup, creating and opening a worktree in Herdr, working in it, removing it, and what to do when removal stops.
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix