Admin UI to manage content for sites built by Beacon.

Pre-release version. You can expect incomplete features and breaking changes before a stable v0.1.0 is released.

• Erlang/OTP v25.1
• Elixir v1.13.4

LiveAdmin requires at least one site running to manage, so let's start LiveAdmin first and then start a sample site.

1. Setup your local env

mix setup

2. Run LiveAdemin

iex --sname admin -S mix dev

Keep this instance running.

3. Open another terminal or tab, clone Beacon into another directory and follow the Local Development instructions to get a site up and running.

4. Open http://localhost:4002/admin

You'll notice that no site is displayed, that's because Beacon LiveAdmin looks for sites running in the cluster and the two nodes aren't connected yet.

5. In the beacon iex terminal (the last one you started) execute the following:

{:ok, hostname} = :inet.gethostname()
node = :"admin@#{List.to_string(hostname)}"
Node.connect(node)

Now you should see a site listed in the admin home page.

6. (Optional) Automically connect the nodes by creating a .iex.exs file in the root of each repository:

In the beacon repo:

{:ok, hostname} = :inet.gethostname()
node = :"admin@#{List.to_string(hostname)}"
Node.connect(node)

In the beacon_live_admin repo:

{:ok, hostname} = :inet.gethostname()
node = :"core@#{List.to_string(hostname)}"
Node.connect(node)

This way you don't need to manually connect the nodes as shown on step 5.

Running tests requires booting a VM to run Beacon sites, which may be blocked by the firewall in your environment.

Make sure both epmd and beam.smp processes are allowed and try running the application before running tests:

iex --sname admin -S mix dev

At DockYard we are ready to help you build your next Elixir project. We have a unique expertise in Elixir and Phoenix development that is unmatched and we love to write about Elixir.

Have a project in mind? Get in touch!