bashclub / zamba-lxc-toolbox Goto Github PK

https://www.dokuwiki.org/dokuwiki

move to debian 11 template

lxc Containter need to be checked

Add option to configure container via dhcp.

• zmb-standalone => ZMB (Samba) standalone server with ZFS volume snapshot support (previous versions)
• zmb-ad => ZMB (Samba) Active Directory Domain Controller, DNS Backends SAMBA_INTERNAL and BIND9_DLZ are supported
• zmb-member => ZMB (Samba) AD member with ZFS volume snapshot support (previous versions)
• mailpiler => mailpiler mail archive mailpiler.org
• matrix => Matrix Synapse Homeserver matrix.org with Element Web Element on github
• nextcloud => Nextcloud Server nextcloud.com with fail2ban und redis configuration
• checkmk => CheckMK 2.0 Raw Edition checkmk.com with our Fork of Matrix Notification Plugin (https://github.com/bashclub/check_mk_matrix_notifications)
• open3a => Open3A accounting software for small and medium business open3a.de
• debian-unpriv => Debian unprivileged container with basic toolset
• debian-priv => Debian privileged container with basic toolset

Also categorize config variable in basic ans advanced settings to allow faster deployment.

The script install.sh should change the values for hostname, memroy, swap etc. in line 109, but doesn't.

Reason: ';' is missing at the end of lines 104 and 106

Add PKI management system to zamba domain controller or as standalone container?

Solutions to get an eye on:

• https://github.com/openxpki/openxpki
• https://github.com/smallstep/certificates

Maybe an IAM system?

Yubikey or Solokey intergration (FIDO2)?

Install check_mk RAW Edition

If a split-dns setup is configured, by default the public company website is not accessible, because the domain will be the local dc.
The host www can be configured by a static DNS A entry, but the website will not be accessible just by the domain name.
A solution for this issue is a webserver on the dc to redirect or reverse proxy to the public website.

Finish Message
Your open3a installation is now complete. Please continue with setup in your Browser:
URL: http://192.168.100.200/24
Login: Admin
Password: Admin

Mysql-Settings:
Server: localhost
User: open3a
Password: KjFToTglK6XDeKkYqETB
Database: open3a

Wrong IP-Addresse (used dhcp no static ip)

https://www.invoiceninja.com/

As a free alternative to JIRA, I would suggest to add https://www.openproject.org/ to the toolbox.

I think especially small to mid sized companies could be interested in such kind of software.

Further alternatives: https://geekflare.com/de/open-source-project-management-software/

Currently when someone just clones the repo and runs install the start of a new container will fail:

# ./install.sh
1) checkmk	     3) debian-unpriv	 5) matrix	     7) onlyoffice	 9) proxmox-pbs	    11) zmb-ad		13) zmb-standalone
2) debian-priv	     4) mailpiler	 6) nextcloud	     8) open3a		10) urbackup	    12) zmb-member	14) quit
#? 2
Installation of debian-priv selected.
Loading config file '/root/zamba-lxc-toolbox/conf/zamba.conf'...
./install.sh: line 91: /root/zamba-lxc-toolbox/conf/zamba.conf: No such file or directory
400 not enough arguments
pveam list <storage>
Will now download newest debian-11-standard .
400 not enough arguments
pveam download <storage> <template>
Will now create LXC Container 105!
unable to parse volume ID ':'
400 too many arguments
pct set <vmid> [OPTIONS]
./install.sh: line 130: [: ==: unary operator expected
400 Parameter verification failed.
nameserver: invalid format - value does not look like a valid IP address

net0: invalid format - missing key in comma-separated list property

pct set <vmid> [OPTIONS]
Configuration file 'nodes/rizzo/lxc/105.conf' does not exist
lxc-attach: 105: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid
lxc-attach: 105: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context
lxc-attach: 105: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid
lxc-attach: 105: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context
400 not enough arguments
pct push <vmid> <file> <destination> [OPTIONS]
can only push files to a running CT
can only push files to a running CT
can only push files to a running CT
can only push files to a running CT
can only push files to a running CT
Installing basic container setup...
lxc-attach: 105: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid
lxc-attach: 105: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context
Install 'debian-priv'!
lxc-attach: 105: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid
lxc-attach: 105: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context

PVE 7.1-8

ZFS snapshots are noch accessible yet on zmb-ad.

Install nextcloud (nginx + redis + postgres or mariadb) container

This needs to be documented!
There are a few options to consider:

• Check predefined password for complexity, if requirements not met, cancel the install script.
• Set administrator password after provisioning the domain?
• INSECURE: Add an option to turn off password complexity

Changing the locale via script is possible in the following way

sed -i "s/^#.$LXC_LOCALE/$LXC_LOCALE/" /etc/locale.gen
locale-gen $LXC_LOCALE
echo LANG=$LXC_LOCALE > /etc/default/locale
echo LANGUAGE=$LXC_LOCALE >> /etc/default/locale
export LANG=$LXC_LOCALE

Hint change zamba.conf to
LXC_LOCALE=de_DE.UTF-8

adding service Summary to pct description.
like:

https://community.ptc.com/t5/Windchill-Systems-Software/How-to-add-multi-line-quot-Work-Description-quot-using-CLI/m-p/129084#M1491

Nextcloud and mailpiler installation scripts do not use the configured LXC_TIMEZONE of zamba.conf but "Europe/Berlin" hardcoded instead.

Privileged containers are only needed for Zamba containers, this should be preconfigured.

• all certs in same path
• deliver with self-signed cert
• letsencrypt support (e.g. certbot), maybe with managed reverse proxy container
• opnsense le support via api

Rework the post-installation of mailpiler to allow an unattended service installation.

https://www.home-assistant.io/

Add a script to install on proxmox host for zmb-member and zmb-standalone, which diffs the snapshots of and places the output on the smb share as textfile to see changed files of the last 24 hours.

https://cloudbeaver.io/

Under some circumstances it might be useful to have a dedicated imapsync LXC available.

Here a reference to a procedure installing an additional (apache) web based imapsync:
https://www.bachmann-lan.de/imapsync-unter-debian-11-installieren/

https://www.proxmox.com/de/proxmox-mail-gateway

for public server?

• ufw
• fail2ban
• RootkitHunter
• ssh-login-email-notify

https://www.ecodms.de/index.php/de/

pct set -timezone - unknown option
Missing parameter on pve 5.3.18
(Livestream - Migration eines Fileservers auf zfs mit zamba...)

The Script run without any erriors, but after that, the share ist not available.
I tried it even with stock .conf but also there the same behavior.

Script workflow needs to be like:

• Select Service
• Configure container based on the service
• Configure configure service settings
• Unattended container creation and service configuration

redirect https://hostname/ to https://hostname/instance/

Make modules out of services like webservers (nginx, apache), tls and certificates, databases (mariadb, postgresql,...), etc. to create a standard for dependent services

the current scripts only allow do deploy a
Primary DC (like https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller ) or an ordinary
member Server. (like https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member )

Please also include the possibility to deploy a
secondary DC (like https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory )

Create installer for Zammad Ticketsystem

e.g. VitalPBX

beim Versuch einen PBS aufzusetzen mit dem Script:
bash install.sh -i3015 und der Auswahl 9
kommt folgende Fehlermeldung:

Fehl:4 http://download.proxmox.com/debian/pbs bullseye InRelease
Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY DD4BA3917E23BF59
Paketlisten werden gelesen… Fertig
W: GPG-Fehler: http://download.proxmox.com/debian/pbs bullseye InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY DD4BA3917E23BF59
E: Das Depot »http://download.proxmox.com/debian/pbs bullseye InRelease« ist nicht signiert.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
E: Paket proxmox-backup-server kann nicht gefunden werden.
/root/install-service.sh: Zeile 22: proxmox-backup-manager: Kommando nicht gefunden.

Add a web interface for managing the domain controller.

https://github.com/christgau/wsdd

dpkg-reconfigure locales requires user interaction ans kills already loaded script vars. Find a solution to configure 'locales' without user interaction.

https://freescout.net/

https://www.bookstackapp.com/

• server_name must be set in /etc/matrix-synapse/conf.d/server_name.yaml

• update to latest version v1.7.34

# Define the version of Element Web
MATRIX_ELEMENT_VERSION="v1.7.34"