Da Nerd Mage Wiki - User contributions [en-gb]

WeeWX Weather Server

2025-09-16T00:54:31Z

Guruofnothing: /* Setting up for EcoWitt gear */

{{{!}} class="wikitable" style="float: right; width: 322px;" border="2"
{{!}}+ Proven on:
{{!}}- < --="" debian="" -->
{{!}} style="text-align: center; width: 60px;" {{!}} [[File:Logo Debian.png{{!}}60px{{!}}link=https://www.debian.org/{{!}}center{{!}}middle{{!}}frameless]]
{{!}} style="text-align: center; width: 40px;" {{!}} 12 (bullseye)
{{!}} Actually, a pretty much all default LXC running under Proxmox. Only non-default item being that I gave it 4 cores.
{{!}}}

This particular set of instructions is based on building a Debian 12 based LXC under Proxmox to handle WeeWX. On my network, I have an existing WebServer & an existing Automation Server. The intent is to have the weather information served up as a web page (Default WeeWX thing...) by the WebServer and also be used by the Automation Server.

There is also a dedicated Database Server which we will be using. (can't possibly do things the easy way...)

(Based on: [https://www.weewx.com/docs/5.1/quickstarts/debian/ WeeWX: Installation on Debian-based systems])

Originally, the old version of this article was done with a much earlier version of WeeWX & our old Accurite weather station. Things have seriously changed since those days...

== Configure apt ==
* <code>sudo apt install -y wget gnupg</code>
* <code>wget -qO - <nowiki>https://weewx.com/keys.html</nowiki> | sudo gpg --dearmor --output /etc/apt/trusted.gpg.d/weewx.gpg</code>
* <code>echo "deb [arch=all] <nowiki>https://weewx.com/apt/python3</nowiki> buster main" | sudo tee /etc/apt/sources.list.d/weewx.list</code>

== Install WeeWX ==

* <code>sudo apt update</code>
* <code>sudo apt install weewx</code>
During this step, you will be asked for all the details about your install.

Fill everything in as best you can, but you can indeed [[#OTHER CUSTOMISATIONS{{!}}change things later]] too.

If you are using weather station hardware that is supported by default, go ahead and select that hardware when asked. In my case, I'm currently running an EcoWitt weather station & that will require a little more effort. For now, I'm selecting '''Simulator''' as my hardware type.

Once the machine has finished churning away at the install, WeeWX will be running. You can verify this by running:

* <code>sudo systemctl status weewx</code>

== Setting up for EcoWitt gear ==
You'll be installing the [https://github.com/hoetzgit/weewx-gw1000 '''Ecowitt Gateway (formerly GW1000) Driver''']

(Something happened to the original developer & all his stuff has vanished from the Interwebs...)

* <code>wget -O weewx-gw1000.zip <nowiki>https://github.com/hoetzgit/weewx-gw1000/archive/master.zip</nowiki></code>
* <code>sudo weectl extension install weewx-gw1000.zip</code>
Verify it can talk to your EcoWitt gateway:

*<code>PYTHONPATH=/usr/share/weewx python3 /etc/weewx/bin/user/gw1000.py --test-driver --ip-address='''device_ip_address'''</code>
(Where you replace '''device_ip_address''' with the actual address of your gateway...)

You should observe loop packets being emitted on a regular basis. Once finished press ctrl-c to exit.

'''Note''': You will only see loop packets and not archive records when running the driver directly. This is because you are seeing output not from WeeWX, but rather directly from the driver.

Configure WeeWX to use the driver:

*<code>sudo weectl station reconfigure --driver=user.gw1000</code>
restart WeeWx

*<code>sudo systemctl restart weewx</code>
('''Note''': I've verified this with '''GW1100''', '''GW1200 and GW3000''' gateways so far...)

== Customising WeeWX ==

=== Broadcasting over MQTT ===
Install paho-mqtt

* <code>sudo apt -y install python3-paho-mqtt</code>

Download the WeeWX MQTT Extension:

* <code>wget -O weewx-mqtt.zip <nowiki>https://github.com/matthewwall/weewx-mqtt/archive/master.zip</nowiki></code>

Install the extension:

* <code>sudo weectl extension install weewx-mqtt.zip</code>

Then edit weewx.conf to configure things for your own MQTT server

* <code>sudo vim /etc/weewx/weewx.conf</code>

Scroll down & find the '''<nowiki>[[MQTT]]</nowiki>''' block, then edit it to suit your network.

<nowiki>[[MQTT]]</nowiki>
server_url = mqtt://'''Machine.Domain.TLD''':1883
topic = '''weather'''
unit_system = METRIC

restart WeeWx

* <code>sudo systemctl restart weewx</code>

=== Connecting to a remote database ===
By default, WeeWX uses a local instance of SQLite.

But, you may wish to archive its data on your primary database.

(Maybe even go nuts & set up multiple weather stations, all sending their data to a central database server...)

==== Setting up the database (MySQL / MariaDB) ====
On the Database Server:

(NOTE: Your Database Server must be configured to allow remote access.)

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

CREATE USER 'weewx'@''''Machine.Domain.TLD'''' IDENTIFIED BY 'weewx';
CREATE DATABASE weewx;
GRANT select, update, create, delete, insert, drop ON weewx.* TO weewx@''''Machine.Domain.TLD'''';

('''Machine.Domain.TLD''', of course, being the address of your WeeWX Server...)

==== Configuring WeeWX to use this database ====
*<code>sudo vi /etc/weewx/weewx.conf</code>

in <nowiki>[[wx_binding]]</nowiki>

change

<code>database = archive_sqlite</code>

to

<code>database = archive_mysql</code>

in <nowiki>[[MySQL]]</nowiki>

change

<code>host = localhost</code>

to

<code>host = '''Machine.Domain.TLD'''</code>

('''Machine.Domain.TLD''', of course, being the address of your Database Server...)

restart WeeWx

* <code>sudo systemctl restart weewx</code>

=== Making the weather visible via Web Browser ===
There are 3 options for locally serving up the weather as HTML...

==== 1: Install a web server on the same machine (or VM...or LXC...) ====

Install your choice of web server and simply point the root at '''/var/www/html/weewx'''

==== 2: Use FTP to upload to your existing WebServer ====

(Your Web Server will need to have FTP enabled...)

*<code>sudo vi /etc/weewx/weewx.conf</code>

Find the <nowiki>[[FTP]]</nowiki> block & edit it to suit.

<nowiki>[StdReport]</nowiki>
<nowiki>[[FTP]]</nowiki>
skin = Ftp
enable = true
server = '''Machine.Domain.TLD'''
path = /var/www/html/weewx
user = '''USERNAME'''
password = '''PASSWORD'''

==== 3: Use RSYNC to upload to your existing WebServer ====

(You will need to set up passwordless SSH between this machine & your web server...)

*<code>sudo vi /etc/weewx/weewx.conf</code>

Find the <nowiki>[[RSYNC]]</nowiki> block & edit it to suit.

<nowiki>[StdReport]</nowiki>
<nowiki>[[RSYNC]]</nowiki>
skin = Rsync
enable = true
server = '''Machine.Domain.TLD'''
path = /var/www/html/weewx
user = '''USERNAME'''

(Make sure your chosen user has write permissions...)

=== OTHER CUSTOMISATIONS ===
There is a configuration file at:
* <code>/etc/weewx/weewx.conf</code>
that holds most (if not all) of the little details & tweaks for your weather server.

==Administration==
Checking status:
* <code>sudo systemctl status weewx</code>

Starting:
* <code>sudo systemctl start weewx</code>

Stopping:
* <code>sudo systemctl stop weewx</code>

Restarting:
* <code>sudo systemctl restart weewx</code>

Watching the system log
* <code>sudo journalctl -u weewx</code>

* <code></code>

Server Building

2025-04-27T05:09:36Z

Guruofnothing:

"The cloud is awesome... Until you get a sunny day." --Tinker 2020

This section is slowly being moved over from my [[TinkerWiki:SBN - Building Notes{{!}}General Wiki]]. Please be patient.

= WEB Servers =
*[[Building Web Servers]]
*[[Building Wiki Servers{{!}}Wiki Servers]]

= Automation Servers =
*[[Automation - MQTT{{!}}MQTT]]
*[[Automation - Node-Red{{!}}Node-Red]]

= Database Servers =
* [[Database - mySQL{{!}}mySQL]]
* [[Database - MariaDB{{!}}MariaDB]]
* [[Database - InfluxDB{{!}}InfluxDB]]
* [[Database - Grafana{{!}}Grafana]]

= Download Servers =

* [[VPN Setup]]
* [[Torrenting Server]]
** Use [[Transmission-Remote]] to interact with the server
*** (on Linux Mint, <code>apt install transmission-remote-gtk</code>)
* [[YTDL Server]]
** ([[TinkerWiki:DownloadServer - Youtube{{!}}Old Version]])

= File and Storage Servers =
* [[Building a Storage Server{{!}}Building a Storage Server]]
** [[Setting up NFS for file sharing{{!}}NFS]]
** [[Installing Samba from the command line{{!}}SMB]]
** [[FTP Serving{{!}}FTP]]
** [[tFTP Serving{{!}}tFTP]]
** [[Cloud Servers - Syncthing{{!}}Syncthing]] (maybe for backups?)

= "Cloud" Servers =
* [[Cloud Servers - NextCloud{{!}}NextCloud]]
** A note: As the current Android app release is massively broken, I'm not using this until that's fixed...
* [[Cloud Servers - Syncthing{{!}}Syncthing]]

= Media Servers =
* Using Plex
* Using Emby
* Using [[Mediaserver - Jellyfin{{!}}Jellyfin]] (WIP)

= Specialised Servers =
* [[PfSense{{!}}pfSense]] (Yes, it's actually a router/firewall/etc... But isn't that really just a rather specialised sort of server?)
* [[SBC - LogicalDOC{{!}}LogicalDOC]] Document Management Server
* [[RustDesk{{!}}RustDesk]] An open source TeamViewer and AnyDesk alternative with a self-hosted server option
* WeeWX Weather Server
** MQTT
** Web Site Upload
** Acurite Weather Station
** EcoWitt Ecosystem
[[Category:ServerBuilding]]

RustDesk

2025-04-27T05:05:33Z

Guruofnothing: Created page with "==== RUSTDESK ==== Go to RustDesk.com and download/install the appropriate flavor for your OS. ===== Local LAN Use - ===== * In the main screen next to the desktop ID, click the three dots. * Under 'Security', Unlock the panel and check the last box that says 'Enable Remote Configuration Modification'. This allows you to make changes to this computers RustDesk settings from any computer you log into it from. * Scroll down to 'Password' and select 'Use Permanent Pas..."

==== RUSTDESK ====
Go to RustDesk.com and download/install the appropriate flavor for your OS.

===== Local LAN Use - =====

* In the main screen next to the desktop ID, click the three dots.
* Under 'Security', Unlock the panel and check the last box that says 'Enable Remote Configuration Modification'. This allows you to make changes to this computers RustDesk settings from any computer you log into it from.
* Scroll down to 'Password' and select 'Use Permanent Password'. Give it a password for access. This will be the password you use to log in when connecting.
* Scroll down to 'Security' and check 'Enable Direct IP Access' box. This allows you to go direct to the box instead of through a server.
* Go to the left panel again and select the 'Display' tab
* Select 'Scale Adaptive'. If this is not checked, unless the screens of the two systems are identical, it does some very annoying scrolling.
** Of interest: The main system I log into remotely has a 60" screen and I access it from a laptop regularly. If 'Scale Original' is left selected, the laptop screen only displays 1/8th of the screen and you have to drag the screen around to see the whole thing. You will want to select adaptive...

Now to do a direct connection - Type the LAN address of the target machine into the 'Control Remote Desktop' box and hit connect. Once you have logged in to a remote, you can select it from the box below just like in AD or TV and rename it for your future connections.

===== WAN Use - =====
You can do the basic install on your machines and use it like AnyDesk or TeamViewer and it is in fact free to use but has no support at all with the exception of the forums but that help doesn't come from the developers. They do have paid PRO plans should you wish to go that way. However, they also have a self-hosted server that you can set up so you are not relying on their server which is functional but they claim faster speeds from a self-hosted server. There are MANY different things that will affect your install like whether or not you have a firewall set up, how you route things or whatever so I won't elaborate on the install. You can [https://rustdesk.com/docs/en/self-host/ go to their site] for more info or I would suggest watching both of these videos for more details -

https://www.youtube.com/watch?v=5WmoLqPkn98

https://www.youtube.com/watch?v=FIEcTNjFZNA

The second video explains pretty clearly how it all works.

Cloud Servers - Syncthing

2025-01-29T03:23:41Z

Guruofnothing: /* Linux (LMDE6) */

This WIP is based on setting up on a Debian based LXC.

= Links: =
* [https://syncthing.net/ Web Site]
* [https://docs.syncthing.net/index.html Documentation]
* [https://github.com/syncthing GitHub]

= Installing Syncthing =

Really, Syncthing is more of a peer-to-peer thing. So the server & client are the same thing. Which it is depends on how you're using it.

== Linux (LMDE6) ==

Add the release PGP keys:
* <code>sudo mkdir -p /etc/apt/keyrings</code>
* <code>sudo curl -L -o /etc/apt/keyrings/syncthing-archive-keyring.gpg <nowiki>https://syncthing.net/release-key.gpg</nowiki></code>
Add the "stable" channel to your APT sources:
* <code>echo "deb [signed-by=/etc/apt/keyrings/syncthing-archive-keyring.gpg] <nowiki>https://apt.syncthing.net/</nowiki> syncthing stable" {{!}} sudo tee /etc/apt/sources.list.d/syncthing.list</code>
Update and install syncthing:
* <code>sudo apt-get update</code>
* <code>sudo apt-get install syncthing</code>
If you need access to the UI from anywhere on your network other than localhost:
* <code>vi ~/.local/state/syncthing/config.xml</code>
** Change <nowiki><address> inside <gui></nowiki> from '''0.0.0.0:8384''' to '''0.0.0.0:8384''' (line 55)
* '''(Note, this file won't actually exist until the first time you run Syncthing MANUALLY...)'''
To manually start it
* <code>syncthing</code>

== Set up as a SYSTEM service ==

This means Syncthing will always run when the machine is running.

Based on configuring it for a regular user.

(Replace “'''myuser'''” with the actual Syncthing user after the @:)

* <code>sudo systemctl enable syncthing@'''myuser'''.service</code>
* <code>sudo systemctl start syncthing@'''myuser'''.service</code>

== Set up as a USER service ==

This means Syncthing will start when the user logs into the machine.

* <code>systemctl --user enable syncthing.service</code>
* <code>systemctl --user start syncthing.service</code>

(oddly, while this shuts down Syncthing when you log out after connecting via SSH, it doesn't seem to shut it down if you log out of the GUI...)

== Android ==

Pretty simple, search for '''Syncthing''' in the [https://play.google.com/store/apps/details?id=com.nutomic.syncthingandroid Play Store] (or through [https://f-droid.org/packages/com.nutomic.syncthingandroid/ F-Droid]).

== Windows ==

[https://github.com/Bill-Stewart/SyncthingWindowsSetup/ Syncthing Windows Setup]: a lightweight yet full-featured Windows installer

== macOS ==

[https://github.com/syncthing/syncthing-macos/releases/latest syncthing-macos]: macOS application bundle

== Synology NAS ==

Open Package Center

Click Settings and click Package Sources

Add a source

Put SynoCommunity in the NAME box and https://packages.synocommunity.com/ in the SOURCE box

Click OK

There will now be a Community tab in the left pane

Click that and find the Syncthing package and install it

= To Be Done =

* figure out proper TLS
* figure out multi-user
* correct NAT/firewall settings

Cloud Servers - Syncthing

2025-01-29T03:23:02Z

Guruofnothing:

This WIP is based on setting up on a Debian based LXC.

= Links: =
* [https://syncthing.net/ Web Site]
* [https://docs.syncthing.net/index.html Documentation]
* [https://github.com/syncthing GitHub]

= Installing Syncthing =

Really, Syncthing is more of a peer-to-peer thing. So the server & client are the same thing. Which it is depends on how you're using it.

== Linux (LMDE6) ==

Add the release PGP keys:
* <code>sudo mkdir -p /etc/apt/keyrings</code>
* <code>sudo curl -L -o /etc/apt/keyrings/syncthing-archive-keyring.gpg <nowiki>https://syncthing.net/release-key.gpg</nowiki></code>
Add the "stable" channel to your APT sources:
* <code>echo "deb [signed-by=/etc/apt/keyrings/syncthing-archive-keyring.gpg] <nowiki>https://apt.syncthing.net/</nowiki> syncthing stable" {{!}} sudo tee /etc/apt/sources.list.d/syncthing.list</code>
Update and install syncthing:
* <code>sudo apt-get update</code>
* <code>sudo apt-get install syncthing</code>
If you need access to the UI from anywhere on your network other than localhost:
* <code>vi ~/.local/state/syncthing/config.xml</code>
** Change <nowiki><address> inside <gui></nowiki> from '''0.0.0.0:8384''' to '''0.0.0.0:8384''' (line 55)
* '''(Note, this file won't actually exist until the first time you run Syncthing MANUALLY...)'''
* <code>syncthing</code>
== Set up as a SYSTEM service ==

This means Syncthing will always run when the machine is running.

Based on configuring it for a regular user.

(Replace “'''myuser'''” with the actual Syncthing user after the @:)

* <code>sudo systemctl enable syncthing@'''myuser'''.service</code>
* <code>sudo systemctl start syncthing@'''myuser'''.service</code>

== Set up as a USER service ==

This means Syncthing will start when the user logs into the machine.

* <code>systemctl --user enable syncthing.service</code>
* <code>systemctl --user start syncthing.service</code>

(oddly, while this shuts down Syncthing when you log out after connecting via SSH, it doesn't seem to shut it down if you log out of the GUI...)

== Android ==

Pretty simple, search for '''Syncthing''' in the [https://play.google.com/store/apps/details?id=com.nutomic.syncthingandroid Play Store] (or through [https://f-droid.org/packages/com.nutomic.syncthingandroid/ F-Droid]).

== Windows ==

[https://github.com/Bill-Stewart/SyncthingWindowsSetup/ Syncthing Windows Setup]: a lightweight yet full-featured Windows installer

== macOS ==

[https://github.com/syncthing/syncthing-macos/releases/latest syncthing-macos]: macOS application bundle

== Synology NAS ==

Open Package Center

Click Settings and click Package Sources

Add a source

Put SynoCommunity in the NAME box and https://packages.synocommunity.com/ in the SOURCE box

Click OK

There will now be a Community tab in the left pane

Click that and find the Syncthing package and install it

= To Be Done =

* figure out proper TLS
* figure out multi-user
* correct NAT/firewall settings

Cloud Servers - Syncthing

2025-01-09T19:37:59Z

Guruofnothing: /* Synology NAS */

This WIP is based on setting up on a Debian based LXC.

= Links: =
* [https://syncthing.net/ Web Site]
* [https://docs.syncthing.net/index.html Documentation]
* [https://github.com/syncthing GitHub]

= Installing Syncthing =

Really, Syncthing is more of a peer-to-peer thing. So the server & client are the same thing. Which it is depends on how you're using it.

== Linux (LMDE6) ==

Add the release PGP keys:
* <code>sudo mkdir -p /etc/apt/keyrings</code>
* <code>sudo curl -L -o /etc/apt/keyrings/syncthing-archive-keyring.gpg <nowiki>https://syncthing.net/release-key.gpg</nowiki></code>
Add the "stable" channel to your APT sources:
* <code>echo "deb [signed-by=/etc/apt/keyrings/syncthing-archive-keyring.gpg] <nowiki>https://apt.syncthing.net/</nowiki> syncthing stable" {{!}} sudo tee /etc/apt/sources.list.d/syncthing.list</code>
Update and install syncthing:
* <code>sudo apt-get update</code>
* <code>sudo apt-get install syncthing</code>

If you need access to the UI from anywhere on your network other than localhost:
* <code>vi ~/.local/state/syncthing/config.xml</code>
** Change <nowiki><address> inside <gui></nowiki> from '''0.0.0.0:8384''' to '''0.0.0.0:8384''' (line 55)
* (Note, this file won't actually exist until the first time you run Syncthing...)

== Set up as a SYSTEM service ==

This means Syncthing will always run when the machine is running.

Based on configuring it for a regular user.

(Replace “'''myuser'''” with the actual Syncthing user after the @:)

* <code>sudo systemctl enable syncthing@'''myuser'''.service</code>
* <code>sudo systemctl start syncthing@'''myuser'''.service</code>

== Set up as a USER service ==

This means Syncthing will start when the user logs into the machine.

* <code>systemctl --user enable syncthing.service</code>
* <code>systemctl --user start syncthing.service</code>

(oddly, while this shuts down Syncthing when you log out after connecting via SSH, it doesn't seem to shut it down if you log out of the GUI...)

== Android ==

Pretty simple, search for '''Syncthing''' in the [https://play.google.com/store/apps/details?id=com.nutomic.syncthingandroid Play Store] (or through [https://f-droid.org/packages/com.nutomic.syncthingandroid/ F-Droid]).

== Windows ==

[https://github.com/Bill-Stewart/SyncthingWindowsSetup/ Syncthing Windows Setup]: a lightweight yet full-featured Windows installer

== macOS ==

[https://github.com/syncthing/syncthing-macos/releases/latest syncthing-macos]: macOS application bundle

== Synology NAS ==

Open Package Center

Click Settings and click Package Sources

Add a source

Put SynoCommunity in the NAME box and https://packages.synocommunity.com/ in the SOURCE box

Click OK

There will now be a Community tab in the left pane

Click that and find the Syncthing package and install it

= To Be Done =

* figure out proper TLS
* figure out multi-user
* correct NAT/firewall settings

Cloud Servers - Syncthing

2025-01-09T19:37:32Z

Guruofnothing:

This WIP is based on setting up on a Debian based LXC.

= Links: =
* [https://syncthing.net/ Web Site]
* [https://docs.syncthing.net/index.html Documentation]
* [https://github.com/syncthing GitHub]

= Installing Syncthing =

Really, Syncthing is more of a peer-to-peer thing. So the server & client are the same thing. Which it is depends on how you're using it.

== Linux (LMDE6) ==

Add the release PGP keys:
* <code>sudo mkdir -p /etc/apt/keyrings</code>
* <code>sudo curl -L -o /etc/apt/keyrings/syncthing-archive-keyring.gpg <nowiki>https://syncthing.net/release-key.gpg</nowiki></code>
Add the "stable" channel to your APT sources:
* <code>echo "deb [signed-by=/etc/apt/keyrings/syncthing-archive-keyring.gpg] <nowiki>https://apt.syncthing.net/</nowiki> syncthing stable" {{!}} sudo tee /etc/apt/sources.list.d/syncthing.list</code>
Update and install syncthing:
* <code>sudo apt-get update</code>
* <code>sudo apt-get install syncthing</code>

If you need access to the UI from anywhere on your network other than localhost:
* <code>vi ~/.local/state/syncthing/config.xml</code>
** Change <nowiki><address> inside <gui></nowiki> from '''0.0.0.0:8384''' to '''0.0.0.0:8384''' (line 55)
* (Note, this file won't actually exist until the first time you run Syncthing...)

== Set up as a SYSTEM service ==

This means Syncthing will always run when the machine is running.

Based on configuring it for a regular user.

(Replace “'''myuser'''” with the actual Syncthing user after the @:)

* <code>sudo systemctl enable syncthing@'''myuser'''.service</code>
* <code>sudo systemctl start syncthing@'''myuser'''.service</code>

== Set up as a USER service ==

This means Syncthing will start when the user logs into the machine.

* <code>systemctl --user enable syncthing.service</code>
* <code>systemctl --user start syncthing.service</code>

(oddly, while this shuts down Syncthing when you log out after connecting via SSH, it doesn't seem to shut it down if you log out of the GUI...)

== Android ==

Pretty simple, search for '''Syncthing''' in the [https://play.google.com/store/apps/details?id=com.nutomic.syncthingandroid Play Store] (or through [https://f-droid.org/packages/com.nutomic.syncthingandroid/ F-Droid]).

== Windows ==

[https://github.com/Bill-Stewart/SyncthingWindowsSetup/ Syncthing Windows Setup]: a lightweight yet full-featured Windows installer

== macOS ==

[https://github.com/syncthing/syncthing-macos/releases/latest syncthing-macos]: macOS application bundle

== Synology NAS ==
Open Package Center
Click Settings and click Package Sources
Add a source
Put SynoCommunity in the NAME box and https://packages.synocommunity.com/ in the SOURCE box
Click OK
There will now be a Community tab in the left pane
Click that and find the Syncthing package and install it

= To Be Done =

* figure out proper TLS
* figure out multi-user
* correct NAT/firewall settings

Database - Python-Poetry

2024-09-22T03:48:02Z

Guruofnothing:

Python-Poetry is a dependencies manager for Python

* <code>curl -sSL https://install.python-poetry.org {{!}} python3 -</code>

Once the installation completes, Poetry will prompt you to add its bin directory to your PATH in order to enable the use of poetry in your command line. On Ubuntu with Bash, this can be done by opening the ~/.bashrc file using nano or your preferred text editor:

* <code>nano ~/.bashrc</code>

Now add the following lines at the end of the page - MAKE SURE TO CHANGE THE [YOUR DIRECTORY HERE] TO YOUR LOCAL USER DIRECTORY

* <code>export PATH="/home/[YOUR DIRECTORY HERE]/.local/bin:$PATH"</code>

Apply the changes to your current session

* <code>source ~/.bashrc</code>

Then verify that you are good to go

* <code>poetry --version</code>

Database - Python-Poetry

2024-09-22T02:59:43Z

Guruofnothing:

Python-Poetry is a dependencies manager for Python

* <code>curl -sSL https://install.python-poetry.org {{!}} python3 -</code>
* <code></code>

Database - Python-Poetry

2024-09-22T02:58:45Z

Guruofnothing:

Python-Poetry is a dependencies manager for Python

* <code>curl -sSL https://install.python-poetry.org | python3 -</code>

Database - Python-Poetry

2024-09-22T02:58:20Z

Guruofnothing:

Python-Poetry is a dependencies manager for Python

* <code>curl -sSL https://install.python-poetry.org | python3 -</code>Installs Python-Poetry dependency manager

Database - Python-Poetry

2024-09-22T02:57:42Z

Guruofnothing: Created page with "Python-Poetry is a dependencies manager for Python * <code>curl -sSL https://install.python-poetry.org {{!}} python3 -</code> "

Python-Poetry is a dependencies manager for Python

* <code>curl -sSL https://install.python-poetry.org {{!}} python3 -</code>

Building Wiki Servers

2023-12-14T22:54:50Z

Guruofnothing: /* Unpack MediaWiki */

Building Wiki Servers

2023-12-14T22:54:31Z

Guruofnothing: /* Download MediaWiki */

Setting up NFS for file sharing

2023-12-14T00:34:09Z

Guruofnothing: /* Make your mount(s) persistant */

{{{!}} class="wikitable" style="float: right; width: 322px;" border="2"
{{!}}+ Proven on:
{{!}}- --="" debian=""
{{!}} style="text-align: center; width: 60px;" {{!}} [[File:Logo Debian.png{{!}}60px{{!}}link=https://www.debian.org/{{!}}center{{!}}middle{{!}}frameless]]
{{!}} style="text-align: center; width: 40px;" {{!}} 11 (bullseye)
{{!}} (This includes LMDE5, Proxmox, OMV...)
{{!}}- --="" winderp=""
{{!}} style="text-align: center; width: 60px;" {{!}} [[File:Logo Windows.png{{!}}60px{{!}}link=https://www.microsoft.com/en-gb/windows{{!}}center{{!}}middle{{!}}frameless]]
{{!}} style="text-align: center; width: 40px;" {{!}} 10
{{!}} (For the client side anyhow...)
{{!}}-
{{!}} style="text-align: center; width: 60px;" colspan="3" {{!}} [[typographic conventions{{!}}A little note about typographic conventions you'll see here]]
{{!}}}
(A note about [[PVE LXC_Containers#Adding_NFS_to_an_LXC{{!}}LXCs & NFS]])

== Install NFS Server ==

* <code>sudo apt install nfs-kernel-server</code>

== Configure NFS Server ==

* <code>sudo vi /etc/exports</code>
Add/edit:

'''/PATH/TO/BE/SHARED''' *(rw,async,no_root_squash,no_subtree_check)
For the changes to take effect, export and start NFS service.
* <code>sudo exportfs -a</code>
* <code>sudo /etc/init.d/nfs-kernel-server start</code>
Pretty simple...

=== A bit about re-sharing ===
Sometimes, you may want to share something that you've actually mounted from an NFS share on another machine...

A couple of things are different in this case.

First, you need to ensure that the mounts are done BEFORE you start the NFS server.

* <code>sudo vi /etc/init.d/nfs-kernel-server</code>
and add:

##########################
echo "Starting out by making sure EVERYTHING is mounted..."
/usr/bin/mount -a
echo "Really..."
echo "This is NOT the right place to do this..."
echo "But, init.d kinda sucks..."
##########################
right near the start.

Then you need to provide an fsid entry (with a unique number) for each export.

'''/PATH/TO/BE/SHARED''' *(rw,async,no_root_squash,no_subtree_check''',fsid=1010''')

'''AND''' it '''STILL''' doesn't start at boot!!!

But, you can force it to start after booting by logging into the machine & telling it:

* <code>sudo /etc/init.d/nfs-kernel-server start</code>

== Connecting to the NFS Server ==
=== From Linux ===
You'll need NFS installed
* <code>sudo apt install nfs-common</code>
or
* <code>sudo apt install nfs-kernel-server</code>
Then you can check what's shared from any particular machine:
* <code>showmount -e '''[SERVERNAME or ADDRESS]'''</code>
** (requires sudo on Debian...)
will show you what's shared from a machine

==== Setting up & mounting a share ====
* <code>sudo mkdir -p '''/PATH/TO/MOUNT/SHARE'''</code>
* <code>sudo mount '''[SERVERNAME or ADDRESS]''':'''/PATH/TO/BE/SHARED''' '''/PATH/TO/MOUNT/SHARE'''</code>
Better yet tho...
* <code>sudo vi /etc/fstab</code>
& add an entry:
'''[SERVERNAME or ADDRESS]''':'''/PATH/TO/BE/SHARED''' '''/PATH/TO/MOUNT/SHARE''' nfs rw,user,exec 0 0
Then, you can mount anything listed in fstab but not yet mounted
* <code>sudo mount -a</code>

=== From Windows (Win10) ===
==== (Tentative Working Notes) ====
'''It has come to my attention... PRO & Enterprise only... Sorry'''
===== Enabling NFS =====

First things first... You need to know the [https://www.cyberciti.biz/faq/understanding-etcpasswd-file-format/ UID and GID] of the user on the intended share so that you can emulate it.

* <code class="mwt-code" >cat /etc/passwd</code> 

Find the user that is responsible for the share and grab that number. In this case we will use '''tinker''' (so '1000' & '1000') but it could be anything. In this example...

<code>tinker:x:1000:1000::/home/tinker:/bin/sh</code>

'''In an Admin Powershell window:'''

Turn on NFS

*<code>Enable-WindowsOptionalFeature -FeatureName ServicesForNFS-ClientOnly, ClientForNFS-Infrastructure -Online -NoRestart</code>
Set up anonymous credentials to match the credentials of a user with full access to the NFS share from a Linux viewpoint...

Make any servers you connect to think you're somebody important

*<code>New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousUID -Value '''1000''' -PropertyType "DWord"</code>
*<code>New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousGID -Value '''1000'''  -PropertyType "DWord"</code>
The "'''AnonymousUID'''" & "'''AnonymousGID'''" Value's are the UID & GID of a user on the server with appropriate permissions... (In this case, the first user created on the server(s)) and for this purpose, they do not need to be changed. Leave them anonymous. Make sure that the '''1000''' is the actual ID you retrieved.

WARNING: If you copy/paste the two lines above, you will find that you can't mount the share (unless you are just lucky and the ID is actually 1000... go buy a lottery ticket). To fix it, you will have to do a <code class="mwt-code" >regedit</code> and change the DWORD value (in hex) to the correct number. You are on your own for that.

'''Reboot the computer'''

===== Mount the drive(s) =====

'''In a regular command shell:'''

*EXAMPLE FORMAT - mount -o nolock \\IP_or_FQDN_OF_SHARE\\Directory_Of_Share\Sub_Folder [ DRIVE TO MAP IT TO:<code>]</code>
*<code>mount -o nolock \\TinkerData.tinkernet.ca\home\tinker\Documents D:</code>
*<code>mount -o nolock \\Warehouse.tinkernet.ca\mnt\Space_1\Pix P:</code>
You can map to a folder on your machine as well if you want it somewhere like the desktop instead(WIP)

EVERY TIME the machine is rebooted, mount the drives... Again...

===== Make your mount(s) persistant =====

([https://dop-amine.com/posts/persistent-nfs-windows/ Source])

Open the Startup folder by opening the Run tool and entering <code>shell:startup</code>

Create <code>nfsmount.bat</code> file in that directory with the mount command used above.

If you use Notepad to create that file, make sure to save it as 'All Files' instead of '.txt.'. Otherwise it will be 'nfsmount.bat.txt' and will not work.

This file will be read on startup and will automatically mount the NFS Share.

== NFS management From the GUI (sort of...) ==

[https://github.com/Philippe734/Simple.NFS.GUI Simple NFS GUI for Linux] is an option.

Installation can be a bit awkward & it's far from polished tho...

Installing: (On Debian-based systems)

* <code>sudo apt install gambas3</code>
** (original instructions attempt to do this via a PPA... Good luck with that...)
* <code>wget <nowiki>https://github.com/Philippe734/Simple.NFS.GUI/raw/master/Linux/1.0.17/simple-nfs-gui_1.0.17-0ubuntu1_all.deb -P ~</nowiki></code>
** To download the package
* <code>sudo dpkg -i ~/simple-nfs-gui_1.0.17-0ubuntu1_all.deb</code>
** Then install it
Once it's installed, you need to run it as root:
* <code>sudo -H Simple_NFS_GUI</code>
Kind of a [https://www.linuxuprising.com/2018/11/easy-nfs-share-setup-in-ubuntu-linux.html guide to using it]
=== Other Options ===
* [https://www.webmin.com/ Webmin] has full support for configuring NFS...

== TBD ==

* Learn what flags do what in '''/etc/exports'''
* Look into automounting (including graceful failure modes)
* Work up some instructions for other non-Linux systems. (Synology, Kodi, Mac)

== Some Links ==

* [https://www.cyberciti.biz/faq/how-to-ubuntu-nfs-server-configuration-howto/ Ubuntu Linux NFS Server installation and Configuration]
* The Geek Diary: [https://www.thegeekdiary.com/understanding-the-etc-exports-file/ Understanding the /etc/exports File]
* [https://linux.die.net/man/8/exportfs exportfs(8) - Linux man page]
* [https://linux.die.net/man/5/exports exports(5) - Linux man page]
* [https://linux.die.net/man/8/mount mount(8) - Linux man page] 
* [https://linux.die.net/man/5/fstab fstab(5) - Linux man page]
[[Category:Linux]]
[[Category: WIP]]

Setting up NFS for file sharing

2023-12-08T23:11:13Z

Guruofnothing:

{{{!}} class="wikitable" style="float: right; width: 322px;" border="2"
{{!}}+ Proven on:
{{!}}- --="" debian=""
{{!}} style="text-align: center; width: 60px;" {{!}} [[File:Logo Debian.png{{!}}60px{{!}}link=https://www.debian.org/{{!}}center{{!}}middle{{!}}frameless]]
{{!}} style="text-align: center; width: 40px;" {{!}} 11 (bullseye)
{{!}} (This includes LMDE5, Proxmox, OMV...)
{{!}}- --="" winderp=""
{{!}} style="text-align: center; width: 60px;" {{!}} [[File:Logo Windows.png{{!}}60px{{!}}link=https://www.microsoft.com/en-gb/windows{{!}}center{{!}}middle{{!}}frameless]]
{{!}} style="text-align: center; width: 40px;" {{!}} 10
{{!}} (For the client side anyhow...)
{{!}}-
{{!}} style="text-align: center; width: 60px;" colspan="3" {{!}} [[typographic conventions{{!}}A little note about typographic conventions you'll see here]]
{{!}}}
(A note about [[PVE LXC_Containers#Adding_NFS_to_an_LXC{{!}}LXCs & NFS]])

== Install NFS Server ==

* <code>sudo apt install nfs-kernel-server</code>

== Configure NFS Server ==

* <code>sudo vi /etc/exports</code>
Add/edit:

'''/PATH/TO/BE/SHARED''' *(rw,async,no_root_squash,no_subtree_check)
For the changes to take effect, export and start NFS service.
* <code>sudo exportfs -a</code>
* <code>sudo /etc/init.d/nfs-kernel-server start</code>
Pretty simple...

=== A bit about re-sharing ===
Sometimes, you may want to share something that you've actually mounted from an NFS share on another machine...

A couple of things are different in this case.

First, you need to ensure that the mounts are done BEFORE you start the NFS server.

* <code>sudo vi /etc/init.d/nfs-kernel-server</code>
and add:

##########################
echo "Starting out by making sure EVERYTHING is mounted..."
/usr/bin/mount -a
echo "Really..."
echo "This is NOT the right place to do this..."
echo "But, init.d kinda sucks..."
##########################
right near the start.

Then you need to provide an fsid entry (with a unique number) for each export.

'''/PATH/TO/BE/SHARED''' *(rw,async,no_root_squash,no_subtree_check''',fsid=1010''')

'''AND''' it '''STILL''' doesn't start at boot!!!

But, you can force it to start after booting by logging into the machine & telling it:

* <code>sudo /etc/init.d/nfs-kernel-server start</code>

== Connecting to the NFS Server ==
=== From Linux ===
You'll need NFS installed
* <code>sudo apt install nfs-common</code>
or
* <code>sudo apt install nfs-kernel-server</code>
Then you can check what's shared from any particular machine:
* <code>showmount -e '''[SERVERNAME or ADDRESS]'''</code>
** (requires sudo on Debian...)
will show you what's shared from a machine

==== Setting up & mounting a share ====
* <code>sudo mkdir -p '''/PATH/TO/MOUNT/SHARE'''</code>
* <code>sudo mount '''[SERVERNAME or ADDRESS]''':'''/PATH/TO/BE/SHARED''' '''/PATH/TO/MOUNT/SHARE'''</code>
Better yet tho...
* <code>sudo vi /etc/fstab</code>
& add an entry:
'''[SERVERNAME or ADDRESS]''':'''/PATH/TO/BE/SHARED''' '''/PATH/TO/MOUNT/SHARE''' nfs rw,user,exec 0 0
Then, you can mount anything listed in fstab but not yet mounted
* <code>sudo mount -a</code>

=== From Windows (Win10) ===
==== (Tentative Working Notes) ====
'''It has come to my attention... PRO & Enterprise only... Sorry'''
===== Enabling NFS =====

First things first... You need to know the ID of the user on the intended share so that you can emulate it.

<code class="mwt-code" >cat /etc/passwd</code> 

Find the user that is responsible for the share and grab that number. In this case we will use '1000' but it could be anything. In this example...

<nowiki>tinker:x:1000:100::/home/tinker:/bin/sh</nowiki>
''''''
'''In an Admin Powershell window:'''

Turn on NFS

*<code>Enable-WindowsOptionalFeature -FeatureName ServicesForNFS-ClientOnly, ClientForNFS-Infrastructure -Online -NoRestart</code>
Set up anonymous credentials to match the credentials of a user with full access to the NFS share from a Linux viewpoint...

Make any servers you connect to think you're somebody important

*<code>New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousUID -Value '''1000''' -PropertyType "DWord"</code>
*<code>New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousGID -Value '''1000'''  -PropertyType "DWord"</code>
The "'''AnonymousUID'''" & "'''AnonymousGID'''" Value's are the UID & GID of a user on the server with appropriate permissions... (In this case, the first user created on the server(s)) and for this purpose, they do not need to be changed. Leave them anonymous. Make sure that the '''1000''' is the actual ID you retrieved.

WARNING: If you copy/paste the two lines above, you will find that you can't mount the share (unless you are just lucky and the ID is actually 1000... go buy a lottery ticket). To fix it, you will have to do a <code class="mwt-code" >regedit</code> and change the DWORD value (in hex) to the correct number. You are on your own for that.

'''Reboot the computer'''

===== Mount the drive(s) =====

'''In a regular command shell:'''

*EXAMPLE FORMAT - mount -o nolock \\IP_or_FQDN_OF_SHARE\\Directory_Of_Share\Sub_Folder [ DRIVE TO MAP IT TO:<code>]</code>
*<code>mount -o nolock \\TinkerData.tinkernet.ca\home\tinker\Documents D:</code>
*<code>mount -o nolock \\Warehouse.tinkernet.ca\mnt\Space_1\Pix P:</code>
You can map to a folder on your machine as well if you want it somewhere like the desktop instead(WIP)

EVERY TIME the machine is rebooted, mount the drives... Again...

===== Make your mount(s) persistant =====

([https://dop-amine.com/posts/persistent-nfs-windows/ Source])

Open the Startup folder by opening the Run tool and entering <code>shell:startup</code>

Create <code>nfsmount.bat</code> file in that directory with the mount command used above.

This file will be read on startup and will automatically mount the NFS Share.

== NFS management From the GUI (sort of...) ==

[https://github.com/Philippe734/Simple.NFS.GUI Simple NFS GUI for Linux] is an option.

Installation can be a bit awkward & it's far from polished tho...

Installing: (On Debian-based systems)

* <code>sudo apt install gambas3</code>
** (original instructions attempt to do this via a PPA... Good luck with that...)
* <code>wget <nowiki>https://github.com/Philippe734/Simple.NFS.GUI/raw/master/Linux/1.0.17/simple-nfs-gui_1.0.17-0ubuntu1_all.deb -P ~</nowiki></code>
** To download the package
* <code>sudo dpkg -i ~/simple-nfs-gui_1.0.17-0ubuntu1_all.deb</code>
** Then install it
Once it's installed, you need to run it as root:
* <code>sudo -H Simple_NFS_GUI</code>
Kind of a [https://www.linuxuprising.com/2018/11/easy-nfs-share-setup-in-ubuntu-linux.html guide to using it]
=== Other Options ===
* [https://www.webmin.com/ Webmin] has full support for configuring NFS...

== TBD ==

* Learn what flags do what in '''/etc/exports'''
* Look into automounting (including graceful failure modes)
* Work up some instructions for other non-Linux systems. (Synology, Kodi, Mac)

== Some Links ==

* [https://www.cyberciti.biz/faq/how-to-ubuntu-nfs-server-configuration-howto/ Ubuntu Linux NFS Server installation and Configuration]
* The Geek Diary: [https://www.thegeekdiary.com/understanding-the-etc-exports-file/ Understanding the /etc/exports File]
* [https://linux.die.net/man/8/exportfs exportfs(8) - Linux man page]
* [https://linux.die.net/man/5/exports exports(5) - Linux man page]
* [https://linux.die.net/man/8/mount mount(8) - Linux man page] 
* [https://linux.die.net/man/5/fstab fstab(5) - Linux man page]
[[Category:Linux]]
[[Category: WIP]]

Cloud Servers - NextCloud

2023-11-28T02:18:02Z

Guruofnothing:

Cloud Servers - NextCloud

2023-11-28T02:12:21Z

Guruofnothing: /* Usage behind a proxy (WIP) */

Cloud Servers - NextCloud

2023-11-28T02:06:29Z

Guruofnothing: /* Securing with HTTPS (WIP) */

SSL Certs

2023-11-27T03:23:27Z

Guruofnothing:

== Upcoming fun stuff ==
SSL certs via ClouDNS' '''"Free SSL Certificates"'''

''''''
== Installing Certbot on your machine ==
Certbot now requires that you install it from SNAP.<pre>sudo apt update
sudo apt upgrade
</pre>Install SNAP
<pre>sudo apt install snapd
sudo snap install core; sudo snap refresh core
</pre>Install Certbot
<pre>sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
</pre>
== Certs for Devices not Actually Accessible on the Internet ==
=== Using HTTP challenge ===
(Do this on your primary web/proxy server)
* <code>sudo certbot certonly -d '''MACHINE.DOMAIN.TLD'''</code>
** when it asks... choose option '''1: Apache Web Server plugin'''
** Copy your shiny new cert into place 

=== Using DNS challenge ===
* For each machine
* <code>sudo certbot -d '''MACHINE.DOMAIN.TLD''' --manual --preferred-challenges dns certonly</code>
** Follow the directions about setting up the DNS record & then hit enter
** Copy your shiny new cert into place

==== Stuff still being worked out... ====
* Problem:  Renewal is potentially problematic
** Tho... Apparently, renewal of a manual cert involves [https://community.letsencrypt.org/t/certbot-manual-renew/17789/2 just running the original command again].
*** (every time you run certbot as above, the TXT Record value changes...)
*** one solution might be to use your DNS providers API calls...
*** ooohhh '''--reuse-key'''
* cron job to manage it all

==== If getting certs for a proxied site... ====
You will need to copy the cert files that you acquired over to the proxied site. You do not need Certbot installed on the proxy VM as it isn't required but you will need to create the appropriate folders to copy the certs into. '''SSH into the proxy machine - ''' <pre>cd /etc
sudo mkdir letsencrypt
cd /letsencrypt
sudo mkdir live
cd /etc </pre>Now exit back out to your web server and SCP your cert files from /etc/letsencrypt/live to the folder you created on the proxy machine.
== Certs on an Apache based server ==
From /usr/share/doc/apache2/README.Debian.gz

=== Enabling SSL ===
To enable SSL, type:

*<code>sudo a2ensite default-ssl</code>
*<code>sudo a2enmod ssl</code>
If you want to use self-signed certificates, you should install the ssl-cert package (see below). Otherwise, just adjust the SSLCertificateKeyFile and SSLCertificateFile directives in '/etc/apache2/sites-available/default-ssl.conf' to point to your SSL certificate. Then restart apache:

*<code>sudo systemctl restart apache2</code>
The SSL key file should only be readable by root; the certificate file may be globally readable. These files are read by the Apache parent process which runs as root, and it is therefore not necessary to make the files readable by the www-data user.

==== Getting proper certificates onto the machine ====
Using the instructions at the top of the page, Install SNAP, Install Certbot and grab the certs for your machines that need them. The old way to do this is still on [[TinkerWiki:NetMan - SSL Certs#Getting proper certificates onto the machine{{!}}the TinkerNet Wiki]].

'''[[Now Do A Backup!{{!}}Now Do A Backup!]]'''

[[Category:Network Management]]
[[Category:WebServers]]

SSL Certs

2023-11-27T03:02:35Z

Guruofnothing:

== Upcoming fun stuff ==
SSL certs via ClouDNS' '''"Free SSL Certificates"'''

''''''
== Installing Certbot on your machine ==
Certbot now requires that you install it from SNAP. <pre>sudo apt update
sudo apt upgrade
</pre>Install SNAP<pre>sudo apt install snapd
sudo snap install core; sudo snap refresh core
</pre>Install Certbot<pre>sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
</pre>
== Certs for Devices not Actually Accessible on the Internet ==
=== Using HTTP challenge ===
(Do this on your primary web/proxy server)
* <code>sudo certbot certonly -d '''MACHINE.DOMAIN.TLD'''</code>
** when it asks... choose option '''1: Apache Web Server plugin'''
** Copy your shiny new cert into place

=== Using DNS challenge ===
* For each machine
* <code>sudo certbot -d '''MACHINE.DOMAIN.TLD''' --manual --preferred-challenges dns certonly</code>
** Follow the directions about setting up the DNS record & then hit enter
** Copy your shiny new cert into place

==== Stuff still being worked out... ====
* Problem:  Renewal is potentially problematic
** Tho... Apparently, renewal of a manual cert involves [https://community.letsencrypt.org/t/certbot-manual-renew/17789/2 just running the original command again].
*** (every time you run certbot as above, the TXT Record value changes...)
*** one solution might be to use your DNS providers API calls...
*** ooohhh '''--reuse-key'''
* cron job to manage it all

== Certs on an Apache based server ==
From /usr/share/doc/apache2/README.Debian.gz

=== Enabling SSL ===
To enable SSL, type:

*<code>sudo a2ensite default-ssl</code>
*<code>sudo a2enmod ssl</code>
If you want to use self-signed certificates, you should install the ssl-cert package (see below). Otherwise, just adjust the SSLCertificateKeyFile and SSLCertificateFile directives in '/etc/apache2/sites-available/default-ssl.conf' to point to your SSL certificate. Then restart apache:

*<code>sudo systemctl restart apache2</code>
The SSL key file should only be readable by root; the certificate file may be globally readable. These files are read by the Apache parent process which runs as root, and it is therefore not necessary to make the files readable by the www-data user.

==== Getting proper certificates onto the machine ====
Using the instructions at the top of the page, Install SNAP, Install Certbot and grab the certs for your machines that need them. 

The old way to do this is still on [[TinkerWiki:NetMan - SSL Certs#Getting proper certificates onto the machine{{!}}the TinkerNet Wiki]].

'''[[Now Do A Backup!{{!}}Now Do A Backup!]]'''

[[Category:Network Management]]
[[Category:WebServers]]

Cloud Servers - NextCloud

2023-11-27T02:44:00Z

Guruofnothing: /* Update and Install Nextcloud */

User:Guruofnothing

2023-11-27T02:28:29Z

Guruofnothing: Created page with "This page is all about Grant Reed..."

This page is all about Grant Reed...

Main Page

2022-01-04T04:45:39Z

Guruofnothing:

Welcome to '''Da Nerd Mage Wiki'''!

During construction, you will likely see a lot of broken links.  With any luck, most of them will simply be pages I haven't managed to put in place yet.  Many of these can be found (with a bit of effort) on the [https://wiki.tinkernet.ca/ TinkerNet Wiki].  Others may not actually exist anywhere yet & will appear as I get to them. OTOH...  If it's an external link, maybe something has borked.  [mailto:NerdMage@tinkernow.net Let me know.]..

OR... Bob has struck. That happens sometimes as well. We need a good Bob exterminator.

[[File:Construction-Zone-Obstacle-Course12-2.jpg{{!}}600px{{!}}center{{!}}frameless]]