Skip to content

Commit 1087775

Browse files
authored
fix: Change URLs in Readme and fix example (#13)
1 parent 4685aaa commit 1087775

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Postgres Strategy for [libcluster](https://hexdocs.pm/libcluster/) which is used
88

99
You can test it out by running `docker compose up`
1010

11-
![example.png](example.png)
11+
![example.png](https://github.com/supabase/libcluster_postgres/blob/main/example.png?raw=true)
1212

1313
## Installation
1414

@@ -29,7 +29,7 @@ To use it, set your configuration file with the informations for your database:
2929
config :libcluster,
3030
topologies: [
3131
example: [
32-
strategy: Cluster.Strategy.Postgres,
32+
strategy: LibclusterPostgres.Strategy,
3333
config: [
3434
hostname: "localhost",
3535
username: "postgres",
@@ -65,7 +65,7 @@ end
6565

6666
At Supabase, we use clustering in all of our Elixir projects which include [Logflare](https://github.com/Logflare/logflare), [Supavisor](https://github.com/supabase/supavisor) and [Realtime](https://github.com/supabase/realtime). With multiple servers connected we can load shed, create globally distributed services and provide the best service to our customers so we’re closer to them geographically and to their instances, reducing overall latency.
6767

68-
![Example of Realtime architecture where a customer from CA will connect to the server closest to them and their Supabase instance](realtime_example.png)
68+
![Example of Realtime architecture where a customer from CA will connect to the server closest to them and their Supabase instance](https://github.com/supabase/libcluster_postgres/blob/main/realtime_example.png?raw=true)
6969

7070
Example of Realtime architecture where a customer from CA will connect to the server closest to them and their Supabase instance
7171
To achieve a connected cluster, we wanted to be as cloud-agnostic as possible. This makes our self-hosting options more accessible. We don’t want to introduce extra services to solve this single issue - Postgres is the logical way to achieve it.

example/config/config.exs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ config :logger, :console,
55

66
config :libcluster, topologies: [
77
postgres: [
8-
strategy: Cluster.Strategy.Postgres,
8+
strategy: LibclusterPostgres.Strategy,
99
config: [
1010
hostname: "db",
1111
username: "postgres",

example/mix.exs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ defmodule Example.MixProject do
2323
defp deps do
2424
[
2525
{:libcluster, "~> 3.3"},
26-
{:libcluster_postgres, path: "../"}
26+
{:libcluster_postgres, "~> 0.1.0"}
2727
]
2828
end
2929
end

mix.exs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ defmodule LibclusterPostgres.MixProject do
55
[
66
name: "libcluster_postgres",
77
app: :libcluster_postgres,
8-
version: "0.1.0",
8+
version: "0.1.1",
99
elixir: "~> 1.14",
1010
start_permanent: Mix.env() == :prod,
1111
deps: deps(),

0 commit comments

Comments
 (0)