24PinTech Wiki - User contributions [en]

Bradley Chamberlain

2023-06-16T20:30:37Z

Lchristopherson: :)

== About ==
[[File:Bradley1.jpg|thumb]]
The god of creation and ending. . Bradley Chamberlain is the man who has founded 24PinTechnologies with his own bare two hands, and single-handedly became a legend among former gods, he has dethroned every god known to man and has become something inevitable. Bradley Chamberlain.
== Origin ==
It all began on November 1st, 1967. The man who will destroy anything and everything was born. Not much is known about Bradley's childhood life, but many speculate that Bradley Chamberlain lead a normal childhood life. In Bradley's young adult life, he engaged in the playing of a sport. That sports name would happen to be foosball... and it would change his life forever.

Edit: Bradford™️ has been found prone to leaving important classified information in his pants from yesterday. Stay aware!
== Foosball era (appx. 1986-1994) ==
Bradley Chamberlain had taken a keen interest to Foosball. This is the first thing in Bradley's life that makes since to him, and allows him to truly be ''free''. One occasion during these Foosball days, appx. 1989, Bradley had come in contact with a very import man in the tech industry, a ''god'' named Scott Manchester. This Deity, ''Scott Manchester'' had challenged everyone in the establishment to a duel in Foosball. Scott had claimed that there was no one in the world who could dethrone Scott as the Foosball champion, and the ''Digital Deity™''. Scott had caused a riot. "''hmm, what's this?''" Bradley curiously denounced. Bradley took a look around to see everyone going crazy over something, but what? People stared cheering, "'''Di-gi-tal De-i-ty, Di-gi-tal De-i-ty'''". This chant piqued Bradley's interest. Bradley located the source of the chanting, the stage. Bradley walked up to the stage and challenged Scott Manchester to a Foosball duel to the death.
=== The rise of a legend ===
Scott noticed Bradley among all of the other smelly nerds, and silenced the crowd. "'''''So you wish to duel me? To the death?'''''" Scott responded. Bradley didn't reply. This made Scott furious. Bradley simply watched. As the crowd grew louder, Scott scoffed. Bradley finally made his way up to the ring with Scott Manchester waiting for him. Scott smirked, and began to speak, "WELC-"! Immediately Bradley teleported behind Scott Manchester with a blank face staring down. "Are you sure you'd like to finish that?" Bradley exclaimed.
=== The tale to be told for ages ===
Scott gulped. Without talking he started setting up the foosball table. Bradley walked to his side very slowly. When Bradley arrived to the table, the referee stated the stakes of this battle, "'''''You are betting your pride, titles, and lives. Do you both consent.'''''" Both of them nodded. Each of them gripped their handles, Scott grabbing a defensive and offensive handle, while Bradley grabbed two offensive handles. Scott smirked and thought, "''He's so stupid! Two offensive???''" Bradley said out loud, "'''Don't think so soon Scotty.'''" The game went on for approximately 4 minutes and 23 seconds. Bradley swept the floor with Scott. The crowd was in awe. As the last point was given to Bradley, Scott began begging for his life, and to be shown mercy. Bradley complied. Bradley would come to be known as one of the most merciful beings in existence. This battle is what allowed Bradley to gain his title as the '''Digital Deity'''.
== Beginning of the End (appx. 1997-2009) ==
This is a very unknown part of Bradley's life, as he does not remember this era very well and it hasn't been documented well. What is known about this time period, is that Bradley had began his reign as the '''Digital Deity'''. Bradley would pillage any town if someone gave him the slightest attitude. The theory goes something along the lines of, "Bradley found a person who made him happy. This so called person didn't like the pointless violence that Bradley partook in, and therefore told him that if he didn't end the pointless violence and destruction, they would leave forever. This person eventually showed Bradley the meaning of compassion." Bradley had finally learned '''''some''''' compassion. Instead of directing his anger at random civilians and towns, Bradley took it out on people who deserved it. Bradley gained his title as "'''The Merciless Bounty Hunter'''" through the only time in this era that has been documented.
=== The Merciless Bounty Hunter ===
With Bradley's newfound compassion, he decided to use it for good. Bradley took to the streets, looking for people who have a price to pay. At first Bradley had begun to destroy petty criminals, with an axe that he had in his garage, but learned of the big time criminals who had a bounty on their heads. Bradley had set out to find his first victim, whomst was very difficult to locate. One Bradley did locate this first criminal however, he was slowly put to rest. ''The AxeTM'' wasn't enough. Although Bradley put up a fight, he was pounced on by this criminal. This brought Bradley back to the drawing board. Bradley had never felt so embarrassed in his life, so therefore he had decided to curate a brand new weapon. The likes of which no one has ever seen before. Bradley spent weeks in the garage designing and perfecting this unholy weapon. Bradley had taken multiple ethernet cords, and combined them all together to create a whip of sorts. Bradley decided to name this the ''EtherWhipTM''. Bradley did not need practice with this new weapon, as it was completely natural to him. This was a part of Bradley already. Bradley immediately set forth to find the same criminal, and when he did... let's just say that Bradley obtained a nice amount of money. This newfound way to bring out his violence and aggression mixed with the fact that he gets paid to do this pushed Bradley to become a name to fear. Everyone who obtained a bounty feared for their very lives, as Bradley would always find them, and finish them swiftly.
== The founding of 24PinTechnologies (appx. 2010-present) ==
After several years of gaining money through bounties, Bradley become quite tired, though Bradley's thirst for excitement was not quite quenched yet. Bradley had always thought that his dream would be to start a business where he can truly be himself, and with his compassion he had acquired, he wanted to help others be themselves as well. Bradley used his title as the '''Digital Deity''' to start a nonprofit IT business through the local school in his town. The business became a booming success, with people finding their places through his program. Bradley had also benefited from this as he could still "punish" the bad kids, RIP, and gain passive income, all while being who he truly wants to be. Bradley had finally found true happiness.

Parsoid and VisualEditor

2022-08-08T19:30:15Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:Parsoid word logo.svg.png|thumb]]
VisualEditor is the plugin that allows MediaWiki to edit pages through the web format. It makes creating pages a seamless process with copy and paste functionality from Google Docs or anywhere else with formatting. VisualEditor runs through a service called Parsoid though. Parsoid takes the text inputted on the VisualEditor, and it parses it into wikitext.

== Setup ==
To setup Parsoid with VisualEditor you have to configure two files.

=== LocalSettings.php ===
LocalSettings.php is located in the root directory of your website. In this file you must find where the extensions are loaded. If VisualEditor is not already loaded, you must load it manually. Add these following lines to the plugins. Our LocalSettings.php is located at <code>/var/www/wiki.24pin.tech/LocalSettings.php</code>

<code>wfLoadExtension( 'VisualEditor' );</code>

<code>wfLoadExtension( 'Parsoid', __DIR__, '/vendor/wikimedia/parsoid/extension.json' );</code>

=== Server Block Config ===
You will have to add the restbase server to your server block for this to work. Our server block is located at <code>/etc/nginx/sites-available/wiki.24pin.tech</code>

<code>location /rest.php/ {</code>

<code>try_files $uri $uri/ /rest.php?$query_string;</code>

<code>}</code>

These lines are just another location block that you will add at the end of your server block.

=== If that doesn't work ===
There could be a multitude of reasons that Parsoid does not work, so the best way to figure it out is researching. The only other fix I could recommend, is adding this to the end of your LocalSettings.php file.

<code>$wgDefaultUserOptions['visualeditor-enable'] = 1;</code>

<code>$wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";</code>

<code>$wgHiddenPrefs[] = 'visualeditor-enable';</code>

This is it... It's not as complicated as we thought.

MediaWiki

2022-08-08T19:27:49Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:MediaWiki-2020-logo.svg.png|thumb|116x116px]]
Mediawiki is the software that our wiki runs on. Mediawiki is ran on our LEMP stack and allows for "wikipedia" type pages to be made securely. Installing a wiki is a very simple process, so pay attention...

Before you begin, make sure that you have a server block set up for the wiki.

== Links ==
https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki

https://www.mediawiki.org/wiki/Manual:Config_script

== Installation ==
To begin the installation for MediaWiki, you need to have a working webserver, in which we are running a LEMP stack.

* Visit [https://mediawiki.org/wiki/Download MediaWiki's Download website] and download the new .tar.gz version
* [[PuTTY]] the file into the webserver.
* Navigate to the root directory of MediaWiki ... ex. <code>/var/www/wiki.24pin.tech</code>
* Move zip to the root directory of MediaWiki using <code>sudo mv ./mediawiki-install-zip /var/www/wiki-install-directory</code>
* Run <code>sudo tar -xzvf ./mediawiki-install-zip</code> to unzip it.
* Best practice is to name the install folder "w". Do this by running <code>sudo mv ./mediawiki-install ./new-name</code>
* If you decide to move all files to the root, run <code>sudo mv ./mediawiki-install/* ./</code>

=== Create a database for the wiki ===
The wiki needs specific parameters for the database to correctly function. Log into mysql by running <code>sudo mysql -u root -p</code>. Once you log in you will run the following commands with your settings.

<code>CREATE DATABASE db_name;</code>

<code>CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'db_password';</code>

<code>GRANT ALL PRIVILEGES ON db_name.* TO 'wikiuser'@'localhost' WITH GRANT OPTION;</code>

This will successfully create the database and database user for your wiki.

=== Install the wiki ===

To run the installation script, you must visit your wiki domain/mw-config. For example: <code>https://wiki.domain.com/mw-config</code> or <code>https://domain.com/wiki/mw-config</code>. You will run through the installation with the settings that you have set up previously, such as the database user and database name. Once the setup is complete, you will receive a download for a file called LocalSettings.php. You must [[PuTTY]] this into the server, as you did with the install zip. Once completed, this will go directly to the wiki's root directory.

The wiki should now be setup. For Parsoid and VisualEditor setup, see: [[Parsoid and VisualEditor]].

== Special Usages ==
The wiki is now set up and may be used. There are two key things I'd like to iterate here. You can find most special settings, like creating accounts in the [https://wiki.24pin.tech/view/Special:SpecialPages Special Pages] tab.

The second thing is that the sidebar is editable. You may edit it by clicking this link.
https://wiki.24pin.tech/edit/MediaWiki:Sidebar

-Luke Christopherson

Parsoid and VisualEditor

2022-08-08T18:46:59Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:Parsoid word logo.svg.png|thumb]]
VisualEditor is the plugin that allows MediaWiki to edit pages through the web format. It makes creating pages a seamless process with copy and paste functionality from Google Docs or anywhere else with formatting. VisualEditor runs through a service called Parsoid though. Parsoid takes the text inputted on the VisualEditor, and it parses it into wikitext.

== Setup ==
To setup Parsoid with VisualEditor you have to configure two files.

=== LocalSettings.php ===
LocalSettings.php is located in the root directory of your website. In this file you must find where the extensions are loaded. If VisualEditor is not already loaded, you must load it manually. Add these following lines to the plugins.

<code>wfLoadExtension( 'VisualEditor' );</code>

<code>wfLoadExtension( 'Parsoid', __DIR__, '/vendor/wikimedia/parsoid/extension.json' );</code>

=== Server Block Config ===
You will have to add the rest base server to your server block for this to work.

<code>location /rest.php/ {</code>

<code>try_files $uri $uri/ /rest.php?$query_string;</code>

<code>}</code>

=== If that doesn't work ===
There could be a multitude of reasons that Parsoid does not work, so the best way to figure it out is researching. The only other fix I could recommend, is adding this to the end of your LocalSettings.php file.

<code>$wgDefaultUserOptions['visualeditor-enable'] = 1;</code>

<code>$wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";</code>

<code>$wgHiddenPrefs[] = 'visualeditor-enable';</code>

This is it... It's not as complicated as we thought.

File:Parsoid word logo.svg.png

2022-08-08T18:07:44Z

Lchristopherson:

jfbdksljhag

PuTTY

2022-08-08T18:02:16Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:Putty img.jpg|thumb|93x93px]]
PuTTY is a very useful program that allows you to communicate with outside devices through SSH. Putty is mainly used for remoting into machines outside of your network. You can download it [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html here].

== Links ==
https://cs.hofstra.edu/docs/pages/guides/putty_setup.html

== Usage ==

=== Remote into other System ===
Open the PuTTY program. Once it is open you will enter the IP address for the system you are trying to access in the Host Name box. Select the connection type as SSH, and use port 22. Press open. You will have to authenticate, and then you will be in.

=== Send file to another System ===
To send a file to another system you will open a new CMD window and navigate to the PuTTY install directory. ''My command...'' <code>cd C:\Program Files\PuTTY</code>. Once you have successfully navigated to the installation directory you will enter the command to send a file. <code>pscp.exe <LocalFilePath> <user>@<RemoteHost>:<RemoteDirectory></code>. You will once again have to authenticate.

MediaWiki

2022-08-08T17:49:58Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:MediaWiki-2020-logo.svg.png|thumb|116x116px]]
Mediawiki is the software that our wiki runs on. Mediawiki is ran on our LEMP stack and allows for "wikipedia" type pages to be made securely. Installing a wiki is a very simple process, so pay attention...

Before you begin, make sure that you have a server block set up for the wiki.

== Links ==
https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki

https://www.mediawiki.org/wiki/Manual:Config_script

== Installation ==
To begin the installation for MediaWiki, you need to have a working webserver, in which we are running a LEMP stack. You will visit [https://mediawiki.org/wiki/Download MediaWiki's Download website] to download the newest version of MediaWiki in .tar.gz format. Once you have the .tar.gz file, you must PuTTY the file into the webserver. Now you have to unzip the file into the working wiki directory. Move the zip into the root of the server block by running, <code>sudo mv ./mediawiki-install-zip /var/www/wiki-install-directory</code>. Once you have moved the zip into the folder, you need to unzip it. Do so by running <code>sudo tar -xzvf ./mediawiki-install-zip</code>. The best practice is to use a folder named "w", for the wiki files, though we used the root directory. To change the directory's name, you will run <code>sudo mv ./mediawiki-install ./new-name</code>. If you are moving all of the contents into the root website directory you will run, <code>sudo mv ./mediawiki-install/* ./</code>.

=== Create a database for the wiki ===
The wiki needs specific parameters for the database to correctly function. Log into mysql by running <code>sudo mysql -u root -p</code>. Once you log in you will run the following commands with your settings.

<code>CREATE DATABASE db_name;</code>

<code>CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'db_password';</code>

<code>GRANT ALL PRIVILEGES ON db_name.* TO 'wikiuser'@'localhost' WITH GRANT OPTION;</code>

This will successfully create the database and database user for your wiki.

=== Install the wiki ===

To run the installation script, you must visit your wiki domain/mw-config. For example: <code>https://wiki.domain.com/mw-config</code> or <code>https://domain.com/wiki/mw-config</code>. You will run through the installation with the settings that you have set up previously, such as the database user and database name. Once the setup is complete, you will receive a download for a file called LocalSettings.php. You must [[PuTTY]] this into the server, as you did with the install zip. Once completed, this will go directly to the wiki's root directory.

The wiki should now be setup. For Parsoid and VisualEditor setup, see: [[Parsoid and VisualEditor]].

== Special Usages ==
The wiki is now set up and may be used. There are two key things I'd like to iterate here. You can find most special settings, like creating accounts in the [https://wiki.24pin.tech/view/Special:SpecialPages Special Pages] tab.

The second thing is that the sidebar is editable. You may edit it by clicking this link.
https://wiki.24pin.tech/edit/MediaWiki:Sidebar

-Luke Christopherson

MediaWiki

2022-08-08T17:38:35Z

Lchristopherson:

File:MediaWiki-2020-logo.svg.png

2022-08-08T17:01:11Z

Lchristopherson:

fds

Vim

2022-08-08T16:54:10Z

Lchristopherson: Lchristopherson moved page Vim/Nano to Vim without leaving a redirect: nano is literally text editor

[[Category:Webserver]]
== About ==
[[File:Vim-splash.png|thumb|The splash screen for Vim]]
According to the official Vim website, "Vim is a highly configurable text editor for efficiently creating and changing any kind of text. It is included as "vi" with most UNIX systems and with Apple OS X."

== Basic Usage ==
The syntax for Vim is pretty straightforward. You can edit files by running <code>vim filename</code> to open the file with Vim, but if the file doesn't exist Vim will create one for you. Once you're in the editor, press <code>i</code> to start inserting text. After you're finished editing the file, press the escape key and then enter <code>:wq</code> to save the file. If you need to exit out of the file, press escape and enter <code>:q</code>, and if you need to exit without saving press escape and type <code>:q!</code>.

Other than that, there isn't much more that you need to know. For more advanced tips, check out the [https://vim.fandom.com/wiki/Vim_Tips_Wiki Vim Tips Wiki].

'''NOTICE:''' Please make sure that you have permission to write to the directory that you're editing the file in. If you don't check and make sure, you won't be able to save the file and will lose whatever changes you made.

== Common Problems ==

=== Can't open file for writing ===
[[File:Vim-permissions.png|left|frameless]]

This problem occurs when you don't have permission to write to the file. To fix this, press the escape key and type <code>:q!</code> to quit without saving. Then, run the same command again but prefixed with <code>sudo</code>.

PuTTY

2022-08-08T05:56:20Z

Lchristopherson:

File:Putty img.jpg

2022-08-08T05:51:31Z

Lchristopherson:

for putty page

Bradley Chamberlain

2022-08-08T05:48:21Z

Lchristopherson: /* Beginning of the End (appx. 1997-2009) */

== About ==
[[File:Bradley1.jpg|thumb]]
The god of creation and ending. The man who will kill you '''and''' your entire family with the '''''EtherWhip™''''' or '''''The Axe™''''' mercilessly if you happen to make him too upset. Bradley Chamberlain is the man who has founded 24PinTechnologies with his own bare two hands, and single-handedly became a legend among former gods, he has dethroned every god known to man and has become something inevitable. Bradley Chamberlain.

== Origin ==
It all began on November 1st, 1967. The man who will destroy anything and everything was born. Not much is known about Bradley's childhood life, but many speculate that Bradley Chamberlain lead a normal childhood life. In Bradley's young adult life, he engaged in the playing of a sport. That sports name would happen to be foosball... and it would change his life forever.

== Foosball era (appx. 1986-1994) ==
Bradley Chamberlain had taken a keen interest to Foosball. This is the first thing in Bradley's life that makes since to him, and allows him to truly be ''free''. One occasion during these Foosball days, appx. 1989, Bradley had come in contact with a very import man in the tech industry, a ''god'' named Scott Manchester. This Deity, ''Scott Manchester'' had challenged everyone in the establishment to a duel in Foosball. Scott had claimed that there was no one in the world who could dethrone Scott as the Foosball champion, and the ''Digital Deity™''. Scott had caused a riot. "''hmm, what's this?''" Bradley curiously denounced. Bradley took a look around to see everyone going crazy over something, but what? People stared cheering, "'''Di-gi-tal De-i-ty, Di-gi-tal De-i-ty'''". This chant piqued Bradley's interest. Bradley located the source of the chanting, the stage. Bradley walked up to the stage and challenged Scott Manchester to a Foosball duel to the death.

=== The rise of a legend ===
Scott noticed Bradley among all of the other smelly nerds, and silenced the crowd. "'''''So you wish to duel me? To the death?'''''" Scott responded. Bradley didn't reply. This made Scott furious. Bradley simply watched. As the crowd grew louder, Scott scoffed. Bradley finally made his way up to the ring with Scott Manchester waiting for him. Scott smirked, and began to speak, "WELC-"! Immediately Bradley teleported behind Scott Manchester with a blank face staring down. "Are you sure you'd like to finish that?" Bradley exclaimed.

=== The tale to be told for ages ===
Scott gulped. Without talking he started setting up the foosball table. Bradley walked to his side very slowly. When Bradley arrived to the table, the referee stated the stakes of this battle, "'''''You are betting your pride, titles, and lives. Do you both consent.'''''" Both of them nodded. Each of them gripped their handles, Scott grabbing a defensive and offensive handle, while Bradley grabbed two offensive handles. Scott smirked and thought, "''He's so stupid! Two offensive???''" Bradley said out loud, "'''Don't think so soon Scotty.'''" The game went on for approximately 4 minutes and 23 seconds. Bradley swept the floor with Scott. The crowd was in awe. As the last point was given to Bradley, Scott began begging for his life, and to be shown mercy. Bradley complied. Bradley would come to be known as one of the most merciful beings in existence. This battle is what allowed Bradley to gain his title as the '''Digital Deity'''.

== Beginning of the End (appx. 1997-2009) ==
This is a very unknown part of Bradley's life, as he does not remember this era very well and it hasn't been documented well. What is known about this time period, is that Bradley had began his reign as the '''Digital Deity'''. Bradley would pillage any town if someone gave him the slightest attitude. The theory goes something along the lines of, "Bradley found a person who made him happy. This so called person didn't like the pointless violence that Bradley partook in, and therefore told him that if he didn't end the pointless violence and destruction, they would leave forever. This person eventually showed Bradley the meaning of compassion." Bradley had finally learned '''''some''''' compassion. Instead of directing his anger at random civilians and towns, Bradley took it out on people who deserved it. Bradley gained his title as "'''The Merciless Bounty Hunter'''" through the only time in this era that has been documented.

=== The Merciless Bounty Hunter ===
With Bradley's newfound compassion, he decided to use it for good. Bradley took to the streets, looking for people who have a price to pay. At first Bradley had begun to destroy petty criminals, with an axe that he had in his garage, but learned of the big time criminals who had a bounty on their heads. Bradley had set out to find his first victim, whomst was very difficult to locate. One Bradley did locate this first criminal however, he was slowly put to rest. ''The AxeTM'' wasn't enough. Although Bradley put up a fight, he was pounced on by this criminal. This brought Bradley back to the drawing board. Bradley had never felt so embarrassed in his life, so therefore he had decided to curate a brand new weapon. The likes of which no one has ever seen before. Bradley spent weeks in the garage designing and perfecting this unholy weapon. Bradley had taken multiple ethernet cords, and combined them all together to create a whip of sorts. Bradley decided to name this the ''EtherWhipTM''. Bradley did not need practice with this new weapon, as it was completely natural to him. This was a part of Bradley already. Bradley immediately set forth to find the same criminal, and when he did... let's just say that Bradley obtained a nice amount of money. This newfound way to bring out his violence and aggression mixed with the fact that he gets paid to do this pushed Bradley to become a name to fear. Everyone who obtained a bounty feared for their very lives, as Bradley would always find them, and finish them swiftly.

== The founding of 24PinTechnologies (appx. 2010-present) ==
After several years of gaining money through bounties, Bradley become quite tired, though Bradley's thirst for excitement was not quite quenched yet. Bradley had always thought that his dream would be to start a business where he can truly be himself, and with his compassion he had acquired, he wanted to help others be themselves as well. Bradley used his title as the '''Digital Deity''' to start a nonprofit IT business through the local school in his town. The business became a booming success, with people finding their places through his program. Bradley had also benefited from this as he could still "punish" the bad kids, RIP, and gain passive income, all while being who he truly wants to be. Bradley had finally found true happiness.

User:Lchristopherson

2022-08-08T05:18:05Z

Lchristopherson: /* About */

== About ==
Hey, my name is Luke Christopherson, and at the time of writing this article I am 17 years old, and about to graduate high school as a senior. I have had a tough time throughout my high school career, and never really found a place I wanted to be. I had switched schools many, many, many times due to a toxic home environment, and ended up at MHS. I transferred to IT Essentials from Video Game Development, and the thing I remember the most, is [[Bradley Chamberlain]] asking me if I'll be okay in this class because its "hardcore" and "nothing like Video Game Development". I did fine. My sophomore year of high school, I was selected to work on the SIEM project, which has now been taken over by Alex Grace. The only reason I did not continue to work on the SIEM, is because the project was assigned around the time when Covid hit. We went online, and I never touched it again. In my Junior year of high school, as well as my first year in 24PinTech, I was not very involved. I was still feeling lazy from Covid and did basically nothing. Once I started my Senior year, I really felt like I wanted to prove that I'm good enough to be remembered in the class. In the first semester I didn't do much. Once I started on the webserver, it was all over for the haters. I mastered Linux, and Nginx, and our Webserver very, very fast. I found this stuff to be relatable to my background in programming, and really enjoyed every minute of working on it... besides adding Wordpress salts. That's about it though, thanks for reading!

== Certifications ==

* '''CompTIA A+'''
* Testout Linux Pro
* Testout Security Pro
* Testout PC Pro

== Awards ==

* First Place Gold Medalist, AZSkillsUSA - Web Design
* First Place Gold Medalist, AZSkillsUSA - Career Pathways Showcase (IT)

== My Mark ==
To be honest, there's not a lot I can talk about when it comes to what I left for 24PinTech. Most of my time was spent in the backend, which not many people would understand. I suppose what you can thank me for is pretty links, an organized web server, and backups??? I don't know man, a lot of it was cleaning up other people's work, and expanding on it. W. Oh and also I am the first person to perform a successful heist on the ''EtherWhipTM''.

== Where I am ==
As of now I am working as an IT Field Technician for a small company called ALOA-ETS. It's very fun because the IT portion of the company is not very mature yet, and with me being the only IT person, I get to shape it how I like. I find that this job gives me the same freedom I got from 24PinTech, and I'll tell you, the skills are transferring very good. I have created a web server for them through Azure, (weird), and I get to research a lot of new fun stuff. My boss doesn't know a lot of backend stuff in IT, which gives me an advantage to learn a lot more about backend IT services, which just so happens to be my favorite part. Though I am learning that everything I'm learning was a part of 24PinTech, which is super cool. Thank you [[Bradley Chamberlain|Bradford]].

I am also going to college at ASU Online. Originally I was planning on going on-campus, but things changed at home, and that wasn't an option anymore. I am majoring in Software Engineering, and I'm very excited to take Calculus for Engineers I and Calculus for Engineers II in one semester! not. I feel that college will take me places I never thought possible, which I am extremely excited to do. Wish me luck.

== Contact ==
{| class="wikitable"
|+Contact Information
!Phone
!Email
!Other
|-
|(480) 295-0194
|lukechristopherson0@gmail.com
|Homing Pigeon
|}

== Conclusion ==
In conclusion, I really enjoyed my time at 24PinTech, and love all of the memories I made. I didn't do as much as I wanted to, or could do, but I am still very happy to have been a part of this program nonetheless.

-Luke

HTTPS with Certbot (LetsEncrypt)

2022-05-30T19:43:37Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:Certbot logo.png|left|thumb|231x231px]]
When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.

By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot provides a very simple way to create and apply these certificates to ensure a secure connection.

== Pre-requisites ==

* Linux Ubuntu
* Working Nginx Webserver
* Running server block/website on Port 80 (HTTP)
* Sudo privileges

== Installation ==
To begin, verify that the website that you'd like to open HTTPS is valid and up on the World Wide Web. This just means having a working [[Nginx]] domain set up. You can view how to add a new Nginx Domain/Subdomain [[Adding a New Domain or Subdomain|here]].

To install Certbot, you will run the commands <code>sudo apt-get install certbot</code> and <code>sudo apt-get install python-certbot-nginx</code>, to install Certbot for our specific server setup. Once this is done, you will be able to create an HTTPS certificate for any website running.

== Creating an Nginx HTTPS Certificate ==
To create a new HTTPS certificate, you may run <code>sudo certbot</code>. This command will bring up a list of all of the available domains on the webserver, and number them, you will choose a number and it will install the certificate. It is as simple as that!

Another way to install a certificate is to run <code>sudo certbot --nginx -d domain.com</code> where <code>domain.com</code> is the name of the domain that you want to add.

=== Verification ===
To verify if the HTTPS domain is valid, run <code>sudo nginx -t</code> to check for any server config file errors. If that test returns successful, navigate to the website in your web browser of choice (Google Chrome), and check for the little lock next to the name of the website, if that has appeared, you have successfully installed Certbot onto that domain.

== Removing an Nginx HTTPS Certificate ==
To remove a certificate from a domain, you will run the command <code>sudo certbot delete</code>. Like the command to create a certificate, this will bring up a list of all of the certificates available numbered. You will enter the number of the certificate, and it will be removed, it's that simple.

=== Verification ===
To verify you didn't break everything like I (Luke), have done multiple times, you will run <code>sudo nginx -t</code>. If this test returns successful, you may navigate to your web browser of choice (Google Chrome), and check next to the URL for a sign that says "Not Secure". This will complete the deletion of a certificate.

== Notes ==
'''Note:''' '''It could possibly take up to 24-72 hours for it to be enabled, although at the time of writing the changes propagated almost immediately.'''

'''Extra Note:''' '''All Certbot certificates should auto-renew every 90 days.'''

Nginx

2022-05-30T19:24:51Z

Lchristopherson:

[[Category:Webserver]]
==About==
Nginx (pronounced engine-x) is web server which can also be used proxy, load balancer, mail proxy and HTTP cache. It's also a modern alternative to something like Apache, IIS, or Caddy.

==Prerequisites==
An nginx installation should be pretty accessible regardless of your OS. This guide is specifically written for Ubuntu Server 18.04 LTS, but should work on any other type of Unix operating system. The setup that we're using is commonly referred to as a LEMP stack (Linux, nginx, MySQL, PHP.)

*nginx/1.14.0 (Ubuntu)
*PHP 7.2.10-0ubuntu0.18.04.1 (cli)
*MySQL v14.14 Distribution 5.7.24

If you've just installed a new operating system, you'll want to update your local package index by running <code>sudo apt-get update</code>, and then add the Universe repository by running <code>sudo apt-add-repository universe</code>.

==Installing nginx==
To start, you're going to want to install nginx using the aptitude package manager. You can do this by running <code>sudo apt-get install nginx</code>. Once you run that, you'll want to go through the configuration prompt that appears.

.

After nginx and its subsequent dependencies have finished installing, you'll want to let it through the firewall by running <code>sudo ufw allow 'Nginx HTTP'</code>. Check what your current IP is by running <code>ifconfig</code>, and then look for whatever interface looks correct. In this instance, the proper interface is <code>eth0</code>.

.

[[File:Ifconfig-example.png|left|frame|an example of the results from ifconfig]]
After running the command, the first indented line should say '''''inet''''' and then an IP address afterwards. Verify functionality of nginx by going to your web browser and typing <code><nowiki>http://{ip}/</nowiki></code> where <code>{ip}</code> is what follows after '''''inet'''''.

If the default nginx page displays, continue to the next section.

.

.

.

.

.

==Installing MySQL==
The process of installing MySQL is fairly similar to installing nginx, although MySQL does require a little bit of configuration before it will function properly. Start off by running <code>sudo apt-get install mysql-server</code>, and then once it finishes run the setup script by typing <code>sudo mysql_secure_installation</code>.

.

The first thing that the installations script will ask you is if you'd like to enable the <code>VALIDATE PASSWORD PLUGIN</code>, but don't. If you don't care about why, then skip to the next paragraph, but if you do, keep reading. Essentially, the plugin throws errors if passwords don't meet specific criteria. This causes issues if you either a.) use weak passwords, or b.) install a package that automatically compiles and creates a default account with basic credentials. '''It is always good practice to use strong passwords for everything, and database credentials are no exception.'''

.

Say yes to the rest of the questions and use good judgement if it asks something that requires anything other than a Y/N input.

==Installing PHP==
Again, installing PHP is very similar to two sections preceding this one. Start off by installing the <code>php-fpm</code> and <code>php-mysql</code> packages by running <code>sudo apt-get install php-fpm php-mysql</code>. After it installs, you'll want to edit <code>php.ini</code> by running <code>sudo vim /etc/php/7.4/fpm/php.ini</code>.

.

'''''Note:''' If the file isn't found, check'' the directory path by using the <code>cd</code> command and seeing where something doesn't exist.

.

If you're using Vim, type a <code>?</code> and search for <code>cgi.fix_pathinfo</code>. You should be taken to a line that's commented out and says <code>;cgi.fix_pathinfo=0</code> or something similar. Press the <code>i</code> key to start editing and remove the <code>;</code> to uncomment it. If the variable is set to 1, change it to 0. Press the <code>escape</code> key and type <code>:wq</code> to save and quit your changes. If you didn't run Vim as a superuser (if you didn't run the command with <code>sudo</code>), it will throw and error and the file won't save.

.

Once the file saves, run <code>sudo systemctl restart php7.4-fpm</code> to restart PHP.

==Configuring nginx==
The configuration for nginx is a little different compared to anything you might be used to. To start, there are two directories: <code>sites-available</code> and <code>sites-enabled</code>. The former directory actually contains the configuration files, while the latter contains symbolic links to the configuration files and enables them.

.

To start, lets say that we wanted to configure our nginx server to work with the domain <code>example.ms</code>. First, we'd want to verify that the directory <code>/var/www/example.ms</code> exists. Move to the <code>sites-available</code> directory by entering the command <code>cd /etc/nginx/sites-available</code>. Next, you'll want to create a new configuration file with the name of the domain. You can either by running <code>sudo touch example.ms && sudo vim example.ms</code> or simply by running <code>sudo vim example.ms</code> since Vim creates the file if it doesn't exist. Again, press <code>i</code> to edit the file. Once you're in edit mode, you'll want the contents to look something like this:<pre>
server {
listen 80;
listen [::]:80;

# this is a comment! you don't have to include this, but if you're not
# going to be using a domain, then you can replace it with an IP
server_name example.ms;

root /var/www/example.ms;
index index.php index.html index.htm;

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.2-fpm.sock;
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>'''''Tip:''' You can periodically save your configuration file by pressing <code>escape</code>, typing <code>:w</code> , and then pressing <code>i</code> again to edit the file.''

'''''Tip''''': If you are adding another domain the <code>listen 80;</code> and <code>listen [::]:80;</code> isn't needed and you can go from <code>server {</code> to <code>server_name example.ms;</code>

''.''

Once you're completely done editing, save and quit the file by pressing the escape key and typing <code>:wq</code>. Finally, you can check your configuration file for errors by running <code>sudo nginx -t</code>. If there are any errors, refer back to your configuration file and see where you went wrong. In the event that nginx threw an error, review your configuration file and look for any missing <code>{</code>, <code>}</code>, or <code>;</code>. Every line that doesn't have curly brackets should end in a semicolon, which is probably the issue. If that isn't, then refer to your favorite search engine and start researching.

.

If nothing went wrong, and your configuration file is completely free of errors, run <code>cd ../sites-enabled</code> to move to the sites-enabled directory. Finally, to enable your website, run <code>sudo ln -s /etc/nginx/sites-available/example.ms ./</code> to create the symbolic link to your configuration file, and then run <code>sudo systemctl restart nginx</code> to restart nginx and make your changes go live.

==Verifying Functionality==
Of course, you'll want to make sure that everything you just did actually works. Run <code>cd /var/www/example.ms && sudo vim info.php</code> to move to your websites home directory and create the file <code>info.php</code>. Inside of the file, type the following:<pre>
<?php
phpinfo();
?>
</pre>... and then save and quit the file by pressing <code>escape</code> and typing <code>:wq</code>. Now, go to <code><nowiki>http://example.ms/info.php</nowiki></code>. If you didn't configure the nameservers for your domain to point to your new nginx server, then just replace the domain name with the IP of the server (refer to the <code>ifconfig</code> part of the [[Nginx#Installing nginx|Installing nginx]] section if you don't know how.)

 

If everything worked properly, you should see a PHP information page with a bunch of library authors and enabled modules. If it doesn't, research!

==Troubleshooting==
Over time we have run into a few quirks with this server that we listed here....

===Resetting the IP address===
Unfortunately we have found that from time to time on server reboots the server forgets the IP address for the webserver. Here is what you need to do to fix it.

Open up the ESXI sesson on .2 and access the webserver. Login with the server admin credentials, ask Chamberlain if you don't know. Enter the following commands...

sudo ifconfig ens32 x.x.x.11 netmask 255.255.255.0 (where x.x.x are the network address of our subnet)

sudo route add default gw x.x.x.1 ens32 (where x.x.x are the network address of our subnet)

==Conclusion==
By now, your nginx server should be up and fully operational. As always, if you're having any issues please [[Three Letter Acronym (TLA)|STFW]] before you ask people for advice!

 

Thank you,

- Tyler & Luke

Bradley Chamberlain

2022-05-20T22:06:32Z

Lchristopherson:

File:Bradley1.jpg

2022-05-20T22:03:59Z

Lchristopherson:

for the bradley chamberlain page

Bradley Chamberlain

2022-05-18T16:04:37Z

Lchristopherson: /* The rise of a legend */

== About ==
The god of creation and ending. The man who will kill you '''and''' your entire family with the '''''EtherWhip™''''' or '''''The Axe™''''' mercilessly if you happen to make him too upset. Bradley Chamberlain is the man who has founded 24PinTechnologies with his own bare two hands, and single-handedly became a legend among former gods, he has dethroned every god known to man and has become something inevitable. Bradley Chamberlain.

== Origin ==
It all began on November 1st, 1967. The man who will destroy anything and everything was born. Not much is known about Bradley's childhood life, but many speculate that Bradley Chamberlain lead a normal childhood life. In Bradley's young adult life, he engaged in the playing of a sport. That sports name would happen to be foosball... and it would change his life forever.

== Foosball era (appx. 1986-1994) ==
Bradley Chamberlain had taken a keen interest to Foosball. This is the first thing in Bradley's life that makes since to him, and allows him to truly be ''free''. One occasion during these Foosball days, appx. 1989, Bradley had come in contact with a very import man in the tech industry, a ''god'' named Scott Manchester. This Deity, ''Scott Manchester'' had challenged everyone in the establishment to a duel in Foosball. Scott had claimed that there was no one in the world who could dethrone Scott as the Foosball champion, and the ''Digital Deity™''. Scott had caused a riot. "''hmm, what's this?''" Bradley curiously denounced. Bradley took a look around to see everyone going crazy over something, but what? People stared cheering, "'''Di-gi-tal De-i-ty, Di-gi-tal De-i-ty'''". This chant piqued Bradley's interest. Bradley located the source of the chanting, the stage. Bradley walked up to the stage and challenged Scott Manchester to a Foosball duel to the death.

=== The rise of a legend ===
Scott noticed Bradley among all of the other smelly nerds, and silenced the crowd. "'''''So you wish to duel me? To the death?'''''" Scott responded. Bradley didn't reply. This made Scott furious. Bradley simply watched. As the crowd grew louder, Scott scoffed. Bradley finally made his way up to the ring with Scott Manchester waiting for him. Scott smirked, and began to speak, "WELC-"! Immediately Bradley teleported behind Scott Manchester with a blank face staring down. "Are you sure you'd like to finish that?" Bradley exclaimed.

=== The tale to be told for ages ===
Scott gulped. Without talking he started setting up the foosball table. Bradley walked to his side very slowly. When Bradley arrived to the table, the referee stated the stakes of this battle, "'''''You are betting your pride, titles, and lives. Do you both consent.'''''" Both of them nodded. Each of them gripped their handles, Scott grabbing a defensive and offensive handle, while Bradley grabbed two offensive handles. Scott smirked and thought, "''He's so stupid! Two offensive???''" Bradley said out loud, "'''Don't think so soon Scotty.'''" The game went on for approximately 4 minutes and 23 seconds. Bradley swept the floor with Scott. The crowd was in awe. As the last point was given to Bradley, Scott began begging for his life, and to be shown mercy. Bradley complied. Bradley would come to be known as one of the most merciful beings in existence. This battle is what allowed Bradley to gain his title as the '''Digital Deity'''.

== Beginning of the End (appx. 1997-2009) ==

== The founding of 24PinTechnologies (appx. 2010-present) ==

HTTPS with Certbot (LetsEncrypt)

2022-05-18T14:56:55Z

Lchristopherson:

User:Lchristopherson

2022-05-13T06:01:42Z

Lchristopherson: /* About */

User:Lchristopherson

2022-05-13T06:00:18Z

Lchristopherson: /* About */

Alumni

2022-05-13T05:59:01Z

Lchristopherson:

This is a list of notable alumni of the 24pintech program, if you would like to join the list after graduation please speak with Chamberlain.

*[[User:AOwen|Ashton Owen]]
*[[User:Lchristopherson|Luke Christopherson]]
*[[User:NShearer|Nathan Shearer]]
*[[User talk:Nick Perez|Nick Perez]]
*Omar Perez (W.I.P)

User:Lchristopherson

2022-05-13T05:57:24Z

Lchristopherson: Created page with "== About == Hey, my name is Luke Christopherson, and at the time of writing this article I am 17 years old, and about to graduate high school as a senior. I have had a tough time throughout my high school career, and never really found a place I wanted to be. I had switched schools many, many, many times due to a toxic home environment, and ended up at MHS. I transferred to IT Essentials from Video Game Development, and the thing I remember the most, is Bradley Chamber..."

HTTPS with Certbot (LetsEncrypt)

2022-05-13T00:31:40Z

Lchristopherson:

File:Certbot logo.png

2022-05-13T00:25:49Z

Lchristopherson:

certbot logo

HTTPS with Certbot (LetsEncrypt)

2022-05-13T00:24:44Z

Lchristopherson:

[[Category:Webserver]]

== About ==
When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.

By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot is a very simple

HTTPS with Certbot (LetsEncrypt)

2022-05-13T00:23:45Z

Lchristopherson:

[[Category:Webserver]]

== About ==
[[File:Certbot.png|left|thumb|126x126px]]
When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.

By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot is a very simple

Three Letter Acronym (TLA)

2022-05-12T23:22:56Z

Lchristopherson: added ssl to tla

== Topic ==
This page will be used for you to make yourself knowledgeable on a variety of tech acronyms. A wide array of acronyms, whether it be on hardware, networking, protocols, etc. These will be very important for any tech in 24Pintech. Learn them and know them well, otherwise you will fall victim to the ether whip.

== Cloud Computing: ==
'''DaaS:''' Desktop as a Service

'''IaaS''': Infrastructure as a Service

'''ICaaS''': Integration Capabilities as a Service

'''NaaS''': Network as a Service

'''PaaS''': Platform as a Service

'''SaaS''': Software as a service

== Hardware: ==
'''CLI''': Command Line Interface

'''CMOS''': Complementary Metal-Oxide Semiconductor

'''CPU''': Central Processing Unit

'''CRT''': Cathode Ray Tube

'''DIMM''': Dual In-line Memory Module

'''GPU''': Graphics Processing Unit

'''NAS''': Network Attached Storage

'''NIC''': Network Interface Card

'''POST''': Power-on Self Test

'''PC''': Personal Computer

'''RAM''': Random Access Memory

'''ROM''': Read-only Memory

'''TPM''': Trusted Platform Module

== Hypervisor/ Virtual ==
'''VDI''': Virtual Desktop Infrastructure

'''VM''': Virtual Machine

'''VNC''': Virtual Network Computer

'''VPN''': Virtual Private Network

== Networking: ==
'''DNS''': Domain Name Service

'''ISP''': Internet Service Provider

'''LAN''': Local Area Network

'''MAN''': Metropolitan Area Network

'''UC''': Unified Communications

'''WAN''': Wide Area Network

== Organizations: ==
'''ANSI''': American National Standards Institute

'''CCIA''': Computer and Communications Industry Association

'''CompTIA''': Computing Technology Industry Association

'''DEC''': Digital Equipment Corporation

'''EIA''': Electronics Industry Alliance

'''FCC''': Federal Communications Commission

'''IANA''': Internet Assigned Number Authority

'''IEEE''': Institute of Electrical and Electronics Engineers

'''IETF''': Internet Engineering Task Force

'''ITU-T''': International Telecommunication Union

'''MoCA''': Multimedia over Coax Alliance

'''OSI''': Open System Interconnect

'''TIA''': Telecommunications Industry Alliance

'''W3C''': World Wide Web Consortium

== Web server ==
'''LTS''': Long Term Support

== Protocol: ==
'''DHCP''': Dynamic Host Configuration Protocol

'''FTP''': File Transfer Protocol

'''HTTP''': Hypertext Transfer Protocol

'''HTTPS''': Hypertext Transfer Protocol Secure

'''IP''': Internet Protocol

'''PAP''': Password Authentication Protocol

'''PPP''': Point-to-Point Protocol

'''SMTP''': Secure Mail Transfer Protocol

'''TCP''': Transmission Control Protocol

'''TCTP''': Trivial File Transfer Protocol

== Security: ==
'''ACL''': Access Control List

'''AES''': Advanced Encryption Standard

'''DDoS''': Distributed Denial of Service

'''DES''': Data Encryption Standard

'''IDS''': Intrusion Detection System

'''IPS''': Intrusion Prevention System

'''MFA''': Multi Factor Authentication

'''RMM''': Remote Monitoring Management

'''SIEM''': Security Information and Event Management

'''TFA''': Two Factor Authentication

'''WPA''': Wi-Fi Protected Access

'''SSL''': Secure Socket Layer

== Misc: ==
'''CA''': Conditional Access

'''IB''': Install Base

'''PII''': Personally Identifiable Information

'''RTT''': Round Trip Time

'''STFW''': Search the F****ng Web

Adding a New Domain or Subdomain

2022-05-12T17:26:34Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80; # This is the port that Nginx will be listening on
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:20:27Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80; <code># This is the port that Nginx will be listening on</code>
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:19:41Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80; <code style="color:green"># This is the port that Nginx will be listening on</code>
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:16:20Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80; # This is the port that Nginx will be listening on
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:14:06Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<nowiki>
server {
listen 80; <style="color:green"># This is the port that Nginx will be listening on
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</nowiki>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:12:40Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80;</pre> <pre style="color:green"># This is the port that Nginx will be listening on</pre><pre>
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:12:06Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80; <pre style="color:green"># This is the port that Nginx will be listening on</pre>
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T17:09:38Z

Lchristopherson:

Adding a New Domain or Subdomain

2022-05-12T16:58:05Z

Lchristopherson:

[[Category:Webserver]]

== New Domains in Nginx ==

=== About ===
Generally speaking, adding a new (website/domain/server block) is very easy in [[Nginx]]. A common misconception throughout 24PinTech is that creating a server block is difficult, to try to curb the fear, I will go over adding a new website to our specific server setup.

==== What you need to start ====

* Access to a working [[Nginx]] Webserver
* A domain with a working A record pointing to our public IP address.
*[[HTTPS with Certbot (LetsEncrypt)|Certbot (LetsEncrypt)]]

=== Procedure ===

==== Configuring the Domain ====
[[File:Namecheap 2.png|thumb|365x365px]]
Before beginning any work on the webserver we need to make sure that the domain is ready to be used in unison with the webserver. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".
[[File:Namecheap .png|left|thumb]]
After making your way to the Advanced [[DNS]] settings, you will see a screen of A records that are what points the website "names" to actual IP addresses. To configure the domain to work with our webserver, select "''ADD NEW RECORD''", and select the "''A record''". You will make the host the "@" symbol, and the value will be the public IP of our webserver. Make sure you save the record, and the page. Once all of this is done, you are ready to begin the creation of the server block.
[[File:Esxi login.png|thumb]]

==== Log in to the Nginx Webserver ====
To begin your process of adding a server block to [[Nginx]] navigate to your favorite web browser and type in the address bar, "''10.21.25.2"''. This will take you to our Valhalla [[ESXi|ESXi box]], this is our [[ESXi|ESXi box]] that hosts all of our production VMs, which is also where devloganweb lives (our Webserver). If you are an administrator on our domain you may log in with your account for the in-class computers, otherwise see a server manager or [[Bradley Chamberlain]] for root account access. Navigate to the Webserver VM and log into it using the information provided in the secret sauce.

==== Creating the Nginx Server Block ====
Once you have logged into the webserver you will need to create an [[Nginx]] server block. Use the [[Linux Basics for Webserver]] page if any of the commands used are confusing to you. Make sure you have a full understanding of this process otherwise it will be a pain to debug.

Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

<pre>
server {
listen 80; # This is the port that Nginx will be listening on
listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

# If you're not going to be using a domain,
# then you can replace it with an IP
server_name domain.com;

# The root is the directory that the website files will be held in
root /var/www/domain.com;
index index.php index.html index.htm; # The default web page

location = /favicon.io {
log_not_found off;
access_log off;
}

location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}

location / {
try_files $uri $uri/ /index.php$args;
}

location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_pass unix:/run/php/php7.4-fpm.sock; # Change this to current php version
}

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
</pre>

==== Enabling the Server Block ====
This is the completed server config. All configs vary based on what type of website you are creating, but this should work for a basic [[WordPress]] website. [[Vim/Nano|Save and exit]] your file. Next you need to enable the site. To do this, you will run the command <code>sudo ln -s ./example.org ../sites-enabled</code> . This command is saying to make a [https://devdojo.com/devdojo/what-is-a-symlink symbolic link] for the server config available site, to the enabled directory. This is essentially how you enable a server config in [[Nginx]].
[[File:Nginx successful config.png|thumb|507x507px]]
Before applying the config changes, you need to run <code>sudo nginx -t</code> to check the [[Nginx]] configuration, if this doesn't return something similar to the example picture, that means the configuration file you have just edited is faulty. This could mean many things, from forgetting a semicolon at the end of a line, to using a setting that is not allowed. This is where you must debug the file, and use those skills you have been learning. Once the test returns successful, you will run <code>sudo systemctl restart nginx</code>. To restart the [[Nginx]] service. This will enable the website, and you can move on to the next step.

==== Testing Working Configuration ====
To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

<pre>
<?php
phpinfo();
?>
</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.

Now the Server block is successfully set up. Congratulations.

== New Sub-Domain in Nginx ==

=== About ===
Adding subdomains is a really easy process and doesn't change a lot from adding a normal domain. You'll just need to remember the general process from the Adding a Domain section.

=== Subdomain Setup ===
The same process for adding a subdomain in [https://www.namecheap.com/ Namecheap] will be used as adding a normal domain. For the host variable, instad of using the "@" symbol, you will instead type the name of the subdomain. ex. for wiki.example.org, the host variable will be "wiki". Remember to save the Record and the page. Then you are ready to begin the server setup.

=== Procedure ===
To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp ./example.com ./subdomain.example.org</code> or creating a new file by running <code>sudo nano subdomain.example.org</code>. If you copied it, edit the file by running <code>sudo nano subdomain.example.org</code>.

==== What needs to be changed ====
The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Find where the variables are located, and change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.org</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.org/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:
# before
root /var/www/example.org;

# after
root /var/www/example.org/subdomain;
The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
# before
server_name example.org;

# after
server_name subdomain.example.org;
Once you've made the proper changes, save and quit the file. Then, run <code>cd ../sites-enabled && sudo ln -s ../sites-available/subdomain.example.org./</code> . Check the [[Nginx]] configuration by running <code>sudo nginx -t</code> for a successful return. Once that is done, restart [[Nginx]] by running <code>sudo systemctl restart nginx</code>.

Adding a New Domain or Subdomain

2022-05-12T16:38:34Z

Lchristopherson:

Adding a New Domain or Subdomain

2022-05-12T16:36:29Z

Lchristopherson:

Adding a New Domain or Subdomain

2022-05-12T16:21:12Z

Lchristopherson:

File:Namecheap .png

2022-05-12T16:19:48Z

Lchristopherson:

a record

Adding a New Domain or Subdomain

2022-05-12T16:16:42Z

Lchristopherson:

File:Namecheap 2.png

2022-05-12T16:04:54Z

Lchristopherson:

namecheap manage page

File:Nginx successful config.png

2022-05-12T15:52:50Z

Lchristopherson:

successful "sudo nginx -t"

Important Nginx Directories

2022-05-12T15:39:44Z

Lchristopherson:

[[Category:Webserver]]

== About ==
This wiki entry's purpose is to list all important directories for managing the web server. Here you will find all of the server blocks exact location, as well as all of the websites files. I will try to list every config file I have edited throughout the course of the year to help with future debugging.

== Directories ==

=== Server blocks/Website config files ===
<code>/etc/nginx/sites-available</code> 
<code>/etc/nginx/sites-enabled</code>

=== 24pin.tech ===
<code>/var/www/24pin.tech</code>

=== service.24pin.tech ===
<code>/var/www/service.24pin.tech</code>

=== wiki.24pin.tech ===
<code>/var/www/wiki.24pin.tech</code>

=== evit.computer ===
<code>/var/www/evit.computer</code>

== Files ==

=== Manual Network Config ===
<code>/etc/netplan/50-cloud-init.yaml</code>

=== DNS Nameserver Config ===
<code>/etc/resolv.conf</code>

Adding a New Domain or Subdomain

2022-05-10T16:52:28Z

Lchristopherson:

Adding a New Domain or Subdomain

2022-05-10T16:48:41Z

Lchristopherson:

Adding a New Domain or Subdomain

2022-05-10T16:47:54Z

Lchristopherson:

Adding a New Domain or Subdomain

2022-05-10T16:44:17Z

Lchristopherson: