https://wiki.24pin.tech/api.php?action=feedcontributions&feedformat=atom&user=Tgriego 2026-05-08T13:17:26Z User contributions MediaWiki 1.37.1 https://wiki.24pin.tech/index.php?title=Nginx&diff=1121 2021-03-08T21:44:41Z

<p>Tgriego: /* Adding HTTPS to a domain with LetsEncrypt (certbot) */</p> <hr /> <div>==About==<br /> 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.<br /> <br /> ==Prerequisites==<br /> 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.)<br /> <br /> *nginx/1.14.0 (Ubuntu)<br /> *PHP 7.2.10-0ubuntu0.18.04.1 (cli)<br /> *MySQL v14.14 Distribution 5.7.24<br /> <br /> If you've just installed a new operating system, you'll want to update your local package index by running &lt;code&gt;sudo apt-get update&lt;/code&gt;, and then add the Universe repository by running &lt;code&gt;sudo apt-add-repository universe&lt;/code&gt;.<br /> <br /> ==Installing nginx==<br /> To start, you're going to want to install nginx using the aptitude package manager. You can do this by running &lt;code&gt;sudo apt-get install nginx&lt;/code&gt;. Once you run that, you'll want to go through the configuration prompt that appears.<br /> <br /> .<br /> <br /> After nginx and its subsequent dependencies have finished installing, you'll want to let it through the firewall by running &lt;code&gt;sudo ufw allow 'Nginx HTTP'&lt;/code&gt;. Check what your current IP is by running &lt;code&gt;ifconfig&lt;/code&gt;, and then look for whatever interface looks correct. In this instance, the proper interface is &lt;code&gt;eth0&lt;/code&gt;.<br /> <br /> .<br /> <br /> [[File:Ifconfig-example.png|left|frame|an example of the results from ifconfig]]<br /> 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 &lt;code&gt;&lt;nowiki&gt;http://{ip}/&lt;/nowiki&gt;&lt;/code&gt; where &lt;code&gt;{ip}&lt;/code&gt; is what follows after '''''inet'''''.<br /> <br /> If the default nginx page displays, continue to the next section.<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Installing MySQL==<br /> 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 &lt;code&gt;sudo apt-get install mysql-server&lt;/code&gt;, and then once it finishes run the setup script by typing &lt;code&gt;sudo mysql_secure_installation&lt;/code&gt;.<br /> <br /> .<br /> <br /> The first thing that the installations script will ask you is if you'd like to enable the &lt;code&gt;VALIDATE PASSWORD PLUGIN&lt;/code&gt;, 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.'''<br /> <br /> .<br /> <br /> 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.<br /> <br /> ==Installing PHP==<br /> Again, installing PHP is very similar to two sections preceding this one. Start off by installing the &lt;code&gt;php-fpm&lt;/code&gt; and &lt;code&gt;php-mysql&lt;/code&gt; packages by running &lt;code&gt;sudo apt-get install php-fpm php-mysql&lt;/code&gt;. After it installs, you'll want to edit &lt;code&gt;php.ini&lt;/code&gt; by running &lt;code&gt;sudo vim /etc/php/7.2/fpm/php.ini&lt;/code&gt;.<br /> <br /> .<br /> <br /> '''''Note:''' If the file isn't found, check'' the directory path by using the &lt;code&gt;cd&lt;/code&gt; command and seeing where something doesn't exist.<br /> <br /> .<br /> <br /> If you're using Vim, type a &lt;code&gt;?&lt;/code&gt; and search for &lt;code&gt;cgi.fix_pathinfo&lt;/code&gt;. You should be taken to a line that's commented out and says &lt;code&gt;;cgi.fix_pathinfo=0&lt;/code&gt; or something similar. Press the &lt;code&gt;i&lt;/code&gt; key to start editing and remove the &lt;code&gt;;&lt;/code&gt; to uncomment it. If the variable is set to 1, change it to 0. Press the &lt;code&gt;escape&lt;/code&gt; key and type &lt;code&gt;:wq&lt;/code&gt; to save and quit your changes. If you didn't run Vim as a superuser (if you didn't run the command with &lt;code&gt;sudo&lt;/code&gt;), it will throw and error and the file won't save.<br /> <br /> .<br /> <br /> Once the file saves, run &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt; to restart PHP.<br /> <br /> ==Configuring nginx==<br /> The configuration for nginx is a little different compared to anything you might be used to. To start, there are two directories: &lt;code&gt;sites-available&lt;/code&gt; and &lt;code&gt;sites-enabled&lt;/code&gt;. The former directory actually contains the configuration files, while the latter contains symbolic links to the configuration files and enables them.<br /> <br /> .<br /> <br /> To start, lets say that we wanted to configure our nginx server to work with the domain &lt;code&gt;example.ms&lt;/code&gt;. First, we'd want to verify that the directory &lt;code&gt;/var/www/example.ms&lt;/code&gt; exists. Move to the &lt;code&gt;sites-available&lt;/code&gt; directory by entering the command &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Next, you'll want to create a new configuration file with the name of the domain. You can either by running &lt;code&gt;sudo touch example.ms &amp;&amp; sudo vim example.ms&lt;/code&gt; or simply by running &lt;code&gt;sudo vim example.ms&lt;/code&gt; since Vim creates the file if it doesn't exist. Again, press &lt;code&gt;i&lt;/code&gt; to edit the file. Once you're in edit mode, you'll want the contents to look something like this:&lt;pre&gt;<br /> server {<br /> listen 80;<br /> listen [::]:80;<br /> <br /> # this is a comment! you don't have to include this, but if you're not<br /> # going to be using a domain, then you can replace it with an IP<br /> server_name example.ms;<br /> <br /> root /var/www/example.ms;<br /> index index.php index.html index.htm;<br /> <br /> location = /favicon.io {<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location = /robots.txt {<br /> allow all;<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location / {<br /> try_files $uri $uri/ /index.php$args;<br /> }<br /> <br /> location ~ \.php$ {<br /> include snippets/fastcgi-php.conf;<br /> fastcgi_intercept_errors on;<br /> fastcgi_pass unix:/run/php/php7.2-fpm.sock;<br /> }<br /> <br /> location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {<br /> expires max;<br /> log_not_found off;<br /> }<br /> }<br /> &lt;/pre&gt;'''''Tip:''' You can periodically save your configuration file by pressing &lt;code&gt;escape&lt;/code&gt;, typing &lt;code&gt;:w&lt;/code&gt; , and then pressing &lt;code&gt;i&lt;/code&gt; again to edit the file.''<br /> <br /> '''''Tip''''': If you are adding another domain the &lt;code&gt;listen 80;&lt;/code&gt; and &lt;code&gt;listen [::]:80;&lt;/code&gt; isn't needed and you can go from &lt;code&gt;server {&lt;/code&gt; to &lt;code&gt;server_name example.ms;&lt;/code&gt;<br /> <br /> ''.''<br /> <br /> Once you're completely done editing, save and quit the file by pressing the escape key and typing &lt;code&gt;:wq&lt;/code&gt;. Finally, you can check your configuration file for errors by running &lt;code&gt;sudo nginx -t&lt;/code&gt;. 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 &lt;code&gt;{&lt;/code&gt;, &lt;code&gt;}&lt;/code&gt;, or &lt;code&gt;;&lt;/code&gt;. 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.<br /> <br /> .<br /> <br /> If nothing went wrong, and your configuration file is completely free of errors, run &lt;code&gt;cd ../sites-enabled&lt;/code&gt; to move to the sites-enabled directory. Finally, to enable your website, run &lt;code&gt;sudo ln -s /etc/nginx/sites-available/example.ms ./&lt;/code&gt; to create the symbolic link to your configuration file, and then run &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt; to restart nginx and make your changes go live.<br /> <br /> ==Verifying Functionality==<br /> Of course, you'll want to make sure that everything you just did actually works. Run &lt;code&gt;cd /var/www/example.ms &amp;&amp; sudo vim info.php&lt;/code&gt; to move to your websites home directory and create the file &lt;code&gt;info.php&lt;/code&gt;. Inside of the file, type the following:&lt;pre&gt;<br /> &lt;?php<br /> phpinfo();<br /> ?&gt;<br /> &lt;/pre&gt;... and then save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Now, go to &lt;code&gt;&lt;nowiki&gt;http://example.ms/info.php&lt;/nowiki&gt;&lt;/code&gt;. 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 &lt;code&gt;ifconfig&lt;/code&gt; part of the [[Nginx#Installing nginx|Installing nginx]] section if you don't know how.)<br /> <br /> .<br /> <br /> 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!<br /> <br /> ==Subdomains==<br /> Adding subdomains is really easy and doesn't require a lot of effort. You'll just need to remember the general process from the [[Nginx#Configuring nginx|Configuring nginx]] section.<br /> <br /> .<br /> <br /> To start, navigate to the &lt;code&gt;sites-available&lt;/code&gt; directory by running &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Then, you can either copy a pre-existing configuration by running &lt;code&gt;sudo cp example.ms subdomain.example.ms&lt;/code&gt; or creating a new file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;. If you copied it, edit the file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;.<br /> <br /> ===What needs to be changed===<br /> The only important things that need to be changed are the &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;server_name&lt;/code&gt; variables. Press &lt;code&gt;i&lt;/code&gt; to start editing the file in Vim, and then find where the variables are located. Change the &lt;code&gt;root&lt;/code&gt; 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 &lt;code&gt;subdomain.example.ms&lt;/code&gt;, we'd create a new folder by running the command &lt;code&gt;sudo mkdir /var/www/example.ms/subdomain&lt;/code&gt;. Then, we'd modify our &lt;code&gt;root&lt;/code&gt; variable to look something like this:&lt;pre&gt;<br /> # before<br /> root /var/www/example.ms;<br /> <br /> # after<br /> root /var/www/example.ms/subdomain;<br /> &lt;/pre&gt;The &lt;code&gt;server_name&lt;/code&gt; variable is just as simple. Just add the subdomain prefix to the beginning of your domain:<br /> # before<br /> server_name example.ms;<br /> <br /> # after<br /> server_name subdomain.example.ms;<br /> Once you've made the proper changes, save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Then, run &lt;code&gt;cd ../sites-enabled &amp;&amp; sudo ln -s /etc/nginx/sites-available/subdomain.example.ms ./&lt;/code&gt; and restart nginx by running &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt;.<br /> <br /> ==Adding other domains (that aren't subdomains)==<br /> The process is exactly the same as adding a subdomain, except instead of adding a prefix the value of &lt;code&gt;server_name&lt;/code&gt; you'll just completely change the domain. Again, don't forget to create the symbolic link to the configuration file and ''especially'' don't forget to restart nginx after saving the config/creating the symbolic link. When you're creating the folder to contain the contents for the server, create a new folder that has the name of the domain. So, for instance, if I was creating example2.ms, I'd run &lt;code&gt;sudo mkdir /var/www/example2.ms&lt;/code&gt;. Now that the domain is ready go to [http://wiki.24pin.tech/index.php?title=WordPress WordPress]if you are planning on using WordPress as your editor.<br /> <br /> ==Adding HTTPS to a domain with LetsEncrypt (certbot)==<br /> If you're adding a new domain to Nginx and want to enable https on a new domain, run &lt;code&gt;sudo certbot --nginx -d domain.com&lt;/code&gt; where &lt;code&gt;domain.com&lt;/code&gt; is the domain that you want to add. Once you've done this, check the domain and look for a lock icon in the url bar of your browser. In the event that you don't already have certbot installed, run the following commands:<br /> <br /> * &lt;code&gt;sudo apt-get install certbot&lt;/code&gt;<br /> * &lt;code&gt;sudo apt-get install python-certbot-nginx&lt;/code&gt;<br /> <br /> '''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.'''<br /> <br /> ==Conclusion==<br /> By now, your nginx server should be up and fully operational. As always, if you're having any issues please STFW before you ask people for advice!<br /> <br /> .<br /> <br /> Thank you,<br /> <br /> - Tyler</div>

Tgriego https://wiki.24pin.tech/index.php?title=Nginx&diff=1120 2021-03-08T21:22:38Z

<p>Tgriego: finished the https section</p> <hr /> <div>==About==<br /> 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.<br /> <br /> ==Prerequisites==<br /> 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.)<br /> <br /> *nginx/1.14.0 (Ubuntu)<br /> *PHP 7.2.10-0ubuntu0.18.04.1 (cli)<br /> *MySQL v14.14 Distribution 5.7.24<br /> <br /> If you've just installed a new operating system, you'll want to update your local package index by running &lt;code&gt;sudo apt-get update&lt;/code&gt;, and then add the Universe repository by running &lt;code&gt;sudo apt-add-repository universe&lt;/code&gt;.<br /> <br /> ==Installing nginx==<br /> To start, you're going to want to install nginx using the aptitude package manager. You can do this by running &lt;code&gt;sudo apt-get install nginx&lt;/code&gt;. Once you run that, you'll want to go through the configuration prompt that appears.<br /> <br /> .<br /> <br /> After nginx and its subsequent dependencies have finished installing, you'll want to let it through the firewall by running &lt;code&gt;sudo ufw allow 'Nginx HTTP'&lt;/code&gt;. Check what your current IP is by running &lt;code&gt;ifconfig&lt;/code&gt;, and then look for whatever interface looks correct. In this instance, the proper interface is &lt;code&gt;eth0&lt;/code&gt;.<br /> <br /> .<br /> <br /> [[File:Ifconfig-example.png|left|frame|an example of the results from ifconfig]]<br /> 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 &lt;code&gt;&lt;nowiki&gt;http://{ip}/&lt;/nowiki&gt;&lt;/code&gt; where &lt;code&gt;{ip}&lt;/code&gt; is what follows after '''''inet'''''.<br /> <br /> If the default nginx page displays, continue to the next section.<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Installing MySQL==<br /> 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 &lt;code&gt;sudo apt-get install mysql-server&lt;/code&gt;, and then once it finishes run the setup script by typing &lt;code&gt;sudo mysql_secure_installation&lt;/code&gt;.<br /> <br /> .<br /> <br /> The first thing that the installations script will ask you is if you'd like to enable the &lt;code&gt;VALIDATE PASSWORD PLUGIN&lt;/code&gt;, 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.'''<br /> <br /> .<br /> <br /> 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.<br /> <br /> ==Installing PHP==<br /> Again, installing PHP is very similar to two sections preceding this one. Start off by installing the &lt;code&gt;php-fpm&lt;/code&gt; and &lt;code&gt;php-mysql&lt;/code&gt; packages by running &lt;code&gt;sudo apt-get install php-fpm php-mysql&lt;/code&gt;. After it installs, you'll want to edit &lt;code&gt;php.ini&lt;/code&gt; by running &lt;code&gt;sudo vim /etc/php/7.2/fpm/php.ini&lt;/code&gt;.<br /> <br /> .<br /> <br /> '''''Note:''' If the file isn't found, check'' the directory path by using the &lt;code&gt;cd&lt;/code&gt; command and seeing where something doesn't exist.<br /> <br /> .<br /> <br /> If you're using Vim, type a &lt;code&gt;?&lt;/code&gt; and search for &lt;code&gt;cgi.fix_pathinfo&lt;/code&gt;. You should be taken to a line that's commented out and says &lt;code&gt;;cgi.fix_pathinfo=0&lt;/code&gt; or something similar. Press the &lt;code&gt;i&lt;/code&gt; key to start editing and remove the &lt;code&gt;;&lt;/code&gt; to uncomment it. If the variable is set to 1, change it to 0. Press the &lt;code&gt;escape&lt;/code&gt; key and type &lt;code&gt;:wq&lt;/code&gt; to save and quit your changes. If you didn't run Vim as a superuser (if you didn't run the command with &lt;code&gt;sudo&lt;/code&gt;), it will throw and error and the file won't save.<br /> <br /> .<br /> <br /> Once the file saves, run &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt; to restart PHP.<br /> <br /> ==Configuring nginx==<br /> The configuration for nginx is a little different compared to anything you might be used to. To start, there are two directories: &lt;code&gt;sites-available&lt;/code&gt; and &lt;code&gt;sites-enabled&lt;/code&gt;. The former directory actually contains the configuration files, while the latter contains symbolic links to the configuration files and enables them.<br /> <br /> .<br /> <br /> To start, lets say that we wanted to configure our nginx server to work with the domain &lt;code&gt;example.ms&lt;/code&gt;. First, we'd want to verify that the directory &lt;code&gt;/var/www/example.ms&lt;/code&gt; exists. Move to the &lt;code&gt;sites-available&lt;/code&gt; directory by entering the command &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Next, you'll want to create a new configuration file with the name of the domain. You can either by running &lt;code&gt;sudo touch example.ms &amp;&amp; sudo vim example.ms&lt;/code&gt; or simply by running &lt;code&gt;sudo vim example.ms&lt;/code&gt; since Vim creates the file if it doesn't exist. Again, press &lt;code&gt;i&lt;/code&gt; to edit the file. Once you're in edit mode, you'll want the contents to look something like this:&lt;pre&gt;<br /> server {<br /> listen 80;<br /> listen [::]:80;<br /> <br /> # this is a comment! you don't have to include this, but if you're not<br /> # going to be using a domain, then you can replace it with an IP<br /> server_name example.ms;<br /> <br /> root /var/www/example.ms;<br /> index index.php index.html index.htm;<br /> <br /> location = /favicon.io {<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location = /robots.txt {<br /> allow all;<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location / {<br /> try_files $uri $uri/ /index.php$args;<br /> }<br /> <br /> location ~ \.php$ {<br /> include snippets/fastcgi-php.conf;<br /> fastcgi_intercept_errors on;<br /> fastcgi_pass unix:/run/php/php7.2-fpm.sock;<br /> }<br /> <br /> location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {<br /> expires max;<br /> log_not_found off;<br /> }<br /> }<br /> &lt;/pre&gt;'''''Tip:''' You can periodically save your configuration file by pressing &lt;code&gt;escape&lt;/code&gt;, typing &lt;code&gt;:w&lt;/code&gt; , and then pressing &lt;code&gt;i&lt;/code&gt; again to edit the file.''<br /> <br /> '''''Tip''''': If you are adding another domain the &lt;code&gt;listen 80;&lt;/code&gt; and &lt;code&gt;listen [::]:80;&lt;/code&gt; isn't needed and you can go from &lt;code&gt;server {&lt;/code&gt; to &lt;code&gt;server_name example.ms;&lt;/code&gt;<br /> <br /> ''.''<br /> <br /> Once you're completely done editing, save and quit the file by pressing the escape key and typing &lt;code&gt;:wq&lt;/code&gt;. Finally, you can check your configuration file for errors by running &lt;code&gt;sudo nginx -t&lt;/code&gt;. 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 &lt;code&gt;{&lt;/code&gt;, &lt;code&gt;}&lt;/code&gt;, or &lt;code&gt;;&lt;/code&gt;. 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.<br /> <br /> .<br /> <br /> If nothing went wrong, and your configuration file is completely free of errors, run &lt;code&gt;cd ../sites-enabled&lt;/code&gt; to move to the sites-enabled directory. Finally, to enable your website, run &lt;code&gt;sudo ln -s /etc/nginx/sites-available/example.ms ./&lt;/code&gt; to create the symbolic link to your configuration file, and then run &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt; to restart nginx and make your changes go live.<br /> <br /> ==Verifying Functionality==<br /> Of course, you'll want to make sure that everything you just did actually works. Run &lt;code&gt;cd /var/www/example.ms &amp;&amp; sudo vim info.php&lt;/code&gt; to move to your websites home directory and create the file &lt;code&gt;info.php&lt;/code&gt;. Inside of the file, type the following:&lt;pre&gt;<br /> &lt;?php<br /> phpinfo();<br /> ?&gt;<br /> &lt;/pre&gt;... and then save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Now, go to &lt;code&gt;&lt;nowiki&gt;http://example.ms/info.php&lt;/nowiki&gt;&lt;/code&gt;. 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 &lt;code&gt;ifconfig&lt;/code&gt; part of the [[Nginx#Installing nginx|Installing nginx]] section if you don't know how.)<br /> <br /> .<br /> <br /> 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!<br /> <br /> ==Subdomains==<br /> Adding subdomains is really easy and doesn't require a lot of effort. You'll just need to remember the general process from the [[Nginx#Configuring nginx|Configuring nginx]] section.<br /> <br /> .<br /> <br /> To start, navigate to the &lt;code&gt;sites-available&lt;/code&gt; directory by running &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Then, you can either copy a pre-existing configuration by running &lt;code&gt;sudo cp example.ms subdomain.example.ms&lt;/code&gt; or creating a new file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;. If you copied it, edit the file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;.<br /> <br /> ===What needs to be changed===<br /> The only important things that need to be changed are the &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;server_name&lt;/code&gt; variables. Press &lt;code&gt;i&lt;/code&gt; to start editing the file in Vim, and then find where the variables are located. Change the &lt;code&gt;root&lt;/code&gt; 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 &lt;code&gt;subdomain.example.ms&lt;/code&gt;, we'd create a new folder by running the command &lt;code&gt;sudo mkdir /var/www/example.ms/subdomain&lt;/code&gt;. Then, we'd modify our &lt;code&gt;root&lt;/code&gt; variable to look something like this:&lt;pre&gt;<br /> # before<br /> root /var/www/example.ms;<br /> <br /> # after<br /> root /var/www/example.ms/subdomain;<br /> &lt;/pre&gt;The &lt;code&gt;server_name&lt;/code&gt; variable is just as simple. Just add the subdomain prefix to the beginning of your domain:<br /> # before<br /> server_name example.ms;<br /> <br /> # after<br /> server_name subdomain.example.ms;<br /> Once you've made the proper changes, save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Then, run &lt;code&gt;cd ../sites-enabled &amp;&amp; sudo ln -s /etc/nginx/sites-available/subdomain.example.ms ./&lt;/code&gt; and restart nginx by running &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt;.<br /> <br /> ==Adding other domains (that aren't subdomains)==<br /> The process is exactly the same as adding a subdomain, except instead of adding a prefix the value of &lt;code&gt;server_name&lt;/code&gt; you'll just completely change the domain. Again, don't forget to create the symbolic link to the configuration file and ''especially'' don't forget to restart nginx after saving the config/creating the symbolic link. When you're creating the folder to contain the contents for the server, create a new folder that has the name of the domain. So, for instance, if I was creating example2.ms, I'd run &lt;code&gt;sudo mkdir /var/www/example2.ms&lt;/code&gt;. Now that the domain is ready go to [http://wiki.24pin.tech/index.php?title=WordPress WordPress]if you are planning on using WordPress as your editor.<br /> <br /> ==Adding HTTPS to a domain with LetsEncrypt (certbot)==<br /> If you're adding a new domain to Nginx and want to enable https on a new domain, run &lt;code&gt;sudo certbot --nginx -d domain.com&lt;/code&gt; where &lt;code&gt;domain.com&lt;/code&gt; is the domain that you want to add. Once you've done this, check the domain and look for a lock icon in the url bar of your browser.<br /> <br /> '''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.'''<br /> <br /> ==Conclusion==<br /> By now, your nginx server should be up and fully operational. As always, if you're having any issues please STFW before you ask people for advice!<br /> <br /> .<br /> <br /> Thank you,<br /> <br /> - Tyler</div>

Tgriego https://wiki.24pin.tech/index.php?title=Nginx&diff=1119 2021-03-08T21:13:22Z

<p>Tgriego: new section</p> <hr /> <div>==About==<br /> 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.<br /> <br /> ==Prerequisites==<br /> 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.)<br /> <br /> *nginx/1.14.0 (Ubuntu)<br /> *PHP 7.2.10-0ubuntu0.18.04.1 (cli)<br /> *MySQL v14.14 Distribution 5.7.24<br /> <br /> If you've just installed a new operating system, you'll want to update your local package index by running &lt;code&gt;sudo apt-get update&lt;/code&gt;, and then add the Universe repository by running &lt;code&gt;sudo apt-add-repository universe&lt;/code&gt;.<br /> <br /> ==Installing nginx==<br /> To start, you're going to want to install nginx using the aptitude package manager. You can do this by running &lt;code&gt;sudo apt-get install nginx&lt;/code&gt;. Once you run that, you'll want to go through the configuration prompt that appears.<br /> <br /> .<br /> <br /> After nginx and its subsequent dependencies have finished installing, you'll want to let it through the firewall by running &lt;code&gt;sudo ufw allow 'Nginx HTTP'&lt;/code&gt;. Check what your current IP is by running &lt;code&gt;ifconfig&lt;/code&gt;, and then look for whatever interface looks correct. In this instance, the proper interface is &lt;code&gt;eth0&lt;/code&gt;.<br /> <br /> .<br /> <br /> [[File:Ifconfig-example.png|left|frame|an example of the results from ifconfig]]<br /> 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 &lt;code&gt;&lt;nowiki&gt;http://{ip}/&lt;/nowiki&gt;&lt;/code&gt; where &lt;code&gt;{ip}&lt;/code&gt; is what follows after '''''inet'''''.<br /> <br /> If the default nginx page displays, continue to the next section.<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Installing MySQL==<br /> 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 &lt;code&gt;sudo apt-get install mysql-server&lt;/code&gt;, and then once it finishes run the setup script by typing &lt;code&gt;sudo mysql_secure_installation&lt;/code&gt;.<br /> <br /> .<br /> <br /> The first thing that the installations script will ask you is if you'd like to enable the &lt;code&gt;VALIDATE PASSWORD PLUGIN&lt;/code&gt;, 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.'''<br /> <br /> .<br /> <br /> 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.<br /> <br /> ==Installing PHP==<br /> Again, installing PHP is very similar to two sections preceding this one. Start off by installing the &lt;code&gt;php-fpm&lt;/code&gt; and &lt;code&gt;php-mysql&lt;/code&gt; packages by running &lt;code&gt;sudo apt-get install php-fpm php-mysql&lt;/code&gt;. After it installs, you'll want to edit &lt;code&gt;php.ini&lt;/code&gt; by running &lt;code&gt;sudo vim /etc/php/7.2/fpm/php.ini&lt;/code&gt;.<br /> <br /> .<br /> <br /> '''''Note:''' If the file isn't found, check'' the directory path by using the &lt;code&gt;cd&lt;/code&gt; command and seeing where something doesn't exist.<br /> <br /> .<br /> <br /> If you're using Vim, type a &lt;code&gt;?&lt;/code&gt; and search for &lt;code&gt;cgi.fix_pathinfo&lt;/code&gt;. You should be taken to a line that's commented out and says &lt;code&gt;;cgi.fix_pathinfo=0&lt;/code&gt; or something similar. Press the &lt;code&gt;i&lt;/code&gt; key to start editing and remove the &lt;code&gt;;&lt;/code&gt; to uncomment it. If the variable is set to 1, change it to 0. Press the &lt;code&gt;escape&lt;/code&gt; key and type &lt;code&gt;:wq&lt;/code&gt; to save and quit your changes. If you didn't run Vim as a superuser (if you didn't run the command with &lt;code&gt;sudo&lt;/code&gt;), it will throw and error and the file won't save.<br /> <br /> .<br /> <br /> Once the file saves, run &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt; to restart PHP.<br /> <br /> ==Configuring nginx==<br /> The configuration for nginx is a little different compared to anything you might be used to. To start, there are two directories: &lt;code&gt;sites-available&lt;/code&gt; and &lt;code&gt;sites-enabled&lt;/code&gt;. The former directory actually contains the configuration files, while the latter contains symbolic links to the configuration files and enables them.<br /> <br /> .<br /> <br /> To start, lets say that we wanted to configure our nginx server to work with the domain &lt;code&gt;example.ms&lt;/code&gt;. First, we'd want to verify that the directory &lt;code&gt;/var/www/example.ms&lt;/code&gt; exists. Move to the &lt;code&gt;sites-available&lt;/code&gt; directory by entering the command &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Next, you'll want to create a new configuration file with the name of the domain. You can either by running &lt;code&gt;sudo touch example.ms &amp;&amp; sudo vim example.ms&lt;/code&gt; or simply by running &lt;code&gt;sudo vim example.ms&lt;/code&gt; since Vim creates the file if it doesn't exist. Again, press &lt;code&gt;i&lt;/code&gt; to edit the file. Once you're in edit mode, you'll want the contents to look something like this:&lt;pre&gt;<br /> server {<br /> listen 80;<br /> listen [::]:80;<br /> <br /> # this is a comment! you don't have to include this, but if you're not<br /> # going to be using a domain, then you can replace it with an IP<br /> server_name example.ms;<br /> <br /> root /var/www/example.ms;<br /> index index.php index.html index.htm;<br /> <br /> location = /favicon.io {<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location = /robots.txt {<br /> allow all;<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location / {<br /> try_files $uri $uri/ /index.php$args;<br /> }<br /> <br /> location ~ \.php$ {<br /> include snippets/fastcgi-php.conf;<br /> fastcgi_intercept_errors on;<br /> fastcgi_pass unix:/run/php/php7.2-fpm.sock;<br /> }<br /> <br /> location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {<br /> expires max;<br /> log_not_found off;<br /> }<br /> }<br /> &lt;/pre&gt;'''''Tip:''' You can periodically save your configuration file by pressing &lt;code&gt;escape&lt;/code&gt;, typing &lt;code&gt;:w&lt;/code&gt; , and then pressing &lt;code&gt;i&lt;/code&gt; again to edit the file.''<br /> <br /> '''''Tip''''': If you are adding another domain the &lt;code&gt;listen 80;&lt;/code&gt; and &lt;code&gt;listen [::]:80;&lt;/code&gt; isn't needed and you can go from &lt;code&gt;server {&lt;/code&gt; to &lt;code&gt;server_name example.ms;&lt;/code&gt;<br /> <br /> ''.''<br /> <br /> Once you're completely done editing, save and quit the file by pressing the escape key and typing &lt;code&gt;:wq&lt;/code&gt;. Finally, you can check your configuration file for errors by running &lt;code&gt;sudo nginx -t&lt;/code&gt;. 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 &lt;code&gt;{&lt;/code&gt;, &lt;code&gt;}&lt;/code&gt;, or &lt;code&gt;;&lt;/code&gt;. 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.<br /> <br /> .<br /> <br /> If nothing went wrong, and your configuration file is completely free of errors, run &lt;code&gt;cd ../sites-enabled&lt;/code&gt; to move to the sites-enabled directory. Finally, to enable your website, run &lt;code&gt;sudo ln -s /etc/nginx/sites-available/example.ms ./&lt;/code&gt; to create the symbolic link to your configuration file, and then run &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt; to restart nginx and make your changes go live.<br /> <br /> ==Verifying Functionality==<br /> Of course, you'll want to make sure that everything you just did actually works. Run &lt;code&gt;cd /var/www/example.ms &amp;&amp; sudo vim info.php&lt;/code&gt; to move to your websites home directory and create the file &lt;code&gt;info.php&lt;/code&gt;. Inside of the file, type the following:&lt;pre&gt;<br /> &lt;?php<br /> phpinfo();<br /> ?&gt;<br /> &lt;/pre&gt;... and then save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Now, go to &lt;code&gt;&lt;nowiki&gt;http://example.ms/info.php&lt;/nowiki&gt;&lt;/code&gt;. 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 &lt;code&gt;ifconfig&lt;/code&gt; part of the [[Nginx#Installing nginx|Installing nginx]] section if you don't know how.)<br /> <br /> .<br /> <br /> 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!<br /> <br /> ==Subdomains==<br /> Adding subdomains is really easy and doesn't require a lot of effort. You'll just need to remember the general process from the [[Nginx#Configuring nginx|Configuring nginx]] section.<br /> <br /> .<br /> <br /> To start, navigate to the &lt;code&gt;sites-available&lt;/code&gt; directory by running &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Then, you can either copy a pre-existing configuration by running &lt;code&gt;sudo cp example.ms subdomain.example.ms&lt;/code&gt; or creating a new file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;. If you copied it, edit the file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;.<br /> <br /> ===What needs to be changed===<br /> The only important things that need to be changed are the &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;server_name&lt;/code&gt; variables. Press &lt;code&gt;i&lt;/code&gt; to start editing the file in Vim, and then find where the variables are located. Change the &lt;code&gt;root&lt;/code&gt; 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 &lt;code&gt;subdomain.example.ms&lt;/code&gt;, we'd create a new folder by running the command &lt;code&gt;sudo mkdir /var/www/example.ms/subdomain&lt;/code&gt;. Then, we'd modify our &lt;code&gt;root&lt;/code&gt; variable to look something like this:&lt;pre&gt;<br /> # before<br /> root /var/www/example.ms;<br /> <br /> # after<br /> root /var/www/example.ms/subdomain;<br /> &lt;/pre&gt;The &lt;code&gt;server_name&lt;/code&gt; variable is just as simple. Just add the subdomain prefix to the beginning of your domain:<br /> # before<br /> server_name example.ms;<br /> <br /> # after<br /> server_name subdomain.example.ms;<br /> Once you've made the proper changes, save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Then, run &lt;code&gt;cd ../sites-enabled &amp;&amp; sudo ln -s /etc/nginx/sites-available/subdomain.example.ms ./&lt;/code&gt; and restart nginx by running &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt;.<br /> <br /> ==Adding other domains (that aren't subdomains)==<br /> The process is exactly the same as adding a subdomain, except instead of adding a prefix the value of &lt;code&gt;server_name&lt;/code&gt; you'll just completely change the domain. Again, don't forget to create the symbolic link to the configuration file and ''especially'' don't forget to restart nginx after saving the config/creating the symbolic link. When you're creating the folder to contain the contents for the server, create a new folder that has the name of the domain. So, for instance, if I was creating example2.ms, I'd run &lt;code&gt;sudo mkdir /var/www/example2.ms&lt;/code&gt;. Now that the domain is ready go to [http://wiki.24pin.tech/index.php?title=WordPress WordPress]if you are planning on using WordPress as your editor.<br /> <br /> == Adding HTTPS to a subdomain with LetsEncrypt (certbot) ==<br /> adsfadsfadfsdfsa<br /> <br /> ==Conclusion==<br /> By now, your nginx server should be up and fully operational. As always, if you're having any issues please STFW before you ask people for advice!<br /> <br /> .<br /> <br /> Thank you,<br /> <br /> - Tyler</div>

Tgriego https://wiki.24pin.tech/index.php?title=Adding_Documentation_to_the_Wiki&diff=907 2019-05-17T20:11:37Z

<p>Tgriego: </p> <hr /> <div>== NOTICE ==<br /> This page is deprecated because of the addition of VisualEditor. If you're a heathen like [[User:Bsanders]] and use Source Editor, this page will help you with that.<br /> <br /> ==Getting the Documentation Ready==<br /> Before you start transferring your documentation over, you'll want to make sure it's written first. Ideally, to keep things clean here, your documentation should be split into sections with formal topic names. For instance, if you were documenting how to make a peanut butter and jelly sandwich, you would want to have something like:<br /> <br /> '''Introduction'''<br /> <br /> [a brief summary of what will be covered in the article]<br /> <br /> '''Preparing the Ingredients'''<br /> <br /> [description of what you need to do to prepare the ingredients]<br /> <br /> '''Acquiring Proper Utensils'''<br /> <br /> [again, just a description of what the proper utensils are (and maybe even ''where'' to get them)]<br /> <br /> '''Making the Sandwich'''<br /> <br /> [you get the idea]<br /> <br /> '''Optional Sides'''<br /> <br /> [...]<br /> <br /> '''Enjoying the Meal'''<br /> <br /> [...]<br /> <br /> <br /> ==Transferring it to the Wiki (the fun part)==<br /> Assuming you've written out your documentation, it's quite easy to transfer over to the wiki. First and foremost, you want to be logged in. In the top right corner (if you're not already logged in) there will be blue text that says &quot;Log in&quot;. Click it, and if you need your credentials just come up to me (Tyler) and ask. After that, find your way to the search bar in the same cozy top right corner as before and search for what you want your article to be titled.<br /> <br /> [[File:Search.png]]<br /> <br /> Hopefully, it will say at the top of the search results &quot;Create the page [title of your page] on this wiki!&quot;. If it doesn't, it will say there is already another page with the same title. Moving on, click the red text that says the title of your page and then paste in your documentation!<br /> <br /> <br /> ==Formatting the Page==<br /> Everyone contributing should aim for consistent and high quality pages. We want this because not only would it make 24PinTech look good, but we can also eventually be established as a credible source for tech related guides/information outside of the city. With that out of the way, here's the good stuff:<br /> <br /> (baited, there's just a little bit more you need to know before continuing)<br /> <br /> What '''not''' to do when formatting/proofreading:<br /> <br /> *paste an unformatted document and publish it<br /> *&lt;nowiki&gt;*use numbered lists for the entire document&lt;/nowiki&gt;<br /> *include broken links<br /> *leave major grammar errors in your writing<br /> *forget to proofread<br /> <br /> ''* = To elaborate: despite numbered lists being straightforward, they look pretty lazy (which we don't want). There are certain exceptions (like when you need to include how to get somewhere, use a certain command/program, et cetera), but just try to avoid using them overall.''<br /> <br /> What '''to''' do when formatting:<br /> <br /> *the contrary of everything above<br /> <br /> ===Actual Text Formatting===<br /> Here's a really summarized version for what you'll need by me:<br /> <br /> *Escape wiki markup: &lt;pre&gt;&lt;nowiki&gt;&lt;nowiki&gt;''no formatting!'' '''''owo'''''&lt;/nowiki&gt;&lt;/nowiki&gt;&lt;/pre&gt;<br /> *New section: &lt;pre&gt;== Section Title ==&lt;/pre&gt;<br /> *New subsection: &lt;pre&gt;(inside of a section) == Subsection Title ==&lt;/pre&gt;<br /> *Bold text: &lt;pre&gt;'''bold!'''&lt;/pre&gt;<br /> *Italic text: &lt;pre&gt;''italics!''&lt;/pre&gt;<br /> *Bold and italic text: &lt;pre&gt;'''''bold and italic!'''''&lt;/pre&gt;<br /> *Bulleted list: &lt;pre&gt;* Start each line with an asterisk, to go deeper start the nextline with 1 more than the previous&lt;/pre&gt;<br /> *Horizontal line: &lt;pre&gt;----&lt;/pre&gt;<br /> *External link: &lt;pre&gt;[https://google.com Google]&lt;/pre&gt; (shows up as [https://google.com Google])<br /> *Internal link: &lt;pre&gt;[[Title of Wiki Article]]&lt;/pre&gt; (shows up as [[Title of Wiki Article]])<br /> <br /> ===Tables===<br /> A brief documentation of creating tables would be impossible due to how broad and detailed you can make them. MediaWiki provides excellent documentation on it which can be found [https://www.mediawiki.org/wiki/Help:Tables here].<br /> <br /> ===Images===<br /> For images, I moved this to a subsection so it can properly be displayed on how to use them. First and foremost, any and all questions you have on embedding images into your wiki posts can be found [https://www.mediawiki.org/wiki/Help:Images here], but below is a brief rundown.<br /> <br /> To begin, start by going to the file upload page ([[Special:Upload]]). Be sure to give it [the file] a name you can remember. For instance, if I were embedding an image of dogs, I would want to go to the upload page ([[Special:Upload]]) and upload the file and name it something like: &lt;pre&gt;dogs.jpg&lt;/pre&gt;<br /> <br /> [[File:Upload example.png]]<br /> <br /> Next, on your page, write &lt;nowiki&gt;[[File:YourFileName.extension]]&lt;/nowiki&gt;. In this example, it would be:<br /> <br /> &lt;pre&gt;[[File:Dogs.jpg]]&lt;/pre&gt;<br /> <br /> Which shows up as:<br /> <br /> [[File:Dogs.jpg]]<br /> <br /> ===Full Documentation===<br /> For MediaWiki's ''full'' documentation of how to format, click [https://www.mediawiki.org/wiki/Help:Formatting here].<br /> <br /> ==Example of a Formatted Article==<br /> If you're still confused on what was covered earlier, an example using the aforementioned analogy with PB&amp;J's is below.<br /> <br /> &lt;pre&gt;<br /> == Introduction ==<br /> If you're unaware, a PB&amp;J (peanut butter and jelly [sandwich]) is a two pieces of bread with peanut butter spread on one side of a slice of bread, and jelly on another piece. It offers protein (varies depending on how much peanut butter you put on it) and also gives 20% of the recommended daily Vitamin E intake.<br /> <br /> For more information on the nutritional benefits of a sandwich, [http://healthyeating.sfgate.com/benefits-peanut-butter-jelly-sandwiches-5553.html click here].<br /> <br /> == Preparing the Ingredients ==<br /> Preparing the ingredients to make a PB&amp;J is quite simple. All you need is 2 slices of bread and a sufficient amount of peanut butter and jelly (or jam) for the bread. If you don't have these ingredients you can either go to a [https://www.google.com/search?q=grocery+stores+near+me nearby grocery store] or shop online from a place like [https://amazon.com/ Amazon].<br /> <br /> == Acquiring Proper Utensils ==<br /> The utensils you will need are as follows:<br /> * 1 Plate<br /> * 1 Butter Knife (or any other knives of your choice)<br /> ** NOTE: A sharp knife is not necessary. In fact, anything that can spread the peanut butter and jelly onto the bread will work just fine.<br /> <br /> You can also get those [https://amazon.com/ online] or from a [https://www.google.com/search?q=grocery+stores+near+me local grocery store].<br /> <br /> == Making the Sandwich ==<br /> === First Step ===<br /> Put the two slices of bread flat on your plate and open both the peanut butter and jelly jars. Take your knife (or other obscure utensil you have decided on using), put it in the peanut butter jar, and get some peanut butter on the utensil. Next, spread it ''evenly'' on one slice of bread, only on one side.<br /> <br /> === Second Step ===<br /> Get the remaining peanut butter off of the utensil either by wiping it onto the other slice of bread or onto a napkin. Once the utensil is clean again, dip it into the jelly/jam jar and repeat the same process onto the other slice of bread.<br /> <br /> == Optional Sides ==<br /> Depending on who you are, you will like different side dishes with your completed PB&amp;J sandwich (if any at all). Some people like chips, others like fruits, and some eat it with spaghetti or other miscellaneous pastas. It entirely depends on who you are, and this is up to you. Looking around your kitchen/house for various foods or edible objects can help inspire you with ideas.<br /> <br /> A link to this example can be found [http://10.21.25.11/wiki/index.php/Making_a_Peanut_Butter_%26_Jelly_Sandwich here].<br /> <br /> == Enjoying the Meal ==<br /> You're finally completed with the extraneous process of making a PB&amp;J! All you have to do now is eat and enjoy it.<br /> &lt;/pre&gt;<br /> <br /> You can find this example here: [[Making a Peanut Butter &amp; Jelly Sandwich]]</div>

Tgriego https://wiki.24pin.tech/index.php?title=WordPress&diff=906 2019-05-16T20:29:09Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. The rest of the instructions are on the page of the web installer. <br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you need to use the admin dashboard. In order to get to it, go to the WordPress installation's root directory and then navigate to the &lt;code&gt;/wp-admin&lt;/code&gt; directory (i.e. website.com/wp-admin). From there, you can edit posts, the theme, pages, plugins, and more. If you don't know how to do something, Google it! The WordPress community has been around since 2003, so your question has most likely been asked and answered before.<br /> <br /> === Logging In ===<br /> In order to log into WordPress, go to website.com'''/wp-admin''' (replace website.com with your domain).<br /> [[File:W1.png|left|frameless|208x208px|screenshot of the login page]]<br /> <br /> [[File:W2.png|left|thumb|150x150px|the ''Users'' tab on the sidebar in the dashboard]]<br /> <br /> === Creating Accounts ===<br /> If you need to create an account, go to '''Users → Add New''' from the WordPress dashboard. From there, fill out all of the information for the new account and press the ''Add New User'' button.<br /> <br /> If you need to edit any of the users (change username, reset password, etc), navigate to '''Users → All Users''' and click on the one that you need to modify.<br /> <br /> === Adding Menu Items ===<br /> Before you can add an item to your primary menu, you need to have a new (or preexisting) page. If you need to create one, go to '''Pages → Add New''' and create it. Once it's created, navigate to '''Appearance → Menus''' and draw your attention to the ''Add Menu Items'' section. Find your new page in the list and click on the checkbox and click ''Add To Menu''.<br /> [[File:W3.png|left|thumb|204x204px|adding an item to the ''Menu structure'' section]]<br /> <br /> === Editing Page Contents ===<br /> lksjdfladsjf<br /> [[File:W4.png|left|thumb|what it should look like when trying to create a dropdown menu]]<br /> <br /> === Adding/Modifying Themes ===<br /> adfadfasdf<br /> <br /> === Uploading Images ===<br /> ldkfjalkdfj<br /> <br /> ==Troubleshooting==<br /> f after an installation you get prompted for FTP credentials, add the following line to the wp-config.php file in the directory that WordPress was installed <br /> define(“FS_METHOD”, “direct”);</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W10.png&diff=905 2019-05-16T20:17:48Z

<p>Tgriego: </p> <hr /> <div>media upload page</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W9.png&diff=904 2019-05-16T20:17:20Z

<p>Tgriego: </p> <hr /> <div>customize page sidebar</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W8.png&diff=903 2019-05-16T20:16:22Z

<p>Tgriego: </p> <hr /> <div>getting to the customization page for a theme</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W7.png&diff=902 2019-05-16T20:15:07Z

<p>Tgriego: </p> <hr /> <div>an example theme in the Themes → Add New section</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W6.png&diff=901 2019-05-16T20:14:46Z

<p>Tgriego: </p> <hr /> <div>screenshot of a post being edited</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W5.png&diff=900 2019-05-16T20:14:17Z

<p>Tgriego: </p> <hr /> <div>screenshot of how to edit pages</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W4.png&diff=899 2019-05-16T20:13:54Z

<p>Tgriego: </p> <hr /> <div>what it should look like when trying to create a dropdown menu</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W3.png&diff=898 2019-05-16T20:13:32Z

<p>Tgriego: </p> <hr /> <div>adding an item to the Menu structure section</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W2.png&diff=897 2019-05-16T20:13:12Z

<p>Tgriego: </p> <hr /> <div>the Users tab on the sidebar in the dashboard</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:W1.png&diff=896 2019-05-16T20:12:24Z

<p>Tgriego: </p> <hr /> <div>screenshot of the login page</div>

Tgriego https://wiki.24pin.tech/index.php?title=Vim&diff=895 2019-05-13T20:26:37Z

<p>Tgriego: Created page with &quot;== About == The splash screen for Vim According to the official Vim website, &quot;Vim is a highly configurable text editor for efficiently creating a...&quot;</p> <hr /> <div>== About ==<br /> [[File:Vim-splash.png|thumb|The splash screen for Vim]]<br /> According to the official Vim website, &quot;Vim is a highly configurable text editor for efficiently creating and changing any kind of text. It is included as &quot;vi&quot; with most UNIX systems and with Apple OS X.&quot;<br /> <br /> == Basic Usage ==<br /> The syntax for Vim is pretty straightforward. You can edit files by running &lt;code&gt;vim filename&lt;/code&gt; 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 &lt;code&gt;i&lt;/code&gt; to start inserting text. After you're finished editing the file, press the escape key and then enter &lt;code&gt;:wq&lt;/code&gt; to save the file. If you need to exit out of the file, press escape and enter &lt;code&gt;:q&lt;/code&gt;, and if you need to exit without saving press escape and type &lt;code&gt;:q!&lt;/code&gt;.<br /> <br /> 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].<br /> <br /> '''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.<br /> <br /> == Common Problems ==<br /> <br /> === Can't open file for writing ===<br /> [[File:Vim-permissions.png|left|frameless]]<br /> <br /> This problem occurs when you don't have permission to write to the file. To fix this, press the escape key and type &lt;code&gt;:q!&lt;/code&gt; to quit without saving. Then, run the same command again but prefixed with &lt;code&gt;sudo&lt;/code&gt;.</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:Vim-splash.png&diff=894 2019-05-13T20:09:34Z

<p>Tgriego: </p> <hr /> <div>the splash screen for vim</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:Vim-permissions.png&diff=893 2019-05-13T20:08:49Z

<p>Tgriego: </p> <hr /> <div>permissions error for vim</div>

Tgriego https://wiki.24pin.tech/index.php?title=WordPress&diff=892 2019-05-13T19:56:33Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. The rest of the instructions are on the page of the web installer. <br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you need to use the admin dashboard. In order to get to it, go to the WordPress installation's root directory and then navigate to the &lt;code&gt;/wp-admin&lt;/code&gt; directory (i.e. website.com/wp-admin). From there, you can edit posts, the theme, pages, plugins, and more. If you don't know how to do something, Google it! The WordPress community has been around since 2003, so your question has most likely been asked and answered before.<br /> <br /> ==Troubleshooting==<br /> If after an installation you get prompted for FTP credentials, add the following line to the wp-config.php file in the directory that WordPress was installed in. <br /> define(“FS_METHOD”, “direct”);</div>

Tgriego https://wiki.24pin.tech/index.php?title=WordPress&diff=843 2019-04-22T20:06:18Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. The rest of the instructions are on the page of the web installer. <br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you use the admin dashboard.<br /> <br /> ==Troubleshooting==<br /> .</div>

Tgriego https://wiki.24pin.tech/index.php?title=MediaWiki:Sidebar&diff=840 2019-02-27T18:31:36Z

<p>Tgriego: </p> <hr /> <div>* navigation<br /> ** mainpage|mainpage-description<br /> ** recentchanges-url|recentchanges<br /> ** helppage|help<br /> <br /> * General<br /> ** Special:AllPages|All Pages<br /> ** Special:NewFiles|All Uploads<br /> ** Special:Contributions|User Contributions<br /> <br /> * Useful Links<br /> ** http://24pin.tech/calendar|Calendar<br /> ** Email_Templates|Email Templates<br /> ** ITop|ITop<br /> ** 24PinTech_Policy|Policy<br /> ** Procedures|Work Order Procedures<br /> ** Spiceworks|Spiceworks</div>

Tgriego https://wiki.24pin.tech/index.php?title=MediaWiki:Sidebar&diff=839 2019-02-27T18:31:15Z

<p>Tgriego: </p> <hr /> <div>* navigation<br /> ** mainpage|mainpage-description<br /> ** recentchanges-url|recentchanges<br /> ** helppage|help<br /> <br /> * General<br /> ** Special:AllPages|All Pages<br /> ** Special:NewFiles|All Uploads<br /> ** Special:Contributions|User Contributions<br /> <br /> * Useful Links<br /> ** Calendar|http://24pin.tech/calendar<br /> ** Email_Templates|Email Templates<br /> ** ITop|ITop<br /> ** 24PinTech_Policy|Policy<br /> ** Procedures|Work Order Procedures<br /> ** Spiceworks|Spiceworks</div>

Tgriego https://wiki.24pin.tech/index.php?title=Email_Templates&diff=817 2019-02-15T15:51:43Z

<p>Tgriego: </p> <hr /> <div>==Things To Keep in Mind==<br /> Please remember to send a courtesy copy of every email '''(CC) to Mr. Chamberlain (bchamberlain@musd20.org) and in addition to your manager's email (currently braydonsanders2001@gmail.com).'''<br /> Remember to remain professional in every email you send, no matter how difficult the customer.<br /> <br /> .<br /> <br /> '''Note:''' Always get permission in written form (usually by email) to take apart a device.<br /> <br /> ==Initial Email==<br /> Opening email sent to the client after their w/o has been processed:&lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I am [your name] from 24PinTech. I am contacting you regarding your [short description of issue].<br /> <br /> We are ready to diagnose your device. You may drop your device off during your lunch or sixth hour in room 120.<br /> <br /> If possible, please provide a description of your issue and also a description of your device. [optional line]<br /> <br /> Respectfully, <br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Reminder Email==<br /> Reminder email sent to the client after not getting a response for at least 3 business days:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I just wanted to follow up with you about your [insert device here]. If you are still interested in doing business with us, please email me back as soon as possible. If I don’t hear back from you within 2 business days, your work order will be closed. <br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Repair Permission Request==<br /> Email sent to the client once you’re ready to start working on their device:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I’m ready to start working on your device. Do I have your permission to disassemble your [insert device here] to [insert action here]?<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Closing a Work Order Due to No Responses==<br /> Sent after 3 business days with no response:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech for your technology needs. We have made several attempts to contact you but did not receive a response. Since we have yet to hear back from you, we must close your work order. If you would like to reopen it, please revisit our website and fill out the support form again. Thank you!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Customer Satisfaction Survey==<br /> Sent after a successfully closed and completed work order:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech to resolve your issue! We greatly appreciate your business and invite you to take a short customer satisfaction survey to evaluate your recent interaction with our team. Our main priority is customer satisfaction, so we would appreciate your input. We use the survey data to evaluate our technicians and improve all future interactions with 24PinTech.<br /> <br /> Your assigned technician was [technician name]. We hope to work with you again!<br /> <br /> OR<br /> <br /> Your assigned technicians were [technician names]. We hope to work with you again!<br /> <br /> <br /> The survey can be found here: http://24pin.tech/survey<br /> <br /> Respectfully, <br /> The 24PinTech Team<br /> &lt;/pre&gt;<br /> <br /> ==Follow-Up==<br /> Sent following 1 week after the work order has been closed:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech! We wanted to check in and see how your device is doing. If it isn’t too much trouble, we have two questions for you:<br /> <br /> Have you found our work satisfactory?<br /> Are there any other issues that have come up?<br /> <br /> Again, everyone at 24PinTech graciously thanks you and appreciates your business and time!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==When Temporarily Closed==<br /> Used when we’re temporarily closed for any reason(s):<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> 24PinTech is currently on a temporary hiatus because of [reason], so we are currently unable to process your request. I will get back to you as soon as we have reopened!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;</div>

Tgriego https://wiki.24pin.tech/index.php?title=User:Tgriego&diff=806 2019-01-31T20:16:08Z

<p>Tgriego: </p> <hr /> <div>website subtext templates:<br /> <br /> 24PinTech is currently closed for training and will re-open within a few weeks. Thank you for understanding and choosing 24PinTech!<br /> <br /> ==Incomplete Pages (aka the Wall of Shame)==<br /> Here's a table of all of the &lt;s&gt;embarrassments&lt;/s&gt; incomplete pages on the wiki. Users in '''bold''' mean that the page needs to be reassigned to someone else.<br /> {| class=&quot;wikitable&quot;<br /> !User<br /> !Page<br /> !Created On (d/m/y)<br /> !Last Edited<br /> !Notes<br /> |-<br /> |amartinez<br /> |[[D-Link Camera Setup]]<br /> |31 July 2018<br /> |31 July 2018<br /> |incomplete and/or missing content<br /> |-<br /> |amartinez<br /> |[[IFIXIT Repair Guides]]<br /> |5 March 2018<br /> |19 March 2018<br /> |incomplete<br /> |-<br /> |bsanders, bchamberlain<br /> |[[Surface USB/PXE]]<br /> |18 April 2018<br /> |24 May 2018<br /> |lackluster and/or vague<br /> |-<br /> |'''bwhitworth'''<br /> |[[Creating bootable drives]]<br /> |28 February 2018<br /> |5 March 2018<br /> |incomplete<br /> |-<br /> |'''dhill'''<br /> |[[How to Audit the Inventory]]<br /> |7 December 2017<br /> |8 December 2017<br /> |lackluster and/or vague + formatting errors<br /> |-<br /> |'''khenderson, sidepanel'''<br /> |[[Technician Workspace]]<br /> |12 February 2018<br /> |3 March 2018<br /> |lackluster + grammatical errors<br /> |-<br /> |'''mdavid'''<br /> |[[SkillsUSA 2018 (Internetworking)]]<br /> |5 April 2018<br /> |5 April 2018<br /> |incomplete<br /> |-<br /> |sidepanel<br /> |[[24PinKiosk]]<br /> |5 September 2018<br /> |6 September 2018<br /> |needs more content (if possible)<br /> |-<br /> |sidepanel<br /> |[[Common Cisco IOS Issues]]<br /> |3 March 2018<br /> |3 March 2018<br /> |incomplete (?) + Cisco Switch IOS Images section needs context<br /> |-<br /> |sgarcia<br /> |[[Router wont save config]]<br /> |14 May 2018<br /> |14 May 2018<br /> |lackluster (seriously)<br /> |-<br /> |&lt;s&gt;tgriego&lt;/s&gt;<br /> |[[Incomplete Pages|&lt;s&gt;Incomplete Pages&lt;/s&gt;]]<br /> |&lt;s&gt;21 September 2018&lt;/s&gt;<br /> |&lt;s&gt;21 September 2018&lt;/s&gt;<br /> |&lt;s&gt;incomplete&lt;/s&gt;<br /> |-<br /> |tgriego<br /> |[[Forum Management]]<br /> |30 July 2018<br /> |2 August 2018<br /> |incomplete<br /> |-<br /> |tgriego<br /> |[[Logan]]<br /> |8 March 2018<br /> |17 May 2018<br /> |incomplete and/or vague<br /> |-<br /> |tgriego<br /> |[[Loki]]<br /> |16 May 2018<br /> |16 May 2018<br /> |incomplete (what?)<br /> |-<br /> |tgriego<br /> |[[WordPress]]<br /> |9 May 2018<br /> |9 May 2018<br /> |incomplete<br /> |-<br /> |'''zkal&lt;bdi&gt;nasy&lt;/bdi&gt;'''<br /> |[[24PinTech Policy]]<br /> |4 May 2018<br /> |31 July 2018<br /> |could use improvement<br /> |}<br /> ==About==<br /> Hi. I'm Tyler and I like full-stack web development and cybersecurity. I also like making things look nice.<br /> to-do list (last updated 29 Nov. 2018)<br /> <br /> '''General'''<br /> <br /> *'''Create a page honoring the previous years technicians'''<br /> **Get the list of students/certs they had<br /> *''Find out how to convince more people to use the forum''<br /> *<br /> *<br /> <br /> '''Wiki'''<br /> <br /> *''Edit the insufficient/lacking articles''<br /> *''Propose edited email templates''<br /> *Extensive Guide to Email Writing<br /> *Good Customer Support Practices</div>

Tgriego https://wiki.24pin.tech/index.php?title=Welcome_to_the_24PinTech_Wiki!&diff=805 2018-12-19T20:14:57Z

<p>Tgriego: </p> <hr /> <div>[[File:Logo-extended.jpg|733x188px|center]]<br /> <br /> __NOTOC__<br /> <br /> ==Who are we?==<br /> The 24PinTech team consists of a group of students all currently attending Maricopa High School. We are all extremely enthusiastic about all things technological based, which prompted us to create the company. The company will allow students to be able to gain experience in Information Technology, thus preparing them for future careers within the technology industry. As part of the training program, employees will be certified in various courses, including but not limited to, the A+ Certificate, CCNA certification and multiple TestOut Course certifications. We also partner with [https://www.azstrut.org/ AZStRUT] to help them repair old computers which will be given back out, giving employees great hands-on hardware repair and software diagnosis experience.<br /> <br /> [https://youtu.be/LWSuHAxm-n8 24PinTech Commercial]<br /> <br /> ==What do we do?==<br /> Computer Service Technicians assets, repair, and maintain computers for companies, businesses, or consumers.<br /> <br /> ==What are our obligations?==<br /> Service Technicians are responsible for installing and repairing internal and external components, implementing proper security settings and programs, installing operating systems and software, making a system’s performance efficient and smooth, and helping customers better understand how to maintain their system(s).<br /> <br /> ==What are our skills?==<br /> <br /> *'''Analytical Skills:''' Computer repair technicians need to be able to solve issues that might not have a clear solution. Being able to experiment and use trial and error is important.<br /> *'''Troubleshooting:''' Computer repair technicians must be able to diagnose, repair and test computer problems as they arise<br /> *'''Communication:''' Computer repair technicians have to ask questions and listen to customers in order to find out the issue, explain the problem in a clear and understandable way, and give them options for repair or replacement.<br /> *'''IT Skills:''' Using diagnostic tools to assess or monitor computer systems requires knowledge of IT skills.<br /> *'''Dexterity:''' Computer repair technicians use their hands to manipulate objects within the computer.<br /> <br /> ==Social Media Stuff!==<br /> <br /> *'''Website:''' [http://24pin.tech/ 24pin.tech]<br /> *'''Twitter:''' [https://twitter.com/ @24PinTech]<br /> *'''Instagram:''' [https://www.instagram.com/24pintech/ @24pintech]</div>

Tgriego https://wiki.24pin.tech/index.php?title=WordPress&diff=804 2018-12-19T16:17:28Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. The rest of the instructions are on the page of the web installer. <br /> <br /> ==Management==<br /> <br /> ==Troubleshooting==<br /> .</div>

Tgriego https://wiki.24pin.tech/index.php?title=WordPress&diff=803 2018-12-18T20:28:57Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. <br /> <br /> ==Management==<br /> <br /> ==Troubleshooting==<br /> .</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:Wp-admin.png&diff=802 2018-12-18T19:56:02Z

<p>Tgriego: </p> <hr /> <div>screenshot of the wordpress dashboard</div>

Tgriego https://wiki.24pin.tech/index.php?title=Email_Templates&diff=801 2018-12-18T19:49:30Z

<p>Tgriego: </p> <hr /> <div>==Things To Keep in Mind==<br /> Please remember to send a courtesy copy of every email '''(CC) to Mr. Chamberlain (bchamberlain@musd20.org) and in addition to your manager's email (currently lucascdial@gmail.com).'''<br /> Remember to remain professional in every email you send, no matter how difficult the customer.<br /> <br /> .<br /> <br /> '''Note:''' Always get permission in written form (usually by email) to take apart a device.<br /> <br /> ==Initial Email==<br /> Opening email sent to the client after their w/o has been processed:&lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I am [your name] from 24PinTech. I am contacting you on behalf of [short description of issue].<br /> <br /> We are ready to diagnose your device. You may drop your device off during your lunch or sixth hour in room 120.<br /> <br /> If possible, please provide a description of your issue and also a description of your device. [optional line]<br /> <br /> Respectfully, <br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Reminder Email==<br /> Reminder email sent to the client after not getting a response for at least 3 business days:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I just wanted to follow up with you about your [insert device here]. If you are still interested in doing business with us, please email me back as soon as possible. If I don’t hear back from you within 2 business days, your work order will be closed. <br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Repair Permission Request==<br /> Email sent to the client once you’re ready to start working on their device:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I’m ready to start working on your device. Do I have your permission to disassemble your [insert device here] to [insert action here]?<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Closing a Work Order Due to No Responses==<br /> Sent after 3 business days with no response:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech for your technology needs. We have made several attempts to contact you but did not receive a response. Since we have yet to hear back from you, we must close your work order. If you would like to reopen it, please revisit our website and fill out the support form again. Thank you!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Customer Satisfaction Survey==<br /> Sent after a successfully closed and completed work order:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech to resolve your issue! We greatly appreciate your business and invite you to take a short customer satisfaction survey to evaluate your recent interaction with our team. Our main priority is customer satisfaction, so we would appreciate your input. We use the survey data to evaluate our technicians and improve all future interactions with 24PinTech.<br /> <br /> Your assigned technician was [technician name]. We hope to work with you again!<br /> <br /> OR<br /> <br /> Your assigned technicians were [technician names]. We hope to work with you again!<br /> <br /> <br /> The survey can be found here: http://24pin.tech/survey<br /> <br /> Respectfully, <br /> The 24PinTech Team<br /> &lt;/pre&gt;<br /> <br /> ==Follow-Up==<br /> Sent following 1 week after the work order has been closed:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech! We wanted to check in and see how your device is doing. If it isn’t too much trouble, we have two questions for you:<br /> <br /> Have you found our work satisfactory?<br /> Are there any other issues that have come up?<br /> <br /> Again, everyone at 24PinTech graciously thanks you and appreciates your business and time!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==When Temporarily Closed==<br /> Used when we’re temporarily closed for any reason(s):<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> 24PinTech is currently on a temporary hiatus because of [reason], so we are currently unable to process your request. I will get back to you as soon as we have reopened!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;</div>

Tgriego https://wiki.24pin.tech/index.php?title=Email_Templates&diff=800 2018-12-18T19:48:39Z

<p>Tgriego: </p> <hr /> <div>==Things To Keep in Mind==<br /> Please remember to send a courtesy copy of every email '''(CC) to Mr. Chamberlain (bchamberlain@musd20.org) and in addition to your manager's email (currently lucascdial@gmail.com).'''<br /> Remember to remain professional in every email you send, no matter how difficult the customer.<br /> <br /> .<br /> <br /> '''Note:''' Always get permission in written form (usually by email) to take apart a device.<br /> <br /> ==Initial Email==<br /> Opening email sent to the client after their w/o has been processed:&lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I am [your name] from 24PinTech. I am contacting you on behalf of [short description of issue].<br /> <br /> We are ready to diagnose your device. You may drop your device off during your lunch or sixth hour in room 120.<br /> <br /> If possible, please provide a description of your issue and also a description of your device. [optional line]<br /> <br /> Respectfully, <br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Reminder Email==<br /> Reminder email sent to the client after not getting a response for at least 3 business days:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I just wanted to follow up with you about your [insert device here]. If you are still interested in doing business with us, please email me back as soon as possible. If I don’t hear back from you within 2 business days, your work order will be closed. <br /> <br /> Respectfully,<br /> [your name]<br /> <br /> &lt;/pre&gt;<br /> <br /> ==Repair Permission Request==<br /> Email sent to the client once you’re ready to start working on their device:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> I’m ready to start working on your device. Do I have your permission to disassemble your [insert device here] to [insert action here]?<br /> <br /> Respectfully,<br /> [your name]<br /> <br /> &lt;/pre&gt;<br /> <br /> ==Closing a Work Order Due to No Responses==<br /> Sent after 3 business days with no response:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech for your technology needs. We have made several attempts to contact you but did not receive a response. Since we have yet to hear back from you, we must close your work order. If you would like to reopen it, please revisit our website and fill out the support form again. Thank you!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==Customer Satisfaction Survey==<br /> Sent after a successfully closed and completed work order:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech to resolve your issue! We greatly appreciate your business and invite you to take a short customer satisfaction survey to evaluate your recent interaction with our team. Our main priority is customer satisfaction, so we would appreciate your input. We use the survey data to evaluate our technicians and improve all future interactions with 24PinTech.<br /> <br /> Your assigned technician was [technician name]. We hope to work with you again!<br /> <br /> OR<br /> <br /> Your assigned technicians were [technician names]. We hope to work with you again!<br /> <br /> <br /> The survey can be found here: http://24pin.tech/survey<br /> <br /> Respectfully, <br /> The 24PinTech Team<br /> &lt;/pre&gt;<br /> <br /> ==Follow-Up==<br /> Sent following 1 week after the work order has been closed:<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> Thank you for choosing 24PinTech! We wanted to check in and see how your device is doing. If it isn’t too much trouble, we have two questions for you:<br /> <br /> Have you found our work satisfactory?<br /> Are there any other issues that have come up?<br /> <br /> Again, everyone at 24PinTech graciously thanks you and appreciates your business and time!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;<br /> <br /> ==When Temporarily Closed==<br /> Used when we’re temporarily closed for any reason(s):<br /> &lt;pre&gt;<br /> Hello [client name]!<br /> <br /> 24PinTech is currently on a temporary hiatus because of [reason], so we are currently unable to process your request. I will get back to you as soon as we have reopened!<br /> <br /> Respectfully,<br /> [your name]<br /> &lt;/pre&gt;</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=799 2018-12-17T16:26:05Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;&lt;nowiki&gt;http://localhost:8000&lt;/nowiki&gt;&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.<br /> <br /> ===HTTP Error 406===<br /> I'm not sure why this happens, but navigate to &lt;code&gt;/etc/mediawiki/parsoid/lib/config&lt;/code&gt; and run &lt;code&gt;sudo vim ParsoidConfig.js&lt;/code&gt; and change the following line from true to false:&lt;pre&gt;<br /> ParsoidConfig.prototype.strictAcceptCheck = false;<br /> &lt;/pre&gt;Alternatively, you can add the following to &lt;code&gt;/etc/mediawiki/parsoid/config.yaml&lt;/code&gt; above the line that reads &lt;code&gt;mwApis:&lt;/code&gt;:<br /> strictAcceptCheck: false<br /> <br /> ===Other===<br /> If you're getting other errors, try doing the following:<br /> <br /> *Restart the Parsoid service (if you've installed Parsoid through aptitude)<br /> **&lt;code&gt;sudo systemctl restart parsoid&lt;/code&gt;<br /> *Check your configuration<br /> **Verify that the uri/api url are correct in &lt;code&gt;config.yaml&lt;/code&gt;<br /> *[[mediawikiwiki:Parsoid/Troubleshooting#Check_that_your_localhost_interwiki_is_set_up_correctly|Make sure that your API url is accessible and functioning properly]]<br /> *Are you using the Parsoid package?<br /> **Try using the [[mediawikiwiki:Parsoid/Developer_Setup|developer build]]<br /> *The other steps found on [[mediawikiwiki:Parsoid/Troubleshooting|this article]]<br /> *</div>

Tgriego https://wiki.24pin.tech/index.php?title=WordPress&diff=798 2018-12-17T16:21:04Z

<p>Tgriego: </p> <hr /> <div>== Introduction ==<br /> <br /> == Installation ==<br /> <br /> == Management ==<br /> <br /> == Troubleshooting ==</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=797 2018-12-17T16:12:55Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;&lt;nowiki&gt;http://localhost:8000&lt;/nowiki&gt;&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.<br /> <br /> ===HTTP Error 406===<br /> I'm not sure why this happens, but navigate to &lt;code&gt;/etc/mediawiki/parsoid/lib/config&lt;/code&gt; and run &lt;code&gt;sudo vim ParsoidConfig.js&lt;/code&gt; and change the following line from true to false:&lt;pre&gt;<br /> ParsoidConfig.prototype.strictAcceptCheck = false;<br /> &lt;/pre&gt;Alternatively, you can add the following to &lt;code&gt;/etc/mediawiki/parsoid/config.yaml&lt;/code&gt; above the line that reads &lt;code&gt;mwApis:&lt;/code&gt;:&lt;pre&gt;<br /> strictAcceptCheck: false<br /> &lt;/pre&gt;<br /> <br /> ===Other===<br /> If you're getting other errors, try doing the following:<br /> <br /> *Restart the Parsoid service (if you've installed Parsoid through aptitude)<br /> **&lt;code&gt;sudo systemctl restart parsoid&lt;/code&gt;<br /> *Check your configuration<br /> **Verify that the uri/api url are correct in &lt;code&gt;config.yaml&lt;/code&gt;<br /> *[[mediawikiwiki:Parsoid/Troubleshooting#Check_that_your_localhost_interwiki_is_set_up_correctly|Make sure that your API url is accessible and functioning properly]]<br /> *Are you using the Parsoid package?<br /> **Try using the [[mediawikiwiki:Parsoid/Developer_Setup|developer build]]<br /> *The other steps found on [[mediawikiwiki:Parsoid/Troubleshooting|this article]]<br /> *</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=796 2018-12-17T16:12:29Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:&lt;pre&gt;<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;http://localhost:8000&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> &lt;/pre&gt;For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.<br /> <br /> ===HTTP Error 406===<br /> I'm not sure why this happens, but navigate to &lt;code&gt;/etc/mediawiki/parsoid/lib/config&lt;/code&gt; and run &lt;code&gt;sudo vim ParsoidConfig.js&lt;/code&gt; and change the following line from true to false:&lt;pre&gt;<br /> ParsoidConfig.prototype.strictAcceptCheck = false;<br /> &lt;/pre&gt;Alternatively, you can add the following to &lt;code&gt;/etc/mediawiki/parsoid/config.yaml&lt;/code&gt; above the line that reads &lt;code&gt;mwApis:&lt;/code&gt;:&lt;pre&gt;<br /> strictAcceptCheck: false<br /> &lt;/pre&gt;<br /> <br /> ===Other===<br /> If you're getting other errors, try doing the following:<br /> <br /> *Restart the Parsoid service (if you've installed Parsoid through aptitude)<br /> **&lt;code&gt;sudo systemctl restart parsoid&lt;/code&gt;<br /> *Check your configuration<br /> **Verify that the uri/api url are correct in &lt;code&gt;config.yaml&lt;/code&gt;<br /> *[[mediawikiwiki:Parsoid/Troubleshooting#Check_that_your_localhost_interwiki_is_set_up_correctly|Make sure that your API url is accessible and functioning properly]]<br /> *Are you using the Parsoid package?<br /> **Try using the [[mediawikiwiki:Parsoid/Developer_Setup|developer build]]<br /> * The other steps found on [[mediawikiwiki:Parsoid/Troubleshooting|this article]]<br /> *</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=795 2018-12-17T16:10:05Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:&lt;pre&gt;<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;http://localhost:8000&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> &lt;/pre&gt;For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.<br /> <br /> ===HTTP Error 406===<br /> I'm not sure why this happens, but navigate to &lt;code&gt;/etc/mediawiki/parsoid/lib/config&lt;/code&gt; and run &lt;code&gt;sudo vim ParsoidConfig.js&lt;/code&gt; and change the following line from true to false:&lt;pre&gt;<br /> ParsoidConfig.prototype.strictAcceptCheck = false;<br /> &lt;/pre&gt;Alternatively, you can add the following to &lt;code&gt;/etc/mediawiki/parsoid/config.yaml&lt;/code&gt; above the line that reads &lt;code&gt;mwApis:&lt;/code&gt;:&lt;pre&gt;<br /> strictAcceptCheck: false<br /> &lt;/pre&gt;<br /> <br /> === Other ===<br /> If you're getting other errors, try doing the following:<br /> <br /> * Restart the Parsoid service (if you've installed Parsoid through aptitude)<br /> ** &lt;code&gt;sudo systemctl restart parsoid&lt;/code&gt;<br /> * Check your configuration<br /> ** Verify that the uri/api url are correct in &lt;code&gt;config.yaml&lt;/code&gt;<br /> *</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=794 2018-12-17T16:06:31Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:&lt;pre&gt;<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;http://localhost:8000&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> &lt;/pre&gt;For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.<br /> <br /> === HTTP Error 406 ===<br /> I'm not sure why this happens, but navigate to &lt;code&gt;/etc/mediawiki/parsoid/lib/config&lt;/code&gt; and run &lt;code&gt;sudo vim ParsoidConfig.js&lt;/code&gt; and change the following line from true to false:&lt;pre&gt;<br /> ParsoidConfig.prototype.strictAcceptCheck = false;<br /> &lt;/pre&gt;Alternatively, you can add the following to &lt;code&gt;/etc/mediawiki/parsoid/config.yaml&lt;/code&gt; above the line that reads &lt;code&gt;mwApis:&lt;/code&gt;:</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=793 2018-12-17T16:02:27Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:&lt;pre&gt;<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;http://localhost:8000&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> &lt;/pre&gt;For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=792 2018-12-17T16:02:07Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:&lt;pre&gt;<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;http://localhost:8000&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> &lt;/pre&gt;For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:&lt;pre&gt;<br /> $wgSessionsInObjectCache = true;<br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;][&quot;forwardCookies&quot;] = true;<br /> &lt;/pre&gt;''Note: Please be aware that there are security implications by sending cookie headers to Parsoid over HTTP.''<br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=791 2018-12-17T15:59:41Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;Modify the value of the uri to properly point to your wiki's API file, and then the domain to match the domain. Make sure that the uri and domain match, so for instance if you use &lt;code&gt;localhost&lt;/code&gt; in the uri, make sure that you use it in the domain as well. Next, you'll want to configure &lt;code&gt;LocalSettings.php&lt;/code&gt; for MediaWiki. Navigate to your wiki's root directory and then run &lt;code&gt;sudo vim LocalSettings.php&lt;/code&gt;. At the bottom, add the following:&lt;pre&gt;<br /> wfLoadExtension(&quot;VisualEditor&quot;);<br /> <br /> $wgDefaultUserOptions[&quot;visualeditor-enable&quot;] = 1;<br /> $wgHiddenPrefs[] = &quot;visualeditor-enable&quot;;<br /> <br /> $wgVirtualRestConfig[&quot;modules&quot;][&quot;parsoid&quot;] = array(<br /> &quot;url&quot; =&gt; &quot;http://localhost:8000&quot;,<br /> &quot;domain&quot; =&gt; &quot;localhost&quot;,<br /> &quot;prefix&quot; =&gt; &quot;localhost&quot;<br /> );<br /> &lt;/pre&gt;For our wiki's configuration, we replaced localhost with the IP on the &lt;code&gt;eth0&lt;/code&gt; interface. This can be checked by running &lt;code&gt;ifconfig eth0&lt;/code&gt;. If you're running a private wiki, add this to the bottom of your configuration as well:<br /> $wgSessionsInObjectCache = true;<br /> <br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]].<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> ===HTTP Error 500===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=790 2018-12-17T15:51:57Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;<br /> <br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2]. You can install it by running &lt;code&gt;sudo npm install pm2 -g&lt;/code&gt;. npm (node package manager) should come pre-installed with node.js and is used to install packages for node.js. Once you've installed PM2, navigate to &lt;code&gt;/etc/mediawiki/parsoid&lt;/code&gt; and run the command &lt;code&gt;sudo pm2 start npm -- start&lt;/code&gt;. This should start an instance of Parsoid in the background, and you can check if it's there by running &lt;code&gt;sudo pm2 list&lt;/code&gt;. <br /> <br /> [[File:Pm2 list.png|left|frameless|851x851px]]<br /> <br /> ==Troubleshooting==<br /> Parsoid can be a pain if it isn't working, so here are a few things that you can try if Parsoid is throwing some errors:<br /> <br /> === HTTP Error 500 ===<br /> This happens when you don't have cURL installed. It can be fixed by running &lt;code&gt;sudo apt-get install php7.2-curl&lt;/code&gt; and then &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt;. If you aren't running PHP 7.2, then change the version number in the packages to accommodate your current configuration.</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:Pm2_list.png&diff=789 2018-12-17T15:46:44Z

<p>Tgriego: </p> <hr /> <div>results from pm2 list</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=788 2018-12-14T20:19:09Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> ==Installation==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> ==Configuration==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;<br /> <br /> ==PM2==<br /> In order to run the developer setup of Parsoid headless and in the background, you'll want to use [https://www.npmjs.com/package/pm2 PM2] <br /> <br /> ==Troubleshooting==</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=787 2018-12-13T16:23:11Z

<p>Tgriego: </p> <hr /> <div>==Introduction==<br /> Parsoid is the back-end for VisualEditor (VE). Essentially, it takes the HTML contents from VE and parses it into wikitext, which is the syntax that MediaWiki uses to display pages. It runs off of node.js and can be installed as a service from a package through &lt;code&gt;apt-get&lt;/code&gt;, but I've only been able to get it to work when using the running developer setup through PM2.<br /> <br /> == Installation ==<br /> This part has already been documented on the MediaWiki website. If you want to install it traditionally, [[mediawikiwiki:Parsoid/Setup|click here]], but if you'd like to install a developer setup, [[mediawikiwiki:Parsoid/Developer_Setup|click here]]. I basically followed the same process for the developer setup, but I'll still document what was completed.<br /> <br /> .<br /> <br /> First, you'll want to install node.js and git by running &lt;code&gt;sudo apt-get install nodejs git&lt;/code&gt;. Verify that it's been installed by running &lt;code&gt;node --version&lt;/code&gt; and then &lt;code&gt;git --version&lt;/code&gt;. Next, create and navigate to &lt;code&gt;/etc/mediawiki/&lt;/code&gt; by running &lt;code&gt;sudo mkdir /etc/mediawiki &amp;&amp; cd /etc/mediawiki&lt;/code&gt;. Once you're ready to pull the contents from the Parsoid git directory, run &lt;code&gt;sudo git clone &lt;nowiki&gt;https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid&lt;/nowiki&gt;&lt;/code&gt; and wait for the download to finish. Move into the newly created &lt;code&gt;parsoid&lt;/code&gt; directory by running &lt;code&gt;cd parsoid&lt;/code&gt;, and then completing the install by running &lt;code&gt;sudo npm install&lt;/code&gt;.<br /> <br /> == Configuration ==<br /> In order to create and then edit the configuration file, run &lt;code&gt;sudo cp config.example.yaml config.yaml &amp;&amp; sudo vim config.yaml&lt;/code&gt;. In there, you'll see something that looks like this:&lt;pre&gt;<br /> mwApis:<br /> - # This is the only required parameter, the URL of you MediaWiki API endpoint.<br /> uri: 'http://localhost/w/api.php'<br /> # The &quot;domain&quot; is used for communication with Visual Editor and RESTBase.<br /> # It defaults to the hostname portion of the `uri` property below, but you can manually set it to an arbitrary string.<br /> domain: 'localhost' # optional<br /> &lt;/pre&gt;<br /> <br /> == PM2 ==<br /> <br /> == Troubleshooting ==</div>

Tgriego https://wiki.24pin.tech/index.php?title=Parsoid_(Deprecated)&diff=786 2018-12-12T15:55:27Z

<p>Tgriego: Created page with &quot;== Introduction == Parsoid is the back-end for VisualEditor, and all it does is take the WikiText (&quot;</p> <hr /> <div>== Introduction ==<br /> Parsoid is the back-end for VisualEditor, and all it does is take the WikiText (</div>

Tgriego https://wiki.24pin.tech/index.php?title=Wiki_Management&diff=785 2018-12-11T16:30:06Z

<p>Tgriego: more</p> <hr /> <div>==Introduction==<br /> Managing the Wiki is pretty straightforward. This article is only for the specific tasks that you might find yourself doing as a webmaster. Anything else that you'd need to do for the Wiki can easily be found on Google, as the MediaWiki foundation has thoroughly documented their everything that you could possibly need to know. Because of this, this page is probably going to end up being pretty short.<br /> <br /> .<br /> <br /> [[File:Create account.png|left|thumb|screenshot of Special:CreateAccount]]<br /> <br /> ==Creating Users==<br /> To create an account, go to the [[Special:CreateAccount|Create account]] page listed under [[Special:SpecialPages|Special Pages]]. If the page doesn't show, it's because your account does not have the proper role (bureaucrat). Refer to the next section to learn how to do this.<br /> <br /> .<br /> <br /> When you're creating an account, make sure that you check &lt;code&gt;Use a temporary random password and send it to the specified email address&lt;/code&gt;. This lets the user set their own password without having to do it at your workstation, and they also are entering their email address in so that in the event that they forget their password they can reset it. If you're not using the &lt;code&gt;first initial + last name&lt;/code&gt; format for usernames, putting their real name in the &lt;code&gt;Real name&lt;/code&gt; field is a good idea.<br /> [[File:User rights.png|thumb|screenshot of Special:UserRights]]<br /> <br /> ==Assigning Roles==<br /> Just like creating an account, assigning roles is also easy. Navigate to the [[Special:UserRights|User rights]] page, enter a username, and assign the roles that you'd like that person to have. This will not work if your account doesn't have the bureaucrat role.</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:User_rights.png&diff=784 2018-12-11T16:27:38Z

<p>Tgriego: </p> <hr /> <div>Special:UserRights</div>

Tgriego https://wiki.24pin.tech/index.php?title=Wiki_Management&diff=783 2018-12-11T16:25:29Z

<p>Tgriego: more</p> <hr /> <div>== Introduction ==<br /> Managing the Wiki is pretty straightforward. This article is only for the specific tasks that you might find yourself doing as a webmaster. Anything else that you'd need to do for the Wiki can easily be found on Google, as the MediaWiki foundation has thoroughly documented their everything that you could possibly need to know. Because of this, this page is probably going to end up being pretty short.<br /> <br /> [[File:Create account.png|left|thumb]]<br /> <br /> == Creating Users ==<br /> To create an account, go to the [[Special:CreateAccount|&quot;Create account&quot;]] page listed under [[Special:SpecialPages|Special Pages]]. If the page doesn't show, it's because your account does not have the proper role (bureaucrat). Refer to the next section to learn how to do this.<br /> <br /> When you're creating an account, make sure that you check &lt;code&gt;Use a temporary random password and send it to the specified email address&lt;/code&gt;. This lets the user set their own password without having to do it at your workstation, and they also are entering their email address in so that in the event that they forget their password they can reset it. If you're not using the &lt;code&gt;first initial + last name&lt;/code&gt; format for usernames, putting their real name in the &lt;code&gt;Real name&lt;/code&gt; field is a good idea.<br /> <br /> == Assigning Roles ==<br /> a</div>

Tgriego https://wiki.24pin.tech/index.php?title=File:Create_account.png&diff=782 2018-12-11T16:22:39Z

<p>Tgriego: </p> <hr /> <div>Special:CreateAccount</div>

Tgriego https://wiki.24pin.tech/index.php?title=Logan_(Retired)&diff=780 2018-12-07T16:10:06Z

<p>Tgriego: </p> <hr /> <div>== General Overview ==<br /> Logan (10.21.25.11) 1 out of 2 of the Dell PowerEdge R430's that we have in Mr. Chamberlain's room. It primarily functions as a print server, BDC (backup domain controller, a host for our DHCP/DNS backups, and a WAMP (Apache) server.<br /> <br /> == Startup ==<br /> There is currently only 1 file in the startup folder which is a visual basic script to start up the Parsoid server. The code for that can be seen as follows:&lt;pre&gt;<br /> set w = CreateObject(&quot;WScript.Shell&quot;)<br /> w.Run chr(34) &amp; &quot;C:\Program Files\nodejs\parsoid\parsoid.bat&quot; &amp; chr(34), 0<br /> set w = Nothing<br /> &lt;/pre&gt;<br /> <br /> == Print Services ==<br /> There are currently 2 active print servers on Logan: one for the &lt;code&gt;Brother HL-4570CDW&lt;/code&gt; printer, and one for the &lt;code&gt;HP LaserJet P4014 UPD PCL 6&lt;/code&gt; printer.<br /> <br /> [[File:Logan_PrintAllPrinters.png]]<br /> <br /> Below is the advanced configuration page for both of the main printers.<br /> <br /> [[File:Printers-advanced_logan.png|frameless|600x600px]]<br /> == Backup Domain Controller ==<br /> Logan is also a backup domain controller for Loki. Its current production configuration can be seen below.<br /> <br /> [[File:Logan_ForwardLookupZones.png]]<br /> <br /> ==WAMP Stack (Apache Server) ==<br /> Everything you need to know about our web server can be found on the [http://wiki.24pin.tech/index.php/Apache Apache] page. It covers everything ranging from installation to configuration, and covers the basics to troubleshooting.<br /> <br /> == DHCP ==<br /> Logan runs as a backup DHCP server. The configuration for it can be seen below:<br /> <br /> == DNS ==<br /> aa<br /> <br /> == IDRAC ==</div>

Tgriego https://wiki.24pin.tech/index.php?title=User:Mdavid&diff=778 2018-12-03T05:52:05Z

<p>Tgriego: sorry bud, &quot;24 Pin Tech&quot; bothered me + it said all of your contractions had typos but they didn't? anyways fixed it. miss ya marquell</p> <hr /> <div>='''End of the Year Summary 2017-2018'''=<br /> ==Introduction==<br /> From the perspective of a student, this class was really interesting and really worth the experience. This was my first year in both Computer Maintenance and 24PinTech, and I truly enjoyed it. I joined the business blind and not sure what to expect. In fact, I originally registered for Networking II, but there were very few of us to make it an official class. As such, I was randomly placed into Computer Maintenance. Hardware has never been my specialty, so I was very hesitant about how I can contribute to 24PinTech in the first place. I wasn't sure how my networking skills would apply to the business, so I aimed to learn more about hardware in order to be useful. However, I’m glad that I was given the opportunity to work towards certifications through the TestOut program, in which I have obtained Switching Pro during the time in which this summary was written.<br /> <br /> ==My Role in 24PinTech==<br /> Going into 24PinTech, I was nothing more than a help desk employee. Reece Thompson took the manager at the time and he did of course train me as far as procedures and Spiceworks goes. In the beginning, I wasn't sure how I would be useful in which I feared. Unlike everyone else, I didn't have a background in technology, until I joined ITE my sophomore year. As such, my skills were quite slim and were limited to networking and some aspects of software. I already knew that a majority of the work orders that would come in would be related to hardware; I was never really good with using tools and fixing screens.<br /> <br /> From August to mid-September, my role as an employee was almost worthless, as I have yet to acquire the skills I need. However, I still took the time to do research and learn how to do certain things. As such, spent my lunch hour in the classroom in addition to my TA hour. Customers would come during the lunch hours, and since Reece trained me how to use Spiceworks, I ended up being the receiving employee and had them sign their contracts whenever he wasn't here himself. At the time, I didn't have admin rights and couldn't assign work orders, but I did attach post-it notes to the received devices with the customers name, the device, when it came in, and the customer’s contact info. Both Reece and Mr. Chamberlain took note of this one day. Reece thought that I was a lot more organized while he himself was more of a worker, and Mr. Chamberlain agreed as well. I was called aside around mid-September, and both asked me if I would like to take Reece’s spot as manager. I was of course warned about all the responsibilities I will have, in which I honorably accepted. I became the head manager, with Reece and Andres Martinez as my assistant managers.<br /> <br /> As a manager, I improved our procedures and really organized 24PinTech’s infrastructure. In my opinion, 24PinTech at the beginning of the school year really needed more “balance” in addition to more procedures and organization- that was my goal. I made sure procedures were being followed in addition to assigning work orders and conducting meetings. I also did loads of documentation throughout the school year that future and employees and managers can make reference to and hopefully improve.<br /> <br /> Being able to contribute as a manager of 24PinTech meant a lot to me, especially as a new member of the 24PinTech team. What was the most meaningful to me was that I was useful for once, and that I was able to develop myself as a leader.<br /> <br /> ==My Accomplishments==<br /> Although I didn't accomplish much as far as work orders go, I do think accomplished great things as 24PinTech's manager. I think I did a great job documenting and taking note of everything I've encountered in the business. One thing that the employees might not know is that I frequently envision 24PinTech's future. As such, I frequently update our email templates, inventory, and procedures. My documentation is quite extensive in terms of the business itself and how it functions. Organization, in my opinion, is a huge improvement to 24PinTech in which I am glad to have influenced.<br /> <br /> ==What I Learned==<br /> In general, I learned how to be a leader. Being an introvert in the first place, is quite challenging. However through 24PinTech, i gained more leadership skills and developed better communication skills. I also think that the business really opened my eyes to what I should expect in my future career. This business is a simulation and the real thing at the same time, and I'm glad that I learned everything I need to know in order to be a good employee. Being a manager really made me think. It's not at all an easy job, as my fellow employees might think. I learned how to manage in general which is something that I wasn't the best at in the past. it's stressful Overall, I learned what a business is all about. It's more than just business. I learned from Mr. Chamberlain that a business is all about the mission in which the employees must aim to accomplish. Although I am more independent than others, I learned how to work a team - I learned how to ask for help when I needed it, and I learned how to understand my fellow employees' strengths and weaknesses.<br /> <br /> ==Improvements as an Employee and Manager==<br /> I feel like I was a bit too nice of a manager. I think I went a bit too easy on employees, and I feel like I could have disciplined them a little more. Although we got work orders done, I do feel like we got distracted every now and then. I put the blame on myself for not taking action like I was supposed to. I do feel like we could have gotten more work done. <br /> <br /> ==Conclusion==<br /> I hope that future employees such as I find ways to contribute to the business in their own way. 24PinTech is still at its early stages, and I’m glad I got to be a part of the best team that made the most impact on the business. This business is still growing, and although I made some contributions to the business, I expect future managers and employees to do even more. I envision expansion. I’m glad the business really prepared me for the real world, as it served a simulation of an IT business. I do think I more prepared for the future because of 24PinTech</div>

Tgriego