The TinkerNet Wiki - User contributions [en-gb]

IoT - Modular - Buttons.h

2021-08-02T05:28:55Z

Grant:

'''Use case code at end of file. Submitted by somebody that probably shouldn't be coding so fix it if it's borked...'''

<syntaxhighlight lang="cpp" line="1">

class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

</syntaxhighlight>

<syntaxhighlight lang="cpp" line="1">

/***********************************************************************************************************************
Code Suggestion:
// I/O - Setup the I/O PINS HERE
PushButton BTN1_TRIGGER = { 23 };// Creates PushButton instance for buttons.h class to work with
PushButton BTN2_TRIGGER = { 14 }; //Etc...
PushButton BTN3_TRIGGER = { 21 }; //Etc...
PushButton BTN4_TRIGGER = { 19 }; //Etc...
PushButton BTN5_TRIGGER = { 18 }; //Etc...
PushButton BTN6_TRIGGER = { 17 }; //Etc...
//These are initialized as part of the class and don't require initialization in 'void setup{}'

void loop{};
uint16_t button_function = button_0;

if (BTN1_TRIGGER.isPressed()) {
button_function = button_1;
}
else if (BTN2_TRIGGER.isPressed()) {
button_function = button_2;
}
else if (BTN3_TRIGGER.isPressed()) {
button_function = button_3;
}
else if (BTN4_TRIGGER.isPressed()) {
button_function = button_4;
}
else if (BTN5_TRIGGER.isPressed()) {
button_function = button_5;
}
else if (BTN6_TRIGGER.isPressed()) {
button_function = button_6;
}

switch (button_function) {
default:
case button_0:
case button_1:
//Do something
break;
case button_2:
// Do something else
break;
case button_3:
// Doing something totally different
break;
case button_4:
// Wish I could do something
break;
case button_5:
// Stop doing that, please for the love of all that is holy!
break;
case button_6:
// Never mind... I will do this instead
break;

}
*/
</syntaxhighlight>

IoT - Modular - Buttons.h

2021-08-02T05:28:05Z

Grant:

//Use case code at end of file
//Submitted by somebody that probably shouldn't be coding so fix it if it's borked...

<syntaxhighlight lang="cpp" line="1">

class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

</syntaxhighlight>

<syntaxhighlight lang="cpp" line="1">

/***********************************************************************************************************************
Code Suggestion:
// I/O - Setup the I/O PINS HERE
PushButton BTN1_TRIGGER = { 23 };// Creates PushButton instance for buttons.h class to work with
PushButton BTN2_TRIGGER = { 14 }; //Etc...
PushButton BTN3_TRIGGER = { 21 }; //Etc...
PushButton BTN4_TRIGGER = { 19 }; //Etc...
PushButton BTN5_TRIGGER = { 18 }; //Etc...
PushButton BTN6_TRIGGER = { 17 }; //Etc...
//These are initialized as part of the class and don't require initialization in 'void setup{}'

void loop{};
uint16_t button_function = button_0;

if (BTN1_TRIGGER.isPressed()) {
button_function = button_1;
}
else if (BTN2_TRIGGER.isPressed()) {
button_function = button_2;
}
else if (BTN3_TRIGGER.isPressed()) {
button_function = button_3;
}
else if (BTN4_TRIGGER.isPressed()) {
button_function = button_4;
}
else if (BTN5_TRIGGER.isPressed()) {
button_function = button_5;
}
else if (BTN6_TRIGGER.isPressed()) {
button_function = button_6;
}

switch (button_function) {
default:
case button_0:
case button_1:
//Do something
break;
case button_2:
// Do something else
break;
case button_3:
// Doing something totally different
break;
case button_4:
// Wish I could do something
break;
case button_5:
// Stop doing that, please for the love of all that is holy!
break;
case button_6:
// Never mind... I will do this instead
break;

}
*/
</syntaxhighlight>

IoT - Modular - Buttons.h

2021-08-02T05:26:32Z

Grant:

//Use case code at end of file
//Submitted by somebody that probably shouldn't be coding so fix it if it's borked...

<syntaxhighlight lang="cpp" line="1">

class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

</syntaxhighlight>

//***********************************************************************************************************************
Code Suggestion:
// I/O - Setup the I/O PINS HERE
PushButton BTN1_TRIGGER = { 23 };// Creates PushButton instance for buttons.h class to work with
PushButton BTN2_TRIGGER = { 14 }; //Etc...
PushButton BTN3_TRIGGER = { 21 }; //Etc...
PushButton BTN4_TRIGGER = { 19 }; //Etc...
PushButton BTN5_TRIGGER = { 18 }; //Etc...
PushButton BTN6_TRIGGER = { 17 }; //Etc...
//These are initialized as part of the class and don't require initialization in 'void setup{}'

void loop{};
uint16_t button_function = button_0;

if (BTN1_TRIGGER.isPressed()) {
button_function = button_1;
}
else if (BTN2_TRIGGER.isPressed()) {
button_function = button_2;
}
else if (BTN3_TRIGGER.isPressed()) {
button_function = button_3;
}
else if (BTN4_TRIGGER.isPressed()) {
button_function = button_4;
}
else if (BTN5_TRIGGER.isPressed()) {
button_function = button_5;
}
else if (BTN6_TRIGGER.isPressed()) {
button_function = button_6;
}

switch (button_function) {
default:
case button_0:
case button_1:
//Do something
break;
case button_2:
// Do something else
break;
case button_3:
// Doing something totally different
break;
case button_4:
// Wish I could do something
break;
case button_5:
// Stop doing that, please for the love of all that is holy!
break;
case button_6:
// Never mind... I will do this instead
break;

}

IoT - Modular - Buttons.h

2021-08-02T05:02:59Z

Grant:

<syntaxhighlight lang="cpp" line="1">

class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

</syntaxhighlight>

IoT - Modular - Buttons.h

2021-08-02T05:02:34Z

Grant:

<syntaxhighlight lang="cpp" line="1">

class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

<nowiki>:</nowiki> pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

</syntaxhighlight>

IoT - Modular - Buttons.h

2021-08-02T05:01:51Z

Grant:

IoT - Modular - Buttons.h

2021-08-02T05:01:25Z

Grant:

<syntaxhighlight lang="cpp" line="1">
class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

<nowiki>:</nowiki> pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

//
<syntaxhighlight>

IoT - Modular - Buttons.h

2021-08-02T04:59:45Z

Grant: Created page with "class PushButton { public: PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created) <nowiki>:</nowiki> pin(pin) { // remember the push button p..."

class PushButton {

public:

PushButton(uint8_t pin) // Constructor (executes when a PushButton object is created)

<nowiki>:</nowiki> pin(pin) { // remember the push button pin

pinMode(pin, INPUT_PULLUP); // enable the internal pull-up resistor

};

bool isPressed() // read the button state check if the button has been pressed, debounce the button as well

{

bool pressed = false;

bool state = digitalRead(pin); // read the button's state

int8_t stateChange = state - previousState; // calculate the state change since last time

if (stateChange == rising) { // If the button is pressed (went from high to low)

if (millis() - previousBounceTime > debounceTime) { // check if the time since the last bounce is higher than the threshold

pressed = true; // the button is pressed

}

}

if (stateChange == falling) { // if the button is released or bounces

previousBounceTime = millis(); // remember when this happened

}

previousState = state; // remember the current state

return pressed; // return true if the button was pressed and didn't bounce

};

private:

uint8_t pin;

bool previousState = HIGH;

unsigned long previousBounceTime = 0;

const static unsigned long debounceTime = 1000;

const static int8_t rising = HIGH - LOW;

const static int8_t falling = LOW - HIGH;

};

//

WikiServer - Install EVEN NEWER

2021-05-30T06:30:08Z

Grant:

'''NEW Version!'''

'''Now with more VirtualHosts...'''

'''And an attempt at running a Development release'''

*Proven on Mint 20 ... (Gets MySQL 8.0)
*Proven on SparkyLinux 5.11 ... (You'll have to [https://tecadmin.net/install-mysql-server-on-debian9-stretch/ fix the missing MySQL] thing & install vim first)
**[[Getting MySQL onto SparkyLinux|Getting MySQL onto SparkyLinux]]
*Proven on LMDE 4 ... (You'll have to [https://linuxize.com/post/how-to-install-mysql-on-debian-10/ fix the missing MySQL] thing & install vim first)

===Install the LAMP Stack===

[[WebServer - Basic LAMP Stack Install|Basic LAMP Stack Install]]

===Install MediaWiki===

*<code>wget <nowiki>https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.1.tar.gz</nowiki></code>
**(Check the '''[[mediawikiwiki:Download|download page]]''' for latest version)
*<code>tar -xvzf mediawiki-1.35.0-rc.1.tar.gz</code>
**(adjust for version...)
*<code>sudo mkdir /var/www/wiki</code>
*<code>sudo mkdir /var/www/labnotes</code>
*<code>sudo cp -r mediawiki-1.35.0-rc.1/* /var/www/wiki</code>
*<code>sudo cp -r mediawiki-1.35.0-rc.1/* /var/www/labnotes</code>
*<code>sudo mysql -u root -p</code>

CREATE DATABASE my_wiki;
GRANT ALL PRIVILEGES ON my_wiki.* TO 'someone'@'localhost';
FLUSH PRIVILEGES;
CREATE DATABASE my_notes;
GRANT ALL PRIVILEGES ON my_notes.* TO 'someone'@'localhost';
FLUSH PRIVILEGES;
EXIT;

*<code>sudo vim /etc/php/7.4/apache2/php.ini</code>
**(this may be in a slightly different location depending on version of php installed...)
**increase <code>upload_max_filesize</code> to 200M
**increase <code>post_max_size</code> to 200M
*Fix upload directories:
**<code>sudo chmod -R ugo+rwX /var/www/wiki/images</code>
**<code>sudo chmod -R ugo+rwX /var/www/labnotes/images</code>

Configure your webserver with [[WebServer - Name-based Virtual Host Support|VirtualHosts]] for the Wiki & LabNotes

*Wiki
**<code>ServerName WikiServer.Domain.TLD</code>
**<code>DocumentRoot "/var/www/wiki"</code>
*LabNotes
**<code>ServerName LabNotesServer.Domain.TLD</code>
**<code>DocumentRoot "/var/www/labnotes"</code>

Browse to '''<nowiki>http://WikiServer.Domain.TLD/</nowiki>''' & follow the steps presented.

Set it as '''Authorised editors only'''.

Browse to '''<nowiki>http://LabNotesServer.Domain.TLD/</nowiki>''' & follow the steps presented.

Set as '''Private Wiki'''

===Adding another Wiki to an existing Wiki Server===

*<code>sudo mkdir /var/www/anudderwiki</code>
*<code>sudo cp -r mediawiki-*/* /var/www/anudderwiki</code>
*<code>sudo mysql -u root -p</code>
**<code>CREATE DATABASE anudder_wiki;</code>
**<code>GRANT ALL PRIVILEGES ON anudder_wiki.* TO 'someone'@'localhost';</code>
**<code>FLUSH PRIVILEGES;</code>
**<code>EXIT;</code>
*<code>sudo chmod -R ugo+rwX /var/www/anudderwiki/images</code>

Configure your webserver with VirtualHosts for the new Wiki

*<code>ServerName AnudderWikiServer.Domain.TLD</code>
*<code>DocumentRoot "/var/www/anudderwiki"</code>

Browse to '''<nowiki>http://AnudderWikiServer.Domain.TLD/</nowiki>''' & follow the steps presented.

Set as '''Authorised editors only''' or '''Private Wiki'''

===Troubleshooting===
'''Note:''' With MySQL 8, there is some possibility that it will default to the wrong authentication method.

*If Mediawiki has problems connecting & gives you "'''The server requested authentication method unknown to the client.'''" as part of the error message, sign back into MySQL & adjust the user being assigned in the wiki install:
**<code>sudo mysql -u root -p</code>
**<code>ALTER USER 'someone'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';</code>

WebServer - Basic LAMP Stack Install

2021-01-31T03:19:29Z

Grant: Undo revision 1423 by Grant (talk)

*Proven on Mint 19.3 ... (Seems to get MySQL 5.7)
*Proven on Mint 20 ... (Gets MySQL 8.0)
*Proven on SparkyLinux 5.11 ... (You'll have to [https://tecadmin.net/install-mysql-server-on-debian9-stretch/ fix the missing MySQL] thing & install vim first)
**[[Getting MySQL onto SparkyLinux]]

===Install the LAMP Stack===
'''Note:''' On Mint 19.3, this installs php 7.2.24. On Mint 20, this installs php 7.4.3. This ''MIGHT'' be an important point to keep in mind for later...

If you expect to need php newer than 7.2.24 on a Mint 19.3 server, force it to upgrade before you move on to installing the packages:

*<code>sudo add-apt-repository ppa:ondrej/php # Press enter to confirm.</code>
*<code>sudo apt update</code>
*<code>sudo apt upgrade</code>
*<code>php -v</code>

(Verify that it's showing a suitable version of php. I'm seeing 7.4.10 in testing...)

====Install the packages====

*<code>sudo apt install apache2 libapache2-mod-php php-xml php-mbstring php-apcu php-intl imagemagick inkscape php-gd php-cli php-cgi php mysql-server mysql-client php-mysql</code>
**Say Yes to Continue
**Configuring mysql-community-server (Doesn't happen on Mint)
***Pick a good '''root''' password...
***I tend to select '''Use Legacy Authentication Method''' because '''Use Strong Password Encryption''' is annoying as hell. (Your choice here...)

====Configure MySQL====

*<code>sudo mysql_secure_installation</code>
**Would you like to setup VALIDATE PASSWORD component?
***I select No (because I'd rather manage my own password policies, thanks...)
**'''''root password'''''
***Please set the password for root here.
****Pick a good '''root''' password...
**or... (depends on install...)
***Using existing password for root.
****Say No
**Remove anonymous users?
***Duh... Yes
**Disallow root login remotely?
***Your choice, but I tend to say No.
**Remove test database and access to it?
***Duh... Yes again.
**Reload privilege tables now?
***Yes
*([[WebServer - MySQL Notes|Extra Instructions if you've never configured MySQL before]])

====& Test it====

*<code>sudo vi /var/www/html/info.php</code>

<?php
phpinfo();
?>
Browse to http://ServerAddress/ & you should see the default page.

Browse to [http://ServerAddress/ http://ServerAddress/info.php] & you should see a whole bunch of info about your PHP subsystem.

====Set up at least one user in mysql====

*<code>sudo mysql -u root -p</code>

CREATE USER 'someone'@'localhost' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;
EXIT;
('''Hint:''' This'd be a good time to create yourself as that user with your non-admin password of choice...)

WebServer - Basic LAMP Stack Install

2021-01-31T03:18:26Z

Grant: /* Install the packages */

This part stolen fair and square from Tinkernet Wiki... https://wiki.tinkernet.ca

*Proven on Mint 19.3 ... (Seems to get MySQL 5.7)
*Proven on Mint 20 ... (Gets MySQL 8.0)

===Install the LAMP Stack===
====Install the packages====

*<code>sudo apt install apache2 libapache2-mod-php php-xml php-mbstring php-apcu php-intl imagemagick inkscape php-gd php-cli php-cgi php mysql-server mysql-client php-mysql</code>
**Say Yes to Continue

====Configure MySQL====

*<code>sudo mysql_secure_installation</code>
**Would you like to setup VALIDATE PASSWORD component?
***I select No (because I'd rather manage my own password policies, thanks...)
**'''''root password'''''
***Please set the password for root here.
****Pick a good '''root''' password...
**or... (depends on install...)
***Using existing password for root.
****Say No
**Remove anonymous users?
***Duh... Yes
**Disallow root login remotely?
***Your choice, but I tend to say No.
**Remove test database and access to it?
***Duh... Yes again.
**Reload privilege tables now?
***Yes

====& Test it====

*<code>sudo vi /var/www/html/info.php</code>

<?php
phpinfo();
?>
Browse to http://ServerAddress/ & you should see the default page.

Browse to [http://ServerAddress/ http://ServerAddress/info.php] & you should see a whole bunch of info about your PHP subsystem.

====Set up at least one user in mysql====

*<code>sudo mysql -u root -p</code>

CREATE USER 'someone'@'localhost' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;
EXIT;
('''Hint:''' This'd be a good time to create yourself as that user with your non-admin password of choice...)

Now. go back to the list... [[WEB_SERVER_FROM_A_TO_Z]]

MQTT Bridging

2021-01-25T01:44:34Z

Grant: /* Bridged MQTT Setup */

==Bridged MQTT Setup==

==='''Prerequisites''' -> [[http://wingsquare.com/blog/setting-up-mqtt-mosquitto-broker-in-ubuntu-linux/|Installing Mosquitto Broker]] .===
Submitted by Guru of Nothing

If you are using MQTT for your automation backbone, you may need to have more than one MQTT broker. In my case, I have a main broker that the majority of my devices connect to in the local network (Skynet, a VM on an enterprise server locally) and I have a secondary broker (PiBridge, an rPi) that is located in the node cabinet at my gate. There are a number of devices at the gate that are critical and if the power goes out to the property, these are powered by 12v battery. Skynet will go down and the gate devices MUST have a broker. So a bridged setup is vital. I installed a Lite version of Raspi OS (previously called Raspbian) on a rPi 3b+ and enabled SSH. I then installed Mosquitto. The rPi is powered from the battery that all the other devices there use for backup power.

The basic bridge is pretty simple. There are lots of options for this and it gets pretty complicated rather quickly. Take a trip over to [http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's place] if you want more info and additional options and use cases. I am sticking with a simple relay between the two. At the most basic, you need to set up ONE (and only one) of your brokers to be the bridge. For this 'relay' connection DO NOT do the following to both or you will create a messaging loop that will bork both of your brokers and make your devices want to commit suicide. Let's set up the bridge. These are Linux instructions, though the Windblows instructions are the same.

===Setup===
Find the location of your mosquitto.conf file in the primary broker. In my case its in the /etc/mosquitto folder. Use whatever editor applies to your tastes, but I like vim. You must have admin access to modify this file
sudo vim /etc/mosquitto/mosquitto.conf
In the file you will need to add the lines that create a bridge. Add in the following:

#External MQTT Broker
allow_anonymous true
connection <your_second_broker_name>
address other_broker_IP:1883
topic # out 0
topic # in 0

Save the file and restart your broker (More than likely by restarting the computer in Windblows)

sudo service mosquitto restart

Important Notes #

*<code>'allow anonymous true'</code> is required if you '''DON'T''' use name and password for your broker communications. Additional lines are required if you '''DO''' use authentication.
*Replace <code><your_second_broker_name></code> with whatever you want your other broker named internally. You must have this line but you can call it anything you'd like. I use DNS in my network so I named the same as the devices hostname.
*Replace <code>other_broker_IP</code> with the IP (or name if you have DNS set up in your network) of your second broker. If you use non-default or secured port numbers, change 1883 to the correct number of your broker
*The topic in and out lines tell the broker to subscribe to every message broadcast from the second broker and to broadcast out every message received directly on the first TO the second. This is why you don't want to do this to BOTH brokers. They will sub and publish to each other until their little brains fall out. Besides, it angers the IT folks in the matrix... just saying.
*BONUS NOTE: If you want to restrict what is sent between them, i.e. to not send STAT messages back and forth, you can change the '#' to specific topic and only that one will be rebroadcast... Refer to [http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's tutorial] for more of that mind numbing configuration.

===Testing===
To make sure that you have it set up correctly, use your visual client of choice (I use [http://workswithweb.com/html/mqttbox/downloads.html MQTT Box]) and open two instances. One needs to be connected to each of the brokers. Pick a topic and sub to it in each window... let's use 'broker/testing' for giggles. Then open a publish screen in both windows. Publish the payload "Hello World" to 'broker/testing' topic on one and make sure that in your sub screen "Hello World" shows up on BOTH brokers sub screens. If it does, good. If not, you did something wrong (like probably not restarting the broker you made the .conf file mods to). This tests that you have communication in one direction, broker to broker. Now, publish the same message to the same topic in your other window and make sure the message shows up in the subscribe screens of both brokers. This tests communications going the other way. Worked? Great! No? You need to troubleshoot...

MQTT Bridging

2021-01-25T01:36:23Z

Grant: /* Bridged MQTT Setup */

==Bridged MQTT Setup==

==='''Prerequisites''' -> [[http://wingsquare.com/blog/setting-up-mqtt-mosquitto-broker-in-ubuntu-linux/|Installing Mosquitto Broker]] .===
Submitted by Guru of Nothing

If you are using MQTT for your automation backbone, you may need to have more than one MQTT broker. In my case, I have a main broker that the majority of my devices connect to in the local network (Skynet, a VM on an enterprise server locally) and I have a secondary broker (PiBridge, an rPi) that is located in the node cabinet at my gate. There are a number of devices at the gate that are critical and if the power goes out to the property, these are powered by 12v battery. Skynet will go down and the gate devices MUST have a broker. So a bridged setup is vital. I installed a Lite version of Raspi OS (previously called Raspbian) on a rPi 3b+ and enabled SSH. I then installed Mosquitto. The rPi is powered from the battery that all the other devices there use for backup power.

The basic bridge is pretty simple. There are lots of options for this and it gets pretty complicated rather quickly. Take a trip over to [http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's place] if you want more info and additional options and use cases. I am sticking with a simple relay between the two. At the most basic, you need to set up ONE (and only one) of your brokers to be the bridge. For this 'relay' connection DO NOT do the following to both or you will create a messaging loop that will bork both of your brokers and make your devices want to commit suicide. Let's set up the bridge. These are Linux instructions, though the Windblows instructions are the same.

===Setup===
Find the location of your mosquitto.conf file in the primary broker. In my case its in the /etc/mosquitto folder. Use whatever editor applies to your tastes, but I like vim. You must have admin access to modify this file
sudo vim /etc/mosquitto/mosquitto.conf
In the file you will need to add the lines that create a bridge. Add in the following:

#External MQTT Broker
allow_anonymous true
connection <your_second_broker_name>
address other_broker_IP:1883
topic # out 0
topic # in 0

Save the file and restart your broker (More than likely by restarting the computer)

Important Notes #

*<code>'allow anonymous true'</code> is required if you '''DON'T''' use name and password for your broker communications. Additional lines are required if you '''DO''' use authentication.
*Replace <code><your_second_broker_name></code> with whatever you want your other broker named internally. You must have this line but you can call it anything you'd like. I use DNS in my network so I named the same as the devices hostname.
*Replace <code>other_broker_IP</code> with the IP (or name if you have DNS set up in your network) of your second broker. If you use non-default or secured port numbers, change 1883 to the correct number of your broker
*The topic in and out lines tell the broker to subscribe to every message broadcast from the second broker and to broadcast out every message received directly on the first TO the second. This is why you don't want to do this to BOTH brokers. They will sub and publish to each other until their little brains fall out. Besides, it angers the IT folks in the matrix... just saying.
*BONUS NOTE: If you want to restrict what is sent between them, i.e. to not send STAT messages back and forth, you can change the '#' to specific topic and only that one will be rebroadcast... Refer to [http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's tutorial] for more of that mind numbing configuration.

===Testing===
To make sure that you have it set up correctly, use your visual client of choice (I use [http://workswithweb.com/html/mqttbox/downloads.html MQTT Box]) and open two instances. One needs to be connected to each of the brokers. Pick a topic and sub to it in each window... let's use 'broker/testing' for giggles. Then open a publish screen in both windows. Publish the payload "Hello World" to 'broker/testing' topic on one and make sure that in your sub screen "Hello World" shows up on BOTH brokers sub screens. If it does, good. If not, you did something wrong (like probably not restarting the broker you made the .conf file mods to). This tests that you have communication in one direction, broker to broker. Now, publish the same message to the same topic in your other window and make sure the message shows up in the subscribe screens of both brokers. This tests communications going the other way. Worked? Great! No? You need to troubleshoot...

MQTT Bridging

2021-01-25T01:31:21Z

Grant:

==Bridged MQTT Setup==

==='''Prerequisites''' -> [[http://wingsquare.com/blog/setting-up-mqtt-mosquitto-broker-in-ubuntu-linux/|Installing Mosquitto Broker]] .===
Submitted by Guru of Nothing

If you are using MQTT for your automation backbone, you may need to have more than one MQTT broker. In my case, I have a main broker that the majority of my devices connect to in the local network (Skynet, a VM on an enterprise server locally) and I have a secondary broker (PiBridge, an rPi) that is located in the node cabinet at my gate. There are a number of devices at the gate that are critical and if the power goes out to the property, these are powered by 12v battery. Skynet will go down and the gate devices MUST have a broker. So a bridged setup is vital. I installed a Lite version of Raspi OS (previously called Raspbian) on a rPi 3b+ and enabled SSH. I then installed Mosquitto. The rPi is powered from the battery that all the other devices there use for backup power.

The basic bridge is pretty simple. There are lots of options for this and it gets pretty complicated rather quickly. Take a trip over to[http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's place] if you want more info and additional options and use cases. I am sticking with a simple relay between the two. At the most basic, you need to set up ONE (and only one) of your brokers to be the bridge. For this 'relay' connection DO NOT do the following to both or you will create a messaging loop that will bork both of your brokers and make your devices want to commit suicide. Let's set up the bridge. These are Linux instructions, though the Windblows instructions are the same.

===Setup===
Find the location of your mosquitto.conf file in the primary broker. In my case its in the /etc/mosquitto folder. Use whatever editor applies to your tastes, but I like vim. You must have admin access to modify this file
sudo vim /etc/mosquitto/mosquitto.conf
In the file you will need to add the lines that create a bridge. Add in the following:

#External MQTT Broker
allow_anonymous true
connection <your_second_broker_name>
address other_broker_IP:1883
topic # out 0
topic # in 0

Save the file and restart your broker (More than likely by restarting the computer)

Important Notes #

*<code>'allow anonymous true'</code> is required if you '''DON'T''' use name and password for your broker communications. Additional lines are required if you '''DO''' use authentication.
*Replace <code><your_second_broker_name></code> with whatever you want your other broker named internally. You must have this line but you can call it anything you'd like. I use DNS in my network so I named the same as the devices hostname.
*Replace <code>other_broker_IP</code> with the IP (or name if you have DNS set up in your network) of your second broker. If you use non-default or secured port numbers, change 1883 to the correct number of your broker
*The topic in and out lines tell the broker to subscribe to every message broadcast from the second broker and to broadcast out every message received directly on the first TO the second. This is why you don't want to do this to BOTH brokers. They will sub and publish to each other until their little brains fall out. Besides, it angers the IT folks in the matrix... just saying.
*BONUS NOTE: If you want to restrict what is sent between them, i.e. to not send STAT messages back and forth, you can change the '#' to specific topic and only that one will be rebroadcast... Refer to [http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's tutorial] for more of that mind numbing configuration.

===Testing===
To make sure that you have it set up correctly, use your visual client of choice (I use [http://workswithweb.com/html/mqttbox/downloads.html MQTT Box]) and open two instances. One needs to be connected to each of the brokers. Pick a topic and sub to it in each window... let's use 'broker/testing' for giggles. Then open a publish screen in both windows. Publish the payload "Hello World" to 'broker/testing' topic on one and make sure that in your sub screen "Hello World" shows up on BOTH brokers sub screens. If it does, good. If not, you did something wrong (like probably not restarting the broker you made the .conf file mods to). This tests that you have communication in one direction, broker to broker. Now, publish the same message to the same topic in your other window and make sure the message shows up in the subscribe screens of both brokers. This tests communications going the other way. Worked? Great! No? You need to troubleshoot...

MQTT Bridging

2021-01-25T01:29:43Z

Grant: Created page with "==Bridged MQTT Setup== ==='''Prerequisites''' -> Installing Mosquitto Broker .=== Submitted by Guru of Nothing If you are using MQTT for you..."

==Bridged MQTT Setup==

==='''Prerequisites''' -> [[Mosquitto MQTT Broker|Installing Mosquitto Broker]] .===
Submitted by Guru of Nothing

If you are using MQTT for your automation backbone, you may need to have more than one MQTT broker. In my case, I have a main broker that the majority of my devices connect to in the local network (Skynet, a VM on an enterprise server locally) and I have a secondary broker (PiBridge, an rPi) that is located in the node cabinet at my gate. There are a number of devices at the gate that are critical and if the power goes out to the property, these are powered by 12v battery. Skynet will go down and the gate devices MUST have a broker. So a bridged setup is vital. I installed a Lite version of Raspi OS (previously called Raspbian) on a rPi 3b+ and enabled SSH. I then installed Mosquitto. The rPi is powered from the battery that all the other devices there use for backup power.

The basic bridge is pretty simple. There are lots of options for this and it gets pretty complicated rather quickly. Take a trip over to[http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's place] if you want more info and additional options and use cases. I am sticking with a simple relay between the two. At the most basic, you need to set up ONE (and only one) of your brokers to be the bridge. For this 'relay' connection DO NOT do the following to both or you will create a messaging loop that will bork both of your brokers and make your devices want to commit suicide. Let's set up the bridge. These are Linux instructions, though the Windblows instructions are the same.

===Setup===
Find the location of your mosquitto.conf file in the primary broker. In my case its in the /etc/mosquitto folder. Use whatever editor applies to your tastes, but I like vim. You must have admin access to modify this file
sudo vim /etc/mosquitto/mosquitto.conf
In the file you will need to add the lines that create a bridge. Add in the following:

#External MQTT Broker
allow_anonymous true
connection <your_second_broker_name>
address other_broker_IP:1883
topic # out 0
topic # in 0

Save the file and restart your broker (More than likely by restarting the computer)

Important Notes #

*<code>'allow anonymous true'</code> is required if you '''DON'T''' use name and password for your broker communications. Additional lines are required if you '''DO''' use authentication.
*Replace <code><your_second_broker_name></code> with whatever you want your other broker named internally. You must have this line but you can call it anything you'd like. I use DNS in my network so I named the same as the devices hostname.
*Replace <code>other_broker_IP</code> with the IP (or name if you have DNS set up in your network) of your second broker. If you use non-default or secured port numbers, change 1883 to the correct number of your broker
*The topic in and out lines tell the broker to subscribe to every message broadcast from the second broker and to broadcast out every message received directly on the first TO the second. This is why you don't want to do this to BOTH brokers. They will sub and publish to each other until their little brains fall out. Besides, it angers the IT folks in the matrix... just saying.
*BONUS NOTE: If you want to restrict what is sent between them, i.e. to not send STAT messages back and forth, you can change the '#' to specific topic and only that one will be rebroadcast... Refer to [http://www.steves-internet-guide.com/mosquitto-bridge-configuration/ Steve's tutorial] for more of that mind numbing configuration.

===Testing===
To make sure that you have it set up correctly, use your visual client of choice (I use [http://workswithweb.com/html/mqttbox/downloads.html MQTT Box]) and open two instances. One needs to be connected to each of the brokers. Pick a topic and sub to it in each window... let's use 'broker/testing' for giggles. Then open a publish screen in both windows. Publish the payload "Hello World" to 'broker/testing' topic on one and make sure that in your sub screen "Hello World" shows up on BOTH brokers sub screens. If it does, good. If not, you did something wrong (like probably not restarting the broker you made the .conf file mods to). This tests that you have communication in one direction, broker to broker. Now, publish the same message to the same topic in your other window and make sure the message shows up in the subscribe screens of both brokers. This tests communications going the other way. Worked? Great! No? You need to troubleshoot...

IoT - MQTT

2021-01-25T01:28:56Z

Grant: /* MQTT - Topics and Wildcards */

==Mosquitto==
[https://mosquitto.org/ MosQuiTTo Web Site]

*[https://mosquitto.org/man/mosquitto-conf-5.html mosquitto.conf — the configuration file for mosquitto]
*[https://github.com/guibom/WebMQonttrol WebMQonttrol]
*[http://mqtt-explorer.com/ MQTT Explorer]
**[https://github.com/thomasnordquist/MQTT-Explorer On GIThub]

==Tools==

*[https://mqtt-explorer.com/ MQTT Explorer]
*[https://mqttfx.jensd.de/ MQTT.fx]

==Links==

*[https://mosquitto.org/documentation/ Documentation]
*[http://wingsquare.com/blog/setting-up-mqtt-mosquitto-broker-in-ubuntu-linux/ Setting up MQTT Mosquitto broker in Ubuntu Linux]
*[https://www.google.ca/search?q=mqtt+and+google+home&gws_rd=cr&dcr=0&ei=YA9TWtfuDcKE8gXAh4z4Aw '''''SEARCH:''''' mqtt and google home]
*[https://www.google.ca/search?q=sonoff+mqtt&gws_rd=cr&dcr=0&ei=xGtVWtKPKpO9jwSx_K54 '''''SEARCH:''''' sonoff mqtt]
*[https://github.com/krvarma/sonoff-mqtt A simple proof of concept home automation using Sonoff WiFi Switch, MQTT and Google Assistant platform.]
*[https://www.hivemq.com/blog/mqtt-essentials/ MQTT Essentials]
<ol style="margin-left: 40px;">
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-1-introducing-mqtt Introducing MQTT]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part2-publish-subscribe Publish & Subscribe]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-3-client-broker-connection-establishment Client, Broker and Connection Establishment]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-4-mqtt-publish-subscribe-unsubscribe MQTT Publish, Subscribe & Unsubscribe]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices MQTT Topics & Best Practices]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels Quality of Service 0, 1 & 2]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-7-persistent-session-queuing-messages Persistent Session and Queuing Messages]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-8-retained-messages Retained Messages]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-9-last-will-and-testament Last Will and Testament]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-part-10-alive-client-take-over Keep Alive and Client Take-Over]</li>
</ol>
<ul style="margin-left: 40px;">
<li>[https://www.hivemq.com/blog/mqtt-essentials-special-mqtt-over-websockets MQTT Essentials Special: MQTT over WebSockets]</li>
<li>[https://www.hivemq.com/blog/mqtt-essentials-wrap-up MQTT Essentials Wrap-Up]</li>
</ul>

*[https://www.hivemq.com/mqtt-security-fundamentals/ MQTT Security Fundamentals]
*[https://www.mysensors.org/build/mqtt_gateway Building a MQTT Gateway (Arduino & W5100)]
*[https://github.com/esp8266/Arduino/issues/2839 ESP8266 as mqtt broker]
**[https://github.com/martin-ger/uMQTTBroker MQTT Broker library for ESP8266 Arduino]

===[http://patriot-geek.blogspot.com/2017/03/mqtt-topics-and-wildcards.html MQTT - Topics and Wildcards]===

=== [[MQTT Bridging]] ===

Grafana

2020-12-01T18:41:41Z

Grant: Created page with "==How To Install Grafana on Linux Mint 20== https://grafana.com/docs/grafana/latest/installation/debian/ Installation was tested on a fresh VM of Mint 20 so if i screwed some..."

==How To Install Grafana on Linux Mint 20==
https://grafana.com/docs/grafana/latest/installation/debian/

Installation was tested on a fresh VM of Mint 20 so if i screwed something up, it wasn't going to be my Automation server

There are 2 versions that could be installed -OSS and Enterprise. It is suggested by Grafana to install the Enterprise version for stability. We will be installing the latest version in this setup. Run the following in a teminal window that is local or SSH'd into your system that will host it...

<code>sudo apt-get install -y apt-transport-https</code>

<code>sudo apt-get install -y software-properties-common wget</code>

<code>wget -q -O - <nowiki>https://packages.grafana.com/gpg.key</nowiki> | sudo apt-key add -</code>

===Add the repository to the list and install===
<code>echo "deb <nowiki>https://packages.grafana.com/enterprise/deb</nowiki> stable main" | sudo tee -a /etc/apt/sources.list.d/grafana.list</code>

<code>sudo apt-get update</code>

<code>sudo apt-get install grafana-enterprise</code>

===Start the Server===
<code>sudo systemctl daemon-reload</code>

<code>sudo systemctl start grafana-server</code>

===Verify that its running properly===
<code>sudo systemctl status grafana-server</code>

===Now configure it to start at boot===
<code>sudo systemctl enable grafana-server.service</code>

===Package details===

*Installs binary to <code>/usr/sbin/grafana-server</code>
*Installs Init.d script to <code>/etc/init.d/grafana-server</code>
*Creates default file (environment vars) to <code>/etc/default/grafana-server</code>
*Installs configuration file to <code>/etc/grafana/grafana.ini</code>
*Installs systemd service (if systemd is available) name <code>grafana-server.service</code>
*The default configuration sets the log file at <code>/var/log/grafana/grafana.log</code>
*The default configuration specifies a SQLite3 db at <code>/var/lib/grafana/grafana.db</code>
*Installs HTML/JS/CSS and other Grafana files at <code>/usr/share/grafana</code>

==Getting Started with Grafana==
The home for this information is here:

https://grafana.com/docs/grafana/latest/getting-started/getting-started/

Open a browser to your new Grafana install, in my case its '''''192.168.1.139:3000'''''

Default user is admin/admin and it will make you change the password

The test install login is admin/Fiddlehead

==Connecting with InfluxDB==
https://grafana.com/docs/grafana/latest/datasources/influxdb/

Open up the GUI for Grafana on your host machine. Log in and click on the little icon that looks like 4 boxes on the left tab. This is the '<nowiki/>'''Dashboards'''<nowiki/>' button. One of the options will be '<nowiki/>'''Data Sources'''<nowiki/>'. Click that and select ''''Add Data Source'''<nowiki/>'.

Give the data source a meaningful name. I gave mine 'InfluxDB'. Select the query language 'InfluxQL'.

My databases are not set up for authorization or credentials since this setup will not be allowed to go play in the streets so all auth is turned off.

Scroll down to '<nowiki/>'''InfluxDB Details'''<nowiki/>'. Put in the name of your new database if this is the first one being added, or the name of the additional database you want in the system. Put in the username and password. Select the type of http access you want. The simple version is '<nowiki/>'''GET'''<nowiki/>'. If you are going to be doing long requests then select ''''POST'''<nowiki/>'. Hit 'Save and Test'. You should get a green bar that says you are connected to the proper database and all is well.

== Adding in a data stream from Node Red ==
Presumably, you went through all this trouble so you could graph and map the giant amount of data you are creating in your IoT gear around your home. Open Node Red and go to '''Manage Pallete.''' Chances are you installed the v2.0 of Influx DB so you will need the ''''NodeRed - Contrib - Stackhero- InfluxDB - v2'''<nowiki/>' pallette.

Utilizing that pallete........ Dunno yet

InfluxDB

2020-12-01T18:39:32Z

Grant: Created page with "==Installing InfluxDB on Mint 19.3 and 20== ===Start by adding it to the repository=== <code>echo "deb <nowiki>https://repos.influxdata.com/debian</nowiki> stretch stable" |..."

==Installing InfluxDB on Mint 19.3 and 20==

===Start by adding it to the repository===
<code>echo "deb <nowiki>https://repos.influxdata.com/debian</nowiki> stretch stable" | sudo tee /etc/apt/sources.list.d/influxdb.list</code>

===Install GPG Key===
<code>sudo curl -sL <nowiki>https://repos.influxdata.com/influxdb.key</nowiki> | sudo apt-key add -</code>

===Update the index and INSTALL===
<code>sudo apt-get update</code>

<code>sudo apt-get install -y influxdb</code>

===Start, Enable and Verify it is running===
<code>sudo systemctl start influxdb</code>

<code>sudo systemctl enable influxdb</code>

<code>systemctl status influxdb</code>

==Setting up a Database==
This will set up an initial database to start with. This gets really deep, really fast if you are not familiar with databases or the coding behind the system. The guide for this can be found at https://docs.influxdata.com/influxdb/v1.8/introduction/get-started/ Good luck with that.

You need to access InfluxDB so open a terminal on the machine it is hosted on (or SSH into it if that is your thing)... type in the terminal
influx
You should see a message like this:

$ influx -precision rfc3339
Connected to <nowiki>http://localhost:8086</nowiki> version 1.8.x
InfluxDB shell 1.8.x
>
A fresh install of if InfluxDB has no useable databases outside of the default internal one. So type this at the prompt, replacing <db-name> with the name you want

<code>CREATE DATABASE <db-name></code>

If all went properly, you won't see any additional info, just the prompt again. Now let's make sure that the database is good just for giggles

<code>SHOW DATABASES</code>

You should see your database listed. If not, something borked and I can't help you with that.

Are you planning to use this with Grafana? You will need to set up a datasource in Grafana then.

==Using this with Grafana==
Set up your database in Grafana by going here... [[Grafana#Connecting with InfluxDB|Connecting with InfluxDB]]

IoT - ESP-M3 Everything!

2020-11-05T21:35:38Z

Grant:

AutomationServer - TasmoAdmin

2020-09-12T08:08:43Z

Grant:

[https://github.com/reloxx13/TasmoAdmin TasmoAdmin]

==Installation==
There are a couple items in the instructions for installing under Linux that are just plain wrong when running an up-to-date Mint-based server. But now you can just copy-pasta from this page... :)

*<code>sudo apt-get update && sudo apt-get install apache2 php libapache2-mod-php php7.2-curl php7.2-zip git vim</code>
*<code>sudo git clone <nowiki>https://github.com/reloxx13/TasmoAdmin.git</nowiki> /var/www/tasmoadmin</code>
*<code>sudo chown -R www-data:www-data /var/www/tasmoadmin</code>
*<code>sudo chmod 777 /var/www/tasmoadmin/tasmoadmin/tmp && sudo chmod 777 /var/www/tasmoadmin/tasmoadmin/data</code>
*<code>sudo rm /etc/php/7.2/apache2/conf.d/10-opcache.ini</code>
*<code>sudo vim /etc/apache2/sites-available/tasmoadmin.conf</code>

<syntaxhighlight lang="apacheconf">
<VirtualHost *:9999>
ServerName tasmoadmin
ServerAdmin webmaster@localhost
DocumentRoot /var/www/tasmoadmin/tasmoadmin
<Directory /var/www/tasmoadmin/tasmoadmin>
AllowOverride All
Order allow,deny
allow from all
</Directory>
ErrorLog /var/log/apache2/error.log
LogLevel warn
CustomLog /var/log/apache2/access.log combined
ServerSignature On
</VirtualHost>
</syntaxhighlight>

*<code>sudo vim /etc/apache2/ports.conf</code>

ADD IN "Listen 9999" to the ports.conf file like this:

<syntaxhighlight lang="apacheconf">
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf

Listen 80
Listen 9999

<IfModule ssl_module>
Listen 443
</IfModule>

<IfModule mod_gnutls.c>
Listen 443
</IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
</syntaxhighlight>

*<code>sudo a2ensite tasmoadmin</code>
*<code>sudo a2enmod rewrite</code>
*<code>sudo service apache2 restart</code>

==Troubleshooting==

===Problem===
On opening the start page all i was presented with was:

<code>array(3) { [0]=> array(7) { ["file"]=> string(50)</code>

<code>...</code>

<code>string(12) "include_once" } } could not read MyConfig.json in read</code>

(Screen full of gibberish...)

====Fix====
SSH into the server & check the '''MyConfig.json''' file:

*<code>ls -l /var/www/tasmoadmin/tasmoadmin/data/</code>

If it is zero-length, delete it.

*<code>sudo rm /var/www/tasmoadmin/tasmoadmin/data/MyConfig.json</code>

Refresh the webpage.
[[Category:IoT]]
[[Category:AutomationServer]]
[[Category:TasmOTA]]

WikiServer - Install EVEN NEWER

2020-08-15T08:38:08Z

Grant:

'''NEW Version!'''

'''Now with more VirtualHosts...'''

'''And an attempt at running a Development release'''

*Proven on Mint 20 ... (Gets MySQL 8.0)
*Proven on SparkyLinux 5.11 ... (You'll have to [https://tecadmin.net/install-mysql-server-on-debian9-stretch/ fix the missing MySQL] thing & install vim first)
**[[Getting MySQL onto SparkyLinux|Getting MySQL onto SparkyLinux]]

===Install the LAMP Stack===

[[WebServer - Basic LAMP Stack Install|Basic LAMP Stack Install]]

===Install MediaWiki===

*<code>wget <nowiki>https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.1.tar.gz</nowiki></code>
*<code>tar -xvzf mediawiki-1.35.0-rc.1.tar.gz</code>
*<code>sudo mkdir /var/www/wiki</code>
*<code>sudo mkdir /var/www/labnotes</code>
*<code>sudo cp -r mediawiki-1.35.0-rc.1/* /var/www/wiki</code>
*<code>sudo cp -r mediawiki-1.35.0-rc.1/* /var/www/labnotes</code>
*<code>sudo mysql -u root -p</code>

CREATE DATABASE my_wiki;
GRANT ALL PRIVILEGES ON my_wiki.* TO 'someone'@'localhost';
FLUSH PRIVILEGES;
CREATE DATABASE my_notes;
GRANT ALL PRIVILEGES ON my_notes.* TO 'someone'@'localhost';
FLUSH PRIVILEGES;
EXIT;

*<code>sudo vim /etc/php/7.4/apache2/php.ini</code>
**(this may be in a slightly different location depending on version of php installed...)
**increase <code>upload_max_filesize</code> to 200M
*Fix upload directories:
**<code>sudo chmod -R ugo+rwX /var/www/wiki/images</code>
**<code>sudo chmod -R ugo+rwX /var/www/labnotes/images</code>

Configure your webserver with [[WebServer - Name-based Virtual Host Support|VirtualHosts]] for the Wiki & LabNotes

*Wiki
**<code>ServerName WikiServer.Domain.TLD</code>
**<code>DocumentRoot "/var/www/wiki"</code>
*LabNotes
**<code>ServerName LabNotesServer.Domain.TLD</code>
**<code>DocumentRoot "/var/www/labnotes"</code>

Browse to '''<nowiki>http://WikiServer.Domain.TLD/</nowiki>''' & follow the steps presented.

Set it as '''Authorised editors only'''.

Browse to '''<nowiki>http://LabNotesServer.Domain.TLD/</nowiki>''' & follow the steps presented.

Set as '''Private Wiki'''

===Adding another Wiki to an existing Wiki Server===

*<code>sudo mkdir /var/www/anudderwiki</code>
*<code>sudo cp -r mediawiki-*/* /var/www/anudderwiki</code>
*<code>sudo mysql -u root -p</code>
**<code>CREATE DATABASE anudder_wiki;</code>
**<code>GRANT ALL PRIVILEGES ON anudder_wiki.* TO 'someone'@'localhost';</code>
**<code>FLUSH PRIVILEGES;</code>
**<code>EXIT;</code>
*<code>sudo chmod -R ugo+rwX /var/www/anudderwiki/images</code>

Configure your webserver with VirtualHosts for the new Wiki

*<code>ServerName AnudderWikiServer.Domain.TLD</code>
*<code>DocumentRoot "/var/www/anudderwiki"</code>

Browse to '''<nowiki>http://AnudderWikiServer.Domain.TLD/</nowiki>''' & follow the steps presented.

Set as '''Authorised editors only''' or '''Private Wiki'''

===Troubleshooting===
'''Note:''' With MySQL 8, there is some possibility that it will default to the wrong authentication method.

*If Mediawiki has problems connecting & gives you "'''The server requested authentication method unknown to the client.'''" as part of the error message, sign back into MySQL & adjust the user being assigned in the wiki install:
**<code>sudo mysql -u root -p</code>
**<code>ALTER USER 'someone'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';</code>

WikiServer - Getting VisualEditor working properly

2020-08-02T23:27:34Z

Grant: Undo revision 787 by Grant (talk)

[[mediawikiwiki:Parsing/Parser_Unification|'''<big>Note:</big>'''<big> Apparently, This is being rolled into WikiMedia 1.35 by default. '''w00t!!!'''</big>]]

==Installing VisualEditor (MediaWiki 1.34 or earlier...)==
'''<big>Note:</big>''' This is still a work in progress... Multi-Wiki is a bit of a fail.

[[mediawikiwiki:Extension:VisualEditor|Extension:VisualEditor]]

'''''VisualEditor does not currently work with private wikis. Supposedly, there are workarounds, but more research is needed.'''''

===Requirements===

*Parsoid 0.11.0
*Node.js 12

====Parsoid Install====
https://www.mediawiki.org/wiki/Parsoid/Setup

*<code>sudo apt install dirmngr</code>
*<code>sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys AF380A3036A03444</code>
*<code>echo "deb <nowiki>https://releases.wikimedia.org/debian</nowiki> jessie-mediawiki main" | sudo tee /etc/apt/sources.list.d/parsoid.list</code>
*<code>sudo apt install apt-transport-https</code>
*<code>sudo apt update && sudo apt install parsoid</code>
*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

'''''This will require further fuckery for the multi-wiki setup with private wiki!'''''

====VisualEditor Install====

Find the current version via: [[mediawikiwiki:Special:ExtensionDistributor/VisualEditor|Download MediaWiki extension]]

*<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_34-74116a7.tar.gz</nowiki></code>
**'''This URL will change!'''
*<code>tar -xzf VisualEditor-REL1_34-74116a7.tar.gz</code>
*<code>sudo rsync -av VisualEditor /var/www/html/wiki/extensions</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => '<nowiki>http://localhost:8142'</nowiki>,
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);

===Multiple Wiki Configuration===

Repeat the parts above where stuff is done in the /wiki/ folder

(but use the folder for your second wiki... duh...)

*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: '<nowiki>http://wiki.tinkernow.net/api.php'</nowiki>
domain: 'wiki'
prefix: 'wiki'
- # and another MediaWiki
uri: '<nowiki>http://labnotes.tinkernow.net/api.php'</nowiki>
domain: 'notes'
prefix: 'notes'

*<code>sudo service parsoid restart</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(
# 'url' => '<nowiki>http://wiki.tinkernow.net:8142'</nowiki>,
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'wiki',
'prefix' => 'wiki'
);

*<code>sudo vim /var/www/html/notes/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

#$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'notes',
'prefix' => 'notes',
'forwardCookies' => true
);

==VisualEditor on MediaWiki 1.35 or newer==
Why yes... It '''IS''' rolled in.

Either enable it during setup or add

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

to the list in <code>LocalSettings.php</code>.

===Enabling VisualEditor on a Private Wiki===

#Install the [[mediawikiwiki:Extension:NetworkAuth|NetworkAuth extension]]
#*(details coming...)
#*Download the extension (do this ON the server...):
#*For version 1.34
#**<code><nowiki>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</nowiki></code>
#*For version 1.35
#**<code><nowiki>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_35-9f2e881.tar.gz</nowiki></code>
#**(You may need to find the latest or possibly correct version at some point...)
#*Copy it into your Private Wiki:
#**<code>tar -xzf NetworkAuth-*.tar.gz -C /var/www/privatewiki/extensions</code>
#**(do adjust for the ACTUAL root of your wiki...)
#Create a user named "'''parsoid'''" on your wiki.
#Add the following to <code>LocalSettings.php</code> on your Private Wiki:
#*replace '''127.0.0.1''' with the actual IP address of your Wiki Server

require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'parsoid'
];
<ol start="4">
<li>'''<big>enjoy</big>'''</li>
</ol>

WikiServer - Getting VisualEditor working properly

2020-08-02T23:25:44Z

Grant:

[[mediawikiwiki:Parsing/Parser_Unification|'''<big>Note:</big>'''<big> Apparently, This is being rolled into WikiMedia 1.35 by default. '''w00t!!!'''</big>]]

==Installing VisualEditor (MediaWiki 1.34 or earlier...)==
'''<big>Note:</big>''' This is still a work in progress... Multi-Wiki is a bit of a fail.

[[mediawikiwiki:Extension:VisualEditor|Extension:VisualEditor]]

'''''VisualEditor does not currently work with private wikis. Supposedly, there are workarounds, but more research is needed.'''''

===Requirements===

*Parsoid 0.11.0
*Node.js 12

====Parsoid Install====
https://www.mediawiki.org/wiki/Parsoid/Setup

*<code>sudo apt install dirmngr</code>
*<code>sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys AF380A3036A03444</code>
*<code>echo "deb <nowiki>https://releases.wikimedia.org/debian</nowiki> jessie-mediawiki main" | sudo tee /etc/apt/sources.list.d/parsoid.list</code>
*<code>sudo apt install apt-transport-https</code>
*<code>sudo apt update && sudo apt install parsoid</code>
*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

'''''This will require further fuckery for the multi-wiki setup with private wiki!'''''

====VisualEditor Install====

Find the current version via: [[mediawikiwiki:Special:ExtensionDistributor/VisualEditor|Download MediaWiki extension]]

*<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_34-74116a7.tar.gz</nowiki></code>
**'''This URL will change!'''
*<code>tar -xzf VisualEditor-REL1_34-74116a7.tar.gz</code>
*<code>sudo rsync -av VisualEditor /var/www/html/wiki/extensions</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => '<nowiki>http://localhost:8142'</nowiki>,
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);

===Multiple Wiki Configuration===

Repeat the parts above where stuff is done in the /wiki/ folder

(but use the folder for your second wiki... duh...)

*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: '<nowiki>http://wiki.tinkernow.net/api.php'</nowiki>
domain: 'wiki'
prefix: 'wiki'
- # and another MediaWiki
uri: '<nowiki>http://labnotes.tinkernow.net/api.php'</nowiki>
domain: 'notes'
prefix: 'notes'

*<code>sudo service parsoid restart</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'wiki',
'prefix' => 'wiki'
);

*<code>sudo vim /var/www/html/notes/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

#$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'notes',
'prefix' => 'notes',
);

==VisualEditor on MediaWiki 1.35 or newer==
Why yes... It '''IS''' rolled in.

Either enable it during setup or add

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

to the list in <code>LocalSettings.php</code>.

===Enabling VisualEditor on a Private Wiki===

#Install the [[mediawikiwiki:Extension:NetworkAuth|NetworkAuth extension]]
#*(details coming...)
#*Download the extension (do this ON the server...):
#*For version 1.34
#**<code><nowiki>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</nowiki></code>
#*For version 1.35
#**<code><nowiki>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_35-9f2e881.tar.gz</nowiki></code>
#**(You may need to find the latest or possibly correct version at some point...)
#*Copy it into your Private Wiki:
#**<code>tar -xzf NetworkAuth-*.tar.gz -C /var/www/privatewiki/extensions</code>
#**(do adjust for the ACTUAL root of your wiki...)
#Create a user named "'''parsoid'''" on your wiki.
#Add the following to <code>LocalSettings.php</code> on your Private Wiki:
#*replace '''127.0.0.1''' with the actual IP address of your Wiki Server

require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'parsoid'
];
<ol start="4">
<li>'''<big>enjoy</big>'''</li>
</ol>

WikiServer - Getting VisualEditor working properly

2020-08-02T06:38:30Z

Grant: /* Enabling VisualEditor on a Private Wiki */

WikiServer - Getting VisualEditor working properly

2020-08-02T06:36:06Z

Grant: /* Enabling VisualEditor on a Private Wiki */

[[mediawikiwiki:Parsing/Parser_Unification|'''<big>Note:</big>'''<big> Apparently, This is being rolled into WikiMedia 1.35 by default. '''w00t!!!'''</big>]]

==Installing VisualEditor (MediaWiki 1.34 or earlier...)==
'''<big>Note:</big>''' This is still a work in progress... Multi-Wiki is a bit of a fail.

[[mediawikiwiki:Extension:VisualEditor|Extension:VisualEditor]]

'''''VisualEditor does not currently work with private wikis. Supposedly, there are workarounds, but more research is needed.'''''

===Requirements===

*Parsoid 0.11.0
*Node.js 12

====Parsoid Install====
https://www.mediawiki.org/wiki/Parsoid/Setup

*<code>sudo apt install dirmngr</code>
*<code>sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys AF380A3036A03444</code>
*<code>echo "deb <nowiki>https://releases.wikimedia.org/debian</nowiki> jessie-mediawiki main" | sudo tee /etc/apt/sources.list.d/parsoid.list</code>
*<code>sudo apt install apt-transport-https</code>
*<code>sudo apt update && sudo apt install parsoid</code>
*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

'''''This will require further fuckery for the multi-wiki setup with private wiki!'''''

====VisualEditor Install====

Find the current version via: [[mediawikiwiki:Special:ExtensionDistributor/VisualEditor|Download MediaWiki extension]]

*<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_34-74116a7.tar.gz</nowiki></code>
**'''This URL will change!'''
*<code>tar -xzf VisualEditor-REL1_34-74116a7.tar.gz</code>
*<code>sudo rsync -av VisualEditor /var/www/html/wiki/extensions</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => '<nowiki>http://localhost:8142'</nowiki>,
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);

===Multiple Wiki Configuration===

Repeat the parts above where stuff is done in the /wiki/ folder

(but use the folder for your second wiki... duh...)

*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: '<nowiki>http://wiki.tinkernow.net/api.php'</nowiki>
domain: 'wiki'
prefix: 'wiki'
- # and another MediaWiki
uri: '<nowiki>http://labnotes.tinkernow.net/api.php'</nowiki>
domain: 'notes'
prefix: 'notes'

*<code>sudo service parsoid restart</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(
# 'url' => '<nowiki>http://wiki.tinkernow.net:8142'</nowiki>,
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'wiki',
'prefix' => 'wiki'
);

*<code>sudo vim /var/www/html/notes/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

#$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'notes',
'prefix' => 'notes',
'forwardCookies' => true
);

==VisualEditor on MediaWiki 1.35 or newer==
Why yes... It '''IS''' rolled in.

Either enable it during setup or add

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

to the list in <code>LocalSettings.php</code>.

===Enabling VisualEditor on a Private Wiki===

#Install the [[mediawikiwiki:Extension:NetworkAuth|NetworkAuth extension]]
#*(details coming...)
#*Download the extension (do this ON the server...):
#*For version 1.34
#**<code>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</code>
#*For version 1.35
#**<code>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_35-9f2e881.tar.gz</code>
#**(You may need to find the latest or possibly correct version at some point...)
#***On MediaWiki 1.34:
#***<code>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</code>
#*Copy it into your Private Wiki:
#**<code>tar -xzf NetworkAuth-*.tar.gz -C /var/www/privatewiki/extensions</code>
#**(do adjust for the ACTUAL root of your wiki...)
#Create a user named "'''parsoid'''" on your wiki.
#Add the following to <code>LocalSettings.php</code> on your Private Wiki:
#*replace '''127.0.0.1''' with the actual IP address of your Wiki Server

require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'parsoid'
];
<ol start="4">
<li>'''<big>enjoy</big>'''</li>
</ol>

WikiServer - Getting VisualEditor working properly

2020-08-02T06:33:37Z

Grant:

[[mediawikiwiki:Parsing/Parser_Unification|'''<big>Note:</big>'''<big> Apparently, This is being rolled into WikiMedia 1.35 by default. '''w00t!!!'''</big>]]

==Installing VisualEditor (MediaWiki 1.34 or earlier...)==
'''<big>Note:</big>''' This is still a work in progress... Multi-Wiki is a bit of a fail.

[[mediawikiwiki:Extension:VisualEditor|Extension:VisualEditor]]

'''''VisualEditor does not currently work with private wikis. Supposedly, there are workarounds, but more research is needed.'''''

===Requirements===

*Parsoid 0.11.0
*Node.js 12

====Parsoid Install====
https://www.mediawiki.org/wiki/Parsoid/Setup

*<code>sudo apt install dirmngr</code>
*<code>sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys AF380A3036A03444</code>
*<code>echo "deb <nowiki>https://releases.wikimedia.org/debian</nowiki> jessie-mediawiki main" | sudo tee /etc/apt/sources.list.d/parsoid.list</code>
*<code>sudo apt install apt-transport-https</code>
*<code>sudo apt update && sudo apt install parsoid</code>
*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

'''''This will require further fuckery for the multi-wiki setup with private wiki!'''''

====VisualEditor Install====

Find the current version via: [[mediawikiwiki:Special:ExtensionDistributor/VisualEditor|Download MediaWiki extension]]

*<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_34-74116a7.tar.gz</nowiki></code>
**'''This URL will change!'''
*<code>tar -xzf VisualEditor-REL1_34-74116a7.tar.gz</code>
*<code>sudo rsync -av VisualEditor /var/www/html/wiki/extensions</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => '<nowiki>http://localhost:8142'</nowiki>,
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);

===Multiple Wiki Configuration===

Repeat the parts above where stuff is done in the /wiki/ folder

(but use the folder for your second wiki... duh...)

*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: '<nowiki>http://wiki.tinkernow.net/api.php'</nowiki>
domain: 'wiki'
prefix: 'wiki'
- # and another MediaWiki
uri: '<nowiki>http://labnotes.tinkernow.net/api.php'</nowiki>
domain: 'notes'
prefix: 'notes'

*<code>sudo service parsoid restart</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(
# 'url' => '<nowiki>http://wiki.tinkernow.net:8142'</nowiki>,
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'wiki',
'prefix' => 'wiki'
);

*<code>sudo vim /var/www/html/notes/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

#$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'notes',
'prefix' => 'notes',
'forwardCookies' => true
);

==VisualEditor on MediaWiki 1.35 or newer==
Why yes... It '''IS''' rolled in.

Either enable it during setup or add

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

to the list in <code>LocalSettings.php</code>.

===Enabling VisualEditor on a Private Wiki===

#Install the [[mediawikiwiki:Extension:NetworkAuth|NetworkAuth extension]]
#*(details coming...)
#*Download the extension (do this ON the server...):
#*For version 1.35
#**<code>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_35-9f2e881.tar.gz</code>
#*For version 1.34
#**<code>wget https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</code>
#**(You may need to find the latest or possibly correct version at some point...)
#***On MediaWiki 1.34:
#***<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</nowiki></code>
#*Copy it into your Private Wiki:
#**<code>tar -xzf NetworkAuth-*.tar.gz -C /var/www/privatewiki/extensions</code>
#**(do adjust for the ACTUAL root of your wiki...)
#Create a user named "'''parsoid'''" on your wiki.
#Add the following to <code>LocalSettings.php</code> on your Private Wiki:
#*replace '''127.0.0.1''' with the actual IP address of your Wiki Server

require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'parsoid'
];
<ol start="4">
<li>'''<big>enjoy</big>'''</li>
</ol>

WikiServer - Getting VisualEditor working properly

2020-08-02T06:31:22Z

Grant:

[[mediawikiwiki:Parsing/Parser_Unification|'''<big>Note:</big>'''<big> Apparently, This is being rolled into WikiMedia 1.35 by default. '''w00t!!!'''</big>]]

==Installing VisualEditor (MediaWiki 1.34 or earlier...)==
'''<big>Note:</big>''' This is still a work in progress... Multi-Wiki is a bit of a fail.

[[mediawikiwiki:Extension:VisualEditor|Extension:VisualEditor]]

'''''VisualEditor does not currently work with private wikis. Supposedly, there are workarounds, but more research is needed.'''''

===Requirements===

*Parsoid 0.11.0
*Node.js 12

====Parsoid Install====
https://www.mediawiki.org/wiki/Parsoid/Setup

*<code>sudo apt install dirmngr</code>
*<code>sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys AF380A3036A03444</code>
*<code>echo "deb <nowiki>https://releases.wikimedia.org/debian</nowiki> jessie-mediawiki main" | sudo tee /etc/apt/sources.list.d/parsoid.list</code>
*<code>sudo apt install apt-transport-https</code>
*<code>sudo apt update && sudo apt install parsoid</code>
*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

'''''This will require further fuckery for the multi-wiki setup with private wiki!'''''

====VisualEditor Install====

Find the current version via: [[mediawikiwiki:Special:ExtensionDistributor/VisualEditor|Download MediaWiki extension]]

*<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_34-74116a7.tar.gz</nowiki></code>
**'''This URL will change!'''
*<code>tar -xzf VisualEditor-REL1_34-74116a7.tar.gz</code>
*<code>sudo rsync -av VisualEditor /var/www/html/wiki/extensions</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => '<nowiki>http://localhost:8142'</nowiki>,
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);

===Multiple Wiki Configuration===

Repeat the parts above where stuff is done in the /wiki/ folder

(but use the folder for your second wiki... duh...)

*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: '<nowiki>http://wiki.tinkernow.net/api.php'</nowiki>
domain: 'wiki'
prefix: 'wiki'
- # and another MediaWiki
uri: '<nowiki>http://labnotes.tinkernow.net/api.php'</nowiki>
domain: 'notes'
prefix: 'notes'

*<code>sudo service parsoid restart</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(
# 'url' => '<nowiki>http://wiki.tinkernow.net:8142'</nowiki>,
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'wiki',
'prefix' => 'wiki'
);

*<code>sudo vim /var/www/html/notes/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

#$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'notes',
'prefix' => 'notes',
'forwardCookies' => true
);

==VisualEditor on MediaWiki 1.35 or newer==
Why yes... It '''IS''' rolled in.

Either enable it during setup or add

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

to the list in <code>LocalSettings.php</code>.

===Enabling VisualEditor on a Private Wiki===

#Install the [[mediawikiwiki:Extension:NetworkAuth|NetworkAuth extension]]
#*(details coming...)
#*Download the extension (do this ON the server...):
#**<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_35-9f2e881.tar.gz</nowiki> for version 1.35</code>
#**
#**(You may need to find the latest or possibly correct version at some point...)
#***On MediaWiki 1.34:
#***<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_34-68393b9.tar.gz</nowiki></code>
#*Copy it into your Private Wiki:
#**<code>tar -xzf NetworkAuth-*.tar.gz -C /var/www/privatewiki/extensions</code>
#**(do adjust for the ACTUAL root of your wiki...)
#Create a user named "'''parsoid'''" on your wiki.
#Add the following to <code>LocalSettings.php</code> on your Private Wiki:
#*replace '''127.0.0.1''' with the actual IP address of your Wiki Server

require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'parsoid'
];
<ol start="4">
<li>'''<big>enjoy</big>'''</li>
</ol>

WikiServer - Getting VisualEditor working properly

2020-08-02T03:41:46Z

Grant: /* Multiple Wiki Configuration */

[[mediawikiwiki:Parsing/Parser_Unification|'''<big>Note:</big>'''<big> Apparently, This is being rolled into WikiMedia 1.35 by default. '''w00t!!!'''</big>]]

==Installing VisualEditor (MediaWiki 1.34 or earlier...)==
'''<big>Note:</big>''' This is still a work in progress... Multi-Wiki is a bit of a fail.

[[mediawikiwiki:Extension:VisualEditor|Extension:VisualEditor]]

'''''VisualEditor does not currently work with private wikis. Supposedly, there are workarounds, but more research is needed.'''''

===Requirements===

*Parsoid 0.11.0
*Node.js 12

====Parsoid Install====
https://www.mediawiki.org/wiki/Parsoid/Setup

*<code>sudo apt install dirmngr</code>
*<code>sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys AF380A3036A03444</code>
*<code>echo "deb <nowiki>https://releases.wikimedia.org/debian</nowiki> jessie-mediawiki main" | sudo tee /etc/apt/sources.list.d/parsoid.list</code>
*<code>sudo apt install apt-transport-https</code>
*<code>sudo apt update && sudo apt install parsoid</code>
*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

'''''This will require further fuckery for the multi-wiki setup with private wiki!'''''

====VisualEditor Install====

Find the current version via: [[mediawikiwiki:Special:ExtensionDistributor/VisualEditor|Download MediaWiki extension]]

*<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_34-74116a7.tar.gz</nowiki></code>
**'''This URL will change!'''
*<code>tar -xzf VisualEditor-REL1_34-74116a7.tar.gz</code>
*<code>sudo rsync -av VisualEditor /var/www/html/wiki/extensions</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => '<nowiki>http://localhost:8142'</nowiki>,
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);

===Multiple Wiki Configuration===

Repeat the parts above where stuff is done in the /wiki/ folder

(but use the folder for your second wiki... duh...)

*<code>sudo vim /etc/mediawiki/parsoid/config.yaml</code>

mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: '<nowiki>http://wiki.tinkernow.net/api.php'</nowiki>
domain: 'wiki'
prefix: 'wiki'
- # and another MediaWiki
uri: '<nowiki>http://labnotes.tinkernow.net/api.php'</nowiki>
domain: 'notes'
prefix: 'notes'

*<code>sudo service parsoid restart</code>
*<code>sudo vim /var/www/html/wiki/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(
# 'url' => '<nowiki>http://wiki.tinkernow.net:8142'</nowiki>,
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'wiki',
'prefix' => 'wiki'
);

*<code>sudo vim /var/www/html/notes/LocalSettings.php</code>

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

#$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => '<nowiki>http://localhost:8142'</nowiki>,
'domain' => 'notes',
'prefix' => 'notes',
'forwardCookies' => true
);

==VisualEditor on MediaWiki 1.35 or newer==
Why yes... It '''IS''' rolled in.

Either enable it during setup or add

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

to the list in <code>LocalSettings.php</code>.

===Enabling VisualEditor on a Private Wiki===

#Install the [[mediawikiwiki:Extension:NetworkAuth|NetworkAuth extension]]
#*(details coming...)
#*Download the extension (do this ON the server...):
#**<code>wget <nowiki>https://extdist.wmflabs.org/dist/extensions/NetworkAuth-REL1_35-9f2e881.tar.gz</nowiki></code>
#**(You may need to find the latest or possibly correct version at some point...)
#*Copy it into your Private Wiki:
#**<code>tar -xzf NetworkAuth-REL1_35-9f2e881.tar.gz -C /var/www/privatewiki/extensions</code>
#**(do adjust for the ACTUAL root of your wiki...)
#Create a user named "'''parsoid'''" on your wiki.
#Add the following to <code>LocalSettings.php</code> on your Private Wiki:
#*replace '''127.0.0.1''' with the actual IP address of your Wiki Server

require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'parsoid'
];
<ol start="4">
<li>'''<big>enjoy</big>'''</li>
</ol>

WikiServer - Configuring the Wiki

2020-07-28T07:46:36Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

Internal links will always open in parent window. If you want to change that, follow the next setup instruction...

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

<nowiki>[[This link]] will open in a new window, but not [[this one]], [[or this one]], [[this one either]].</nowiki>

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:45:13Z

Grant: /* Open external links in new window */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

Internal links will always open in parent window. If you want to change that, follow the next setup instruction...

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

<nowiki>[[This link]] will open in a new window, but not [[this one]].</nowiki>

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:44:20Z

Grant: /* Open external links in new window */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==
Internal links will always open in parent window. If you want to change that, follow the next setup instruction...

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

<nowiki>[[This link]] will open in a new window, but not [[this one]].</nowiki>

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:42:40Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

<nowiki>[[This link]] will open in a new window, but not [[this one]].</nowiki>

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:41:44Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

<code>[[This link]] will open in a new window, but not [[this one]].</code>

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:41:21Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

[[This link]] will open in a new window, but not [[this one]].

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:40:57Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering. Place the following below that:

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all INTERNAL links to open in a new window unless specified like below...In the wiki:

[[This link]] will open in a new window, but not [[this one]].

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:38:23Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

The above will default all local links to open in a new window unless specified like below...In the wiki:

[[This link]] will open in a new window, but not [[this one]].

You can change the the default behavior by changing '_self' to '_blank' or vice-versa.

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:33:44Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

In the wiki:
<pre>
[[This link]] will open in a new window, but not [[this one]].
</pre>

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:33:18Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file below the default installed code:

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';
This defaults all EXTERNAL links to a new page, all internal links

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:29:06Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file: 

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

This sets up the extension and creates classes for filtering

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:28:08Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
If you would like to have some links open in the parent window ( '_self' ) and some open in a new window ( '_blank' ), you can identify a link as part of a group (foo or bar in this case) and tell the wiki how the group is to be treated.

Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file: 

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';
$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:25:09Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file: 

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';
$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';</code>

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:24:35Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file: 

require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';</code>

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:23:18Z

Grant: /* Assign how links are opened by 'groups' */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file: 

<code>require_once "$IP/extensions/LinkTarget/LinkTarget.php";

$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

$wgExternalLinkTarget = '_blank';

$wgLinkTargetParentClasses = array( 'foo', 'bar' );

$wgLinkTargetDefault = '_self';</code>

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

WikiServer - Configuring the Wiki

2020-07-28T07:22:45Z

Grant: /* Open external links in new window */

Little snippets of configuration to add to LocalSettings.php...

To add any of them:

*<code>sudo vim /var/www/wiki/LocalSettings.php</code>

==Uploadable File Types==
search for $wgFileExtensions

If you don't find it, you can add it.

on my wiki, it looks like:

<nowiki>#########################################</nowiki>
<nowiki>#</nowiki> Uploadable File Types
<nowiki>#########################################</nowiki>
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf', 'epub', 'ino', 'c', 'cpp', 'h', 'zip', 'gz', 'mp3', 'txt' );

You likely don't want ino, c, cpp, h

==Open external links in new window==

#########################################
# Open external links in new window.
#########################################

$wgExternalLinkTarget = '_blank';

==Assign how links are opened by 'groups'==
Install [[mediawikiwiki:Extension:LinkTarget|Extension:LinkTarget]] by first [[mediawikiwiki:Special:ExtensionDistributor/LinkTarget|downloading]] the file and pasting it into your Extensions folder of your wiki install. Then paste the following into your LocalSettings.php file: 

<code>require_once "$IP/extensions/LinkTarget/LinkTarget.php";
$wgLinkTargetParentClasses = ' /*ENTER SOME CLASSES HERE*/ ';

$wgExternalLinkTarget = '_blank';
$wgLinkTargetParentClasses = array( 'foo', 'bar' );
$wgLinkTargetDefault = '_self';</code>

==InterWiki Links==

#########################################
# InterWiki configuration
#########################################

// To grant sysops permissions to edit interwiki data
$wgGroupPermissions['sysop']['interwiki'] = true;

// To create a new user group that may edit interwiki data
// (bureaucrats can add users to this group)
# $wgGroupPermissions['developer']['interwiki'] = true; // delete the comment indicator # as appropriate
See [[WikiServer - InterWiki Linking|InterWiki Linking]] for a little bit more detail

==There was gonna be a VisualEditor thing here, but wait a month... May be a moot point...==

Ramp

2020-07-17T05:45:27Z

Grant:

A ramp is an angled surface...

This page is a Ramp Page...

Yer welcome Grant.

Thank you. I was wondering how I'd get over it.

Ramp

2020-07-17T05:13:22Z

Grant:

A ramp is an angled surface...

This page is a Ramp Page...

Yer welcome Grant.

<nowiki>Thank you. I was wondering how I'd get over it.</nowiki>

SSL - ESXi

2020-07-02T09:13:13Z

Grant: removed an "either" from the sentence as there is only one in this instance

==Installing manual certs on an ESXi server==
PIKEDOM.COM has some very good [https://pikedom.com/replace-self-signed-certificate-on-esxi-6-7-host/ instructions].

Something to know if you got your certs from certbot:

*The file you're replacing <code>rui.crt</code> with is either <code>cert.pem</code> or <code>fullchain.pem</code> (depending on whether you've set up with one or more than one domain in your certs.
*The file you're replacing <code>rui.key</code> with is <code>privkey.pem</code>.
*Both of the files from certbot may have a number attached to the end of the filename itself.

So...

SSH into the server...

*<code>cd /etc/vmware/ssl</code>
*<code>mv rui.crt orig.rui.crt</code>
*<code>mv rui.key orig.rui.key</code>
*<code>vi rui.crt</code>
**Paste in the content of <code>fullchain.pem</code>
*<code>vi rui.key</code>
**Paste in the content of <code>privkey.pem</code>
*<code>reboot</code>

==Using SCP to install the certs==
You should be able directly install certs on your ESXi server thanks to vmWares bad habit of allowing SSH as root...

'''''<big>THIS HAS NOT YET BEEN FULLY TESTED!</big>'''''

'''You have been warned.'''

*<code>scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/fullchain.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.crt</code>
*<code>scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/privkey.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.key</code>
*<code>ssh root@NAME.DOMAIN.TLD reboot</code>

Of course, you'll replace '''NAME.DOMAIN.TLD''' with the actual name of your server...

OpenVPN Autoconnect - Using NordVPN

2020-06-04T04:55:29Z

Grant:

== Setting up NordVPN in Linux - Mint specifically ==
This is the basics, there is more info at the NordVPN site, [https://support.nordvpn.com/Connectivity/Linux/1325531132/Installing-and-using-NordVPN-on-Debian-Ubuntu-Elementary-OS-and-Linux-Mint.htm Installing in Debian]
To install NordVPN to run in the background of your Linux install, you can either go to their [https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb download page] OR follow the following steps:

1. Open a terminal window and download the appropriate file-

<code>sudo wget -qnc <nowiki>https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb</nowiki></code>

2. Install the package you just downloaded-

<code><nowiki>sudo dpkg -i /pathToFile/nordvpn-release_1.0.0_all.deb</nowiki></code>

Make sure to replace /pathToFile/ with the path to your Downloads folder (or other location where the NordVPN file was downloaded).

Example: sudo dpkg -i ~/Downloads/nordvpn-release_1.0.0_all.deb

You will be asked to enter your root password. Enter it, wait for the package installation to finish, and proceed to the next step.

3. Update the package list-

<code><nowiki>sudo apt update (or sudo apt-get update)</nowiki></code>

4. Install the NordVPN app-

OpenVPN Autoconnect - Using NordVPN

2020-06-04T04:54:36Z

Grant:

== Setting up NordVPN in Linux - Mint specifically ==
This is the basics, there is more info at the NordVPN site, [https://support.nordvpn.com/Connectivity/Linux/1325531132/Installing-and-using-NordVPN-on-Debian-Ubuntu-Elementary-OS-and-Linux-Mint.htm Installing in Debian]
To install NordVPN to run in the background of your Linux install, you can either go to their [https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb download page] OR follow the following steps:

1. Open a terminal window and download the appropriate file-

<code>sudo wget -qnc <nowiki>https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb</nowiki></code>

2. Install the package you just downloaded-

<nowiki>sudo dpkg -i /pathToFile/nordvpn-release_1.0.0_all.deb</nowiki>

Make sure to replace /pathToFile/ with the path to your Downloads folder (or other location where the NordVPN file was downloaded).

Example: sudo dpkg -i ~/Downloads/nordvpn-release_1.0.0_all.deb

You will be asked to enter your root password. Enter it, wait for the package installation to finish, and proceed to the next step.

3. Update the package list-

<nowiki>sudo apt update (or sudo apt-get update)</nowiki>

4. Install the NordVPN app-

OpenVPN Autoconnect - Using NordVPN

2020-06-04T04:54:15Z

Grant:

== Setting up NordVPN in Linux - Mint specifically ==
This is the basics, there is more info at the NordVPN site, [https://support.nordvpn.com/Connectivity/Linux/1325531132/Installing-and-using-NordVPN-on-Debian-Ubuntu-Elementary-OS-and-Linux-Mint.htm Installing in Debian]
To install NordVPN to run in the background of your Linux install, you can either go to their [https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb download page] OR follow the following steps:

1. Open a terminal window and download the appropriate file-

<code>sudo wget -qnc <nowiki>https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb</code>

2. Install the package you just downloaded-

<nowiki>sudo dpkg -i /pathToFile/nordvpn-release_1.0.0_all.deb</nowiki>

Make sure to replace /pathToFile/ with the path to your Downloads folder (or other location where the NordVPN file was downloaded).

Example: sudo dpkg -i ~/Downloads/nordvpn-release_1.0.0_all.deb

You will be asked to enter your root password. Enter it, wait for the package installation to finish, and proceed to the next step.

3. Update the package list-

<nowiki>sudo apt update (or sudo apt-get update)</nowiki>

4. Install the NordVPN app-