Slack-Clone | full stack web application | Websocket library

wait-for-it.sh by default waits for 15 seconds and returns, even if the target isn't ready yet. You see that in your output too. But the database isn't ready yet. Make wait-for-it.sh wait longer, maybe with -t 90 to wait for 90 seconds or -t 0 to make it wait forever.

(In my experience the Docker database containers routinely take 30-60 seconds to start up, especially the first time.)

They are custom elements. In regards to the tag's validity, you may have noticed that it is not defined anywhere in the code. As per step 5 of the spec, it is valid, and has a namespace of Element.

For a higher-level overview of custom elements, take a look at the MDN tutorial on using custom elements.

An additional note: These tags could be replaced by regular

I think you need to add this to your pipeline:

One way to think about contexts is to view them as a layer of abstraction when you are designing your app. As it is put in the docs,

Phoenix projects are structured like Elixir and any other Elixir project – we split our code into contexts. A context will group related functionality, such as posts and comments, often encapsulating patterns such as data access and data validation. By using contexts, we decouple and isolate our systems into manageable, independent parts.

Models themselves with their underlying schema are therefore the units which you group into contexts. Models can have more fine-grained api which is necessary for their inner workings. Contexts in turn only expose methods which are useful to other application components or contexts, thus hiding the underlying implementation detail of the models.

It is not necessary to extend the context boundary down through the models level for absolute isolation. Instead you create your schema as usual, with all the many-to-many relations you need on the models. Then implement whatever low-level methods on the models directly. Put in the context only those methods which are either public api of the context or private methods touching more than one model.

UPDATE

In your scenario you might have e.g. Chats context where you put the rooms method. Its signature might be e.g. Chats.rooms_of(user). Repo.get() also goes to the context as, e.g. def get(id), do: Repo.get(User, id). The models end up containing changesets, validation methods, private methods with no dependencies to other models. The context in turn gets most of the group's publicly available business logic methods.

It looks like you need to add a route to the controller that you want to handle for the path /.

There are a couple of ways to handle it. You should check out the Phoenix Routing guide. One of the ways to handle this is to add something like the following inside your api scope.:

Documents in DocDB are stored in Collections. Collections can hold any kind (schema-free) document and are the billable unit. (See the Hierarchical model here).

You are correct about DocDB when you say you'd need to update the entire document, you cannot do partial updates, so in your original approach, it will turn into a slower process each time a new message arrives.

But you can refactor the design for smaller documents and still query the user1 / user2 relationship with something like:

Resolved with these

This error message usually means you're getting a non-JSON response. If you look at the raw response in the Network tab of your debugger, you should be able to see what you're getting back from the server.

It's a bug in Firebase 3.7.1. When I reverted to Firebase 3.7.0 my code works and my browsers don't freeze. I've reported the bug to Firebase.