summaryrefslogtreecommitdiff
path: root/blog/src/a
diff options
context:
space:
mode:
Diffstat (limited to 'blog/src/a')
-rw-r--r--blog/src/a/mail_server_with_postfix.md4
-rw-r--r--blog/src/a/sql_video_notes.md10
-rw-r--r--blog/src/a/website_with_nginx.md4
3 files changed, 9 insertions, 9 deletions
diff --git a/blog/src/a/mail_server_with_postfix.md b/blog/src/a/mail_server_with_postfix.md
index d72ecac..b65cf54 100644
--- a/blog/src/a/mail_server_with_postfix.md
+++ b/blog/src/a/mail_server_with_postfix.md
@@ -316,7 +316,7 @@ systemctl start dovecot.service
systemctl enable dovecot.service
```
-# OpenDKIM
+## OpenDKIM
[OpenDKIM](https://wiki.archlinux.org/index.php/OpenDKIM) is needed so services like G\*\*gle (we don't mention that name here \[\[\[this is a meme\]\]\]) don't throw the mail to the trash. DKIM stands for "DomainKeys Identified Mail".
@@ -518,7 +518,7 @@ Next, to actually login into a mail app/program/whateveryouwanttocallit, you wil
All that's left to do is test your mail server for spoofing, and to see if everything is setup correctly. Go to [DKIM Test](https://www.appmaildev.com/en/dkim) and follow the instructions (basically click next, and send an email with whatever content to the email that they provide). After you send the email, you should see something like:
-![DKIM Test successful](https://static.luevano.xyz/images/b/notes/mail/dkim_test_successful.png)
+![DKIM Test successful](images/b/notes/mail/dkim_test_successful.png)
(Yes, I blurred a lot in the picture just to be sure, either way what's important is the list on the bottom part of the image)
diff --git a/blog/src/a/sql_video_notes.md b/blog/src/a/sql_video_notes.md
index b6662db..91c5976 100644
--- a/blog/src/a/sql_video_notes.md
+++ b/blog/src/a/sql_video_notes.md
@@ -140,10 +140,10 @@ There are different types of SQL JOINs:
* `RIGHT (OUTER) JOIN`: returns all records from the right table, and the matched records from the left table.
* `FULL (OUTER) JOIN`: returns all records when there is a match in either left or right table.
-![INNER JOIN](https://static.luevano.xyz/images/b/notes/sql/img_innerjoin.gif)
-![LEFT JOIN](https://static.luevano.xyz/images/b/notes/sql/img_leftjoin.gif)
-![RIGHT JOIN](https://static.luevano.xyz/images/b/notes/sql/img_rightjoin.gif)
-![FULL OUTER JOIN](https://static.luevano.xyz/images/b/notes/sql/img_fulljoin.gif)
+![INNER JOIN](images/b/notes/sql/img_innerjoin.gif)
+![LEFT JOIN](images/b/notes/sql/img_leftjoin.gif)
+![RIGHT JOIN](images/b/notes/sql/img_rightjoin.gif)
+![FULL OUTER JOIN](images/b/notes/sql/img_fulljoin.gif)
#### Nested queries
@@ -174,4 +174,4 @@ The diagram consists of:
* **Weak entity's primary key**: oval with its text underlined, but the line is dotted.
* **Identifying relationship**: a diamond inside a diamond with its name inside; a relationship that serves to uniquely identify the weak entity.
-![ERD example taken from wikipedia](https://static.luevano.xyz/images/b/notes/sql/erd_example.png)
+![ERD example taken from wikipedia](images/b/notes/sql/erd_example.png)
diff --git a/blog/src/a/website_with_nginx.md b/blog/src/a/website_with_nginx.md
index 1682da2..95c90c1 100644
--- a/blog/src/a/website_with_nginx.md
+++ b/blog/src/a/website_with_nginx.md
@@ -34,7 +34,7 @@ systemctl start nginx.service
And that's it, at this point you can already look at the default initial page of nginx if you enter the ip of your server in a web browser. You should see something like this:
-![Nginx welcome page](https://static.luevano.xyz/images/b/notes/nginx/nginx_welcome_page.png)
+![Nginx welcome page](images/b/notes/nginx/nginx_welcome_page.png)
As stated in the welcome page, configuration is needed, head to the directory of nginx:
@@ -117,7 +117,7 @@ systemctl restart nginx
If everything goes correctly, you can now go to your website by typing "domain.name" on a web browser. But you will see a "404 Not Found" page like the following (maybe with different nginx version):
-![Nginx 404 page](https://static.luevano.xyz/images/b/notes/nginx/nginx_404_page.png)
+![Nginx 404 page](images/b/notes/nginx/nginx_404_page.png)
That's no problem, because it means that the web server it's actually working. Just add an `index.html` file with something simple to see it in action. If you keep seeing the 404 page make sure your `root` line is correct and that the directory/index file exists.