Skip to content

Commit

Permalink
Merge pull request DockYard-Academy#126 from DockYard-Academy/fix-cod…
Browse files Browse the repository at this point in the history
…espell

Fix codespell
  • Loading branch information
BrooklinJazz committed Jul 10, 2022
2 parents 9c08014 + f5b4621 commit 93e4693
Show file tree
Hide file tree
Showing 4 changed files with 33 additions and 4 deletions.
2 changes: 1 addition & 1 deletion reading/html_css.livemd
Original file line number Diff line number Diff line change
Expand Up @@ -317,7 +317,7 @@ All elements, regardless of type, will be selected.

<!-- livebook:{"break_markdown":true} -->

### Futher Selectors
### Further Selectors

See the [MDN CSS Selectors](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors) documentation for a complete guide on CSS selectors.

Expand Down
2 changes: 1 addition & 1 deletion reading/phoenix.livemd
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ Phoenix breaks the complexity of our application into several layers with differ
* **Controller**: Handles the request—generally, the controller delegates to the Model and View to manipulate business logic and return a response.
* **Model**: Contains the application's business logic, often separated into the **Context** and the **Schema** if the application has a data layer.
* **View**: Handles returning the response, may delegate to a template.
* **Template**: Builds a response, typically using HEEx (HTML + Elixir) to programatically build an HTML web page using both HTML and Elixir.
* **Template**: Builds a response, typically using HEEx (HTML + Elixir) to programmatically build an HTML web page using both HTML and Elixir.

<!-- livebook:{"break_markdown":true} -->

Expand Down
29 changes: 29 additions & 0 deletions reading/phoenix_and_ecto.livemd
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Phoenix and Ecto

```elixir
Mix.install([
{:kino, github: "livebook-dev/kino", override: true},
{:kino_lab, "~> 0.1.0-dev", github: "jonatanklosko/kino_lab"},
{:vega_lite, "~> 0.1.4"},
{:kino_vega_lite, "~> 0.1.1"},
{:benchee, "~> 0.1"},
{:ecto, "~> 3.7"},
{:math, "~> 0.7.0"},
{:faker, "~> 0.17.0"},
{:utils, path: "utils"},
{:httpoison, "~> 1.8"},
{:poison, "~> 5.0"}
])
```

## Navigation

[Return Home](../start.livemd)<span style="padding: 0 30px"></span>
[Report An Issue](https://github.com/DockYard-Academy/beta_curriculum/issues/new)

## Setup

Ensure you type the `ea` keyboard shortcut to evaluate all Elixir cells before starting. Alternatively you can evaluate the Elixir cells as you read.

## Overview

4 changes: 2 additions & 2 deletions reading/web_servers.livemd
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ Transmission Control Protocol (TCP) is the communication protocol applications u
We use the built in `:gen_tcp` library to from Erlang to start a server that uses TCP to listen for connections on a network.

This server creates a **socket** connection on a specified **port** of the machine.
A port is a communication endpoint for a particular service. For example, by default this livebook application runs on port `8080` which you can see in the url of your browser. `http://localhost:8080/sessions/`. A socket allows for two way communication over this port to send and recieve data.
A port is a communication endpoint for a particular service. For example, by default this livebook application runs on port `8080` which you can see in the url of your browser. `http://localhost:8080/sessions/`. A socket allows for two way communication over this port to send and receive data.

<!-- livebook:{"break_markdown":true} -->

Expand Down Expand Up @@ -150,7 +150,7 @@ WebServer.start(4000)

This server will remain open indefinitely and recursively call `accept/2` every time a new client connects to the socket on port `4000`.

All websites use a similar (albiet more fully featured) web server to accept client connections, recieve requests, and send responses back.
All websites use a similar (albeit more fully featured) web server to accept client connections, receive requests, and send responses back.

Hopefully, this example provides you context on how web servers operate under the hood. However, it's rarely practical to build our own web server, and instead we'll rely on the Phoenix Framework which hides these implementation details from use.

Expand Down

0 comments on commit 93e4693

Please sign in to comment.