Mozilla Hubs

Important resources

https://github.com/mozilla/hubs

https://github.com/mozilla/hubs-compose/

https://github.com/albirrkarim/mozilla-hubs-installation-detailed

https://github.com/mozilla/reticulum

https://github.com/mozilla/hubs-ops

Edit Rooms

You need to allow "Remixing" in Spoke (by ticking the checkbox after pressing the blue "Publish to Hubs..." button, see:

https://imgur.com/RMQFDYo.png

Hubs-compose

Base installation

sudo apt install vim git docker docker-compose tmux htop
sudo systemctl enable docker --now
wget https://github.com/mutagen-io/mutagen/releases/download/v0.17.2/mutagen_linux_amd64_v0.17.2.tar.gz
wget https://github.com/mutagen-io/mutagen-compose/releases/download/v0.17.2/mutagen-compose_linux_amd64_v0.17.2.tar.gz
tar xvzf mutagen_linux_amd64_v0.17.2.tar.gz
tar xvzf mutagen-compose_linux_amd64_v0.17.2.tar.gz
rm -f mutagen-compose_linux_amd64_v0.17.2.tar.gz mutagen_linux_amd64_v0.17.2.tar.gz
sudo mv mutagen mutagen-compose /usr/local/bin/
git clone https://github.com/mozilla/hubs-compose.git
cd hubs-compose
sudo mutagen daemon start
sudo ./bin/init

Activate admin account

Stop docker container and start it with a shell as entry point and manually start the reticulum server. Using the iex shell, create an admin account.

• https://stackoverflow.com/questions/32353055/how-to-start-a-stopped-docker-container-with-a-different-command

sudo mutagen-compose stop reticulum
sudo mutagen start -it --entrypoint=sh reticulum

Now we should be inside the container - indicated by /code #

iex -S mix phx.server
Ret.Account |> Ret.Repo.all() |> Enum.at(0) |> Ecto.Changeset.change(is_admin: true) |> Ret.Repo.update!()

Email

https://github.com/mozilla/reticulum/issues/653

edit /config/dev.exs

config :ret, Ret.Mailer,
  # adapter: Bamboo.LocalAdapter
  adapter: Bamboo.SMTPAdapter,
  server: "smtp.gmail.com",
  hostname: "your.fqdn",
  port: 465,
  username: "xxxxxxxxxxxx@gmail.com",
  password: "xxxxxxxxxxxx",
  tls: :always, # can be `:always` or `:never`
  ssl: true, # can be `true`
  retries: 1

Hints

- If the admin panel stays blank. Visit all open ports via browser and accept the self-signed certificate.

- If mutagen is complaining about deamon/version conflict. Try downgrading to 17.2. I faced similar issues with version 17.4.

My Dev instance

https://tobias-weiss.org:8888/

Manage start with pm2

https://github.com/Unitech/pm2

npm install pm2 -g

pm2 start "npm run dev" --name hubs

pm2 restart hubs --watch