1. Introduction
2. OS Setup
3. Encrypted Storage
4. Users
5. Samba
6. Docker and Portainer
7. Ldap
8. Kvm and WebVirtCloud
9. Cockpit (and smbManager)
10. Piwigo
11. Ampache
12. JellyFin
13. File browser

Getting started

The idea is to build a NAS-like device able to replace my current QNAP Server, with disks encrypted on an external device

What is it??

The following functionalities would be implemented

• File browser (https://github.com/filebrowser/filebrowser)
• Samba share (https://github.com/enira/cockpit-smb-plugin)
• Virtual Machines (https://github.com/retspen/webvirtcloud)
• Docker containers (https://www.portainer.io/)
• Remote Administration (https://cockpit-project.org/)
• Photo manager (https://piwigo.org/)
• Music manager (https://ampache.org/)
• Video Manager (https://jellyfin.org/)
• Ldap (http://phpldapadmin.sourceforge.net)
• VPN (https://openvpn.net/)

With Luks encrypting the devices and data via a remote key (just in case of robbery) that i store inside a small ESP32 device. But even a Raspberry Zero WH can fit

Connections to the warious software

Supposing that mi server is "192.168.1.67"

Docker stuffs

• File server: http://192.168.1.67:7000 main (Custom auth)
• Webvirtcloud: http://192.168.1.67:8000 main (Ldap)
• Jellyfin: http://192.168.1.67:8096 main (Ldap)
• Portainer: http://192.168.1.67:9000 main (Custom auth)
• Piwigo: http://192.168.1.67:11000 main (Ldap)
• Ampache: http://192.168.1.67:12000 main (Ldap)
• phpLdapAdmin: http://192.168.1.67:13000 (cn=admin,dc=kendar,dc=org)
• OpenVpn (Ldap)

Installed stuff

• SSH login: (Local Machine)
• Cockpit: http://192.168.1.67:9090 main (Local machine)
  • Samba manager
• Samba shares (Local Machine)

Conventions

In general i prefer

Please notice that all the files modification are listed in a "diff-like" way:

** path/filename **

  something
+ added line
- removed line

While new files are listed completely

** path/filename **

this is the 
file content

Running command if the prompt is changed like for fdisk, the new prompt is listed between round parenthesis, followed by the command

fdisk /dev/sdb      #Run fdisk
(fdisk)p            #Inside fdisk run the "p" command

Executing the commands the > sign means the output (or its interesting part). Running lsblk you can retrieve the size of the disk sdb as output

lsblk   
> sdb                         8:16   0 465.8G  0 disk