# Header

Your content here

## Grafana

http://192.168.178.63:3000

admin, admin → borabora

https://www.derekseaman.com/2023/04/home-assistant-installing-grafana-lxc.html

## InfluxDB LXC

http://192.168.178.64:8086

version 2 and Telegraf installed

nano /etc/influxdb/influxdb.conf

nano /etc/telegraf/telegraf.conf

https://www.derekseaman.com/2023/04/home-assistant-installing-influxdb-lxc.html

http://192.168.178.68:8888

If you don’t know the IP of your container type >>ip a

https://www.influxdata.com/downloads/

root, salzbrezel

wget https://dl.influxdata.com/chronograf/releases/chronograf_1.10.2_amd64.deb

homeassistant, savemydata

## Wiki.js LXC

https://tteck.github.io/Proxmox/

http://192.168.178.26:3000/, borabora, boraers@gmail.com

https://wiki.mywiki.com

diagrams can be created by inserting “diagram” from the left panel on Markdown pages

### Backing up all pages on github

how to access the file system of a proxmox container?

https://www.reddit.com/r/Proxmox/comments/fap1wx/beginner_question_where_are_container_filesystems/

find / -size +500M -ls

/var/lib/lxc/103/rootfs/

lvdisplay

/dev/pve/vm-103-disk-0

using github:

https://docs.requarks.io/storage/git

ssh-keygen -t rsa -b 4096

/root/.ssh/id_rsa

Your identification has been saved in /root/.ssh/id_rsa

Your public key has been saved in /root/.ssh/id_rsa.pub

The key fingerprint is:

SHA256:JmrdPXntGuqgopWrbAquqhZIGuy5rdo2vGLr/BHm3k4 root@wikijs

The key's randomart image is:

+---[RSA 4096]----+

| |

| |

|. |

|.o |

|=..o . S |

|o+o .+ + . . . |

|..+o=E. o + o . |

|=**+=. . . + o |

|#@XBo+. .o ... |

+----[SHA256]-----+

>>nano /root/.ssh/id_rsa.pub

https://unix.stackexchange.com/questions/122795/long-line-wrapping-in-nano

!!complicated copy procedure: esc → shift+4 → mar everything with mouse → Alt+6 or right mouse!!

ssh-rsa root@wikijs

TARGET CONFIGURATION

​

Authentication Type

ssh

Use SSH for maximum security.

​

Repository URI

git@github.com:BoraEr90/WikiJS.git

Git-compliant URI (e.g. git@github.com:org/repo.git for ssh, https://github.com/org/repo.git for basic)

​

Branch

main

The branch to use during pull / push

​

SSH Private Key Mode

path

SSH Authentication Only - The mode to use to load the private key. Fill in the corresponding field below.

​

A - SSH Private Key Path

/root/.ssh/id_rsa

SSH Authentication Only - Absolute path to the key. The key must NOT be passphrase-protected. Mode must be set to path to use this option.

​

B - SSH Private Key Contents

SSH Authentication Only - Paste the contents of the private key. The key must NOT be passphrase-protected. Mode must be set to contents to use this option.

Some hosts requires SSL certificate checking to be disabled. Leave enabled for proper security.

​

Username

Basic Authentication Only

​

Password / PAT

Basic Authentication Only

​

Default Author Email

boraers@gmail.com

Used as fallback in case the author of the change is not present.

​

Default Author Name

BoraEr90

Used as fallback in case the author of the change is not present.

​

Local Repository Path

/root/repo

Path where the local git repository will be created.

​

Git Binary Path

Optional - Absolute path to the Git binary, when not available in PATH. Leave empty to use the default PATH location (recommended).

SYNC DIRECTION

Choose how content synchronization is handled for this storage target.

Bi-directional

In bi-directional mode, content is first pulled from the storage target. Any newer content overwrites local content. New content since last sync is then pushed to the storage target, overwriting any content on target if present.

Push to target

Content is always pushed to the storage target, overwriting any existing content. This is safest choice for backup scenarios.

Pull from target

Content is always pulled from the storage target, overwriting any local content which already exists. This choice is usually reserved for single-use content import. Caution with this option as any local content will always be overwritten!

SYNC SCHEDULE

For performance reasons, this storage target synchronize changes on an interval-based schedule, instead of on every change. Define at which interval should the synchronization occur.

Every

5

Minute(s)

0

Hour(s)

0

Day(s)

0

Month(s)

0

Year(s)

Currently set to every 5 minutes.

The default is every 5 minutes.

### using self-hosted gitea

https://www.reddit.com/r/wikijs/comments/uyfjlz/help_cannot_use_storage_targets/

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

192.168.178.79

attention: DHCP to be activated manually!

root, mygit90

#Install git

apt update && apt install git -y

#Get the correct download link for the latest version

wget https://dl.gitea.com/gitea/1.21.4/gitea-1.21.4-linux-amd64

#Move the binary to bin

mv gitea* /usr/local/bin/gitea

#Make executable

chmod +x /usr/local/bin/gitea

#Ensure it works

gitea --version

#Create the user/group for gitea to operate as

adduser --system --group --disabled-password --home /etc/gitea gitea

#Config directory was created by adduser

#Create directory structure (mountpoint should be /var/lib/gitea)

mkdir -p /var/lib/gitea/{custom,data,log}

chown -R gitea:gitea /var/lib/gitea/

chmod -R 750 /var/lib/gitea/

chown root:gitea /etc/gitea

chmod 770 /etc/gitea

checking permission:

ls -l

/var/lib/gitea/lost+found

rmdir /var/lib/gitea/

rm -r -f /var/lib/gitea/

lsof +D /var/lib/gitea/

umount /var/lib/gitea

lsof +D /var/lib/gitea | awk '{print $2}' | tail -n +2 | xargs -r kill -9

need to delete the Linux lost+found directory to avoid issues with changing permissions:

https://www.baeldung.com/linux/lost-found-directory

find "-iname" lost+found -type d -exec rm -r "{}" \;

nano /etc/systemd/system/gitea.service

→ copy code from aforementioned instruction webpage

ip a

192.168.178.79/24

fe80::be24:11ff:fee4:4091/64

systemctl daemon-reload

systemctl enable --now gitea

→ configure via web gui: http://192.168.178.79:3000/

admin_bora, boraers@gmail.com, mygit90

after isntallation: http://192.168.178.79:80/

http://192.168.178.79:3000/admin_bora/WikiJS.git

gitea@192.168.178.79:admin_bora/WikiJS.git

instead of git@github.com:BoraEr90/WikiJS.git

TARGET CONFIGURATION

​

Authentication Type

basic

Use SSH for maximum security.

​

Repository URI

http://192.168.178.79:80/admin_bora/WikiJS.git

Git-compliant URI (e.g. git@github.com:org/repo.git for ssh, https://github.com/org/repo.git for basic)

​

Branch

main

The branch to use during pull / push

​

SSH Private Key Mode

path

SSH Authentication Only - The mode to use to load the private key. Fill in the corresponding field below.

​

A - SSH Private Key Path

/root/.ssh/id_rsa

SSH Authentication Only - Absolute path to the key. The key must NOT be passphrase-protected. Mode must be set to path to use this option.

​

B - SSH Private Key Contents

SSH Authentication Only - Paste the contents of the private key. The key must NOT be passphrase-protected. Mode must be set to contents to use this option.

Some hosts requires SSL certificate checking to be disabled. Leave enabled for proper security.

​

Username

admin_bora

Basic Authentication Only

​

Password / PAT

mygit90

Basic Authentication Only

​

Default Author Email

boraers@gmail.com

Used as fallback in case the author of the change is not present.

​

Default Author Name

admin_bora

Used as fallback in case the author of the change is not present.

​

Local Repository Path

/root/repo

Path where the local git repository will be created.

​

Git Binary Path

Optional - Absolute path to the Git binary, when not available in PATH. Leave empty to use the default PATH location (recommended).

SYNC DIRECTION

Choose how content synchronization is handled for this storage target.

Bi-directional

In bi-directional mode, content is first pulled from the storage target. Any newer content overwrites local content. New content since last sync is then pushed to the storage target, overwriting any content on target if present.

Push to target

Content is always pushed to the storage target, overwriting any existing content. This is safest choice for backup scenarios.

Pull from target

Content is always pulled from the storage target, overwriting any local content which already exists. This choice is usually reserved for single-use content import. Caution with this option as any local content will always be overwritten!

SYNC SCHEDULE

For performance reasons, this storage target synchronize changes on an interval-based schedule, instead of on every change. Define at which interval should the synchronization occur.

Every

5

Minute(s)

0

Hour(s)

0

Day(s)

0

Month(s)

0

Year(s)

Currently set to every 5 minutes.

The default is every 5 minutes.

pic