| defmodule Projections.Repo.Migrations.CreateProjectionVersions do | |
| use Ecto.Migration | |
| def change do | |
| create table(:projection_versions, primary_key: false) do | |
| add :projection_name, :text, primary_key: true | |
| add :last_seen_event_id, :bigint | |
| timestamps | |
| end |
| #!/usr/bin/env bash | |
| set -x | |
| term_handler() { | |
| echo "Stopping the server process with PID $PID" | |
| erl -noshell -name "[email protected]" -eval "rpc:call('[email protected]', init, stop, [])" -s init stop | |
| echo "Stopped" | |
| } | |
| trap 'term_handler' TERM INT |
Heroku has a great feature called heroku ps:exec which allows you to connect to running nodes. You can use this command to connect your elixir nodes easily. And debug your nodes like in your network.
Let's start with Procfile
To run a named app at heroku your procfile should specify the app name like:
web: MIX_ENV=prod elixir --sname coolelixirapp -S mix run --no-halt
| defmodule MasterProxy.Application do | |
| alias MyApp.Endpoint, as: MyAppEndpoint | |
| alias MyApp.UserSocket, as: MyAppUserSocket | |
| alias MyOtherApp.Endpoint, as: MyOtherAppEndpoint | |
| alias MyOtherApp.UserSocket, as: MyOtherAppUserSocket | |
| alias Phoenix.LiveReloader.Socket, as: LiveReloadSocket | |
| alias Plug.Cowboy |
| defmodule Executable do | |
| @moduledoc """ | |
| Executables are either commands or queries. | |
| They should declare a struct that dictates the shape and defaults of their | |
| parameters and a `handle_execute/1` function that takes that struct and does | |
| something in response. | |
| """ | |
| use Behaviour |
| // Required Plugin: https://marketplace.visualstudio.com/items?itemName=drcika.apc-extension | |
| // settings.json | |
| { | |
| // Remove left-side icons | |
| "workbench.activityBar.location": "hidden", | |
| // Remove bottom status bar | |
| "workbench.statusBar.visible": false, | |
| // Remove position indicator in the editor's scrollbar | |
| "editor.hideCursorInOverviewRuler": true, |