Browse Source

adds docs on URIs, fixes some typos

master
apoc 5 months ago
parent
commit
b6d3299b97

+ 2
- 2
docs/Series/2. git/2.5 Gitea/2.5.2 Reading changes.md View File

@@ -1,12 +1,12 @@
In order to understand how to make changes to code within a repository you need to understand how to read changes from said repository first.

We've been through the git clone, pull, push workflow but that is meaningless if you don't have situational awareness regarding he state of the repository. Using information from documents
We've been through the git clone, pull, push workflow but that is meaningless if you don't have situational awareness regarding the state of the repository. Using information from documents

- 1.1
- 1.2
- and 2.1

you should be able to clone this repository to your computer. If it simpler to grasp you can open the repository in a web browser
you should be able to clone this repository to your computer. If it is simpler to grasp you can open the repository in a web browser

https://git.teknik.io/apoc/bazaar-design


+ 25
- 1
docs/Series/4. http, servers/4.3 Uniform resource locator.md View File

@@ -16,7 +16,7 @@ Now, of course it would be inefficient to number webpages on your website as
- Page 4
- etc

then tell your customers to find your shop/business phone number or address on Page 2. What we do instead is take advantage of hypertext, a website is made up of web pages and each and every web page is a document - a single file.
then tell your customers to find your shop/business phone number or address on Page 2. What we do instead is take advantage of hypertext, a website is made up of web pages and each and every web page is a document - a single file, just like the index is.

In our case (with WAMPP) the website index in the
```
@@ -24,3 +24,27 @@ http://localhost/index.html
```

is an actual index.html file.

If click a link (or manually navigate) to

```
http://localhost/pages/advertisement/create.htm
```

what you are doing is you are instructing the browser to obtain resources at this "http://localhost/pages/advertisement/create.htm" identifier - the (U)niform (R)resource (I)dentifier, also known as the (U)niform (R)esource (L)ocation/(L)ocator.

The browser then relays the URI to the server, who in turn takes "http://localhost/pages/advertisement/create.htm" and separates it into

http:// (the scheme (the (h)yper(t)ext (t)ransfer (p)rotocol))
localhost (the host/domain, google.com for google, wikipedia.org for wikipedia, etc)
pages/ (file (or in our case a directory) by the name "pages" sitting at server root)
advertisement (file (or in our case a directory) by the name advertisement sitting within the "pages" directory)
create.htm (file (or in our case a file) by the name create.htm sitting within the advertisement directory)

Lastest part, create.htm is an actual file that the server reads and relays contents of to the browser. If we had a description.txt file right next to create.htm, navigating the URI of

```
http://localhost/pages/advertisement/description.txt
```

would read the contents (state, remember) of the description.txt file and send it back to the browser, letting you read it.

Loading…
Cancel
Save