Getting Jiggy with the Latte Panda

Originally I was thinking of using multiple single board computers on a network to perform different tasks. But after buying a 256GB micro-SD card which I had intended to use for a Raspberry Pi, I had a change of heart. The latter panda has 32GB of on board storage which I can use to host the OS, and then with 256GB of extra storage, rather than having a lot of different devices on the network, I can probably install everything to the latter panda.

So what’s the plan? There are a bunch of points I want to hit on this. I guess I should start with the high priority ones and work from there.

1. Access point – I want to be able to host a wifi network and have clients, my laptop and cell phone, connect to this. The advantage of doing this is I can set up a DNS to be able to define name for locations on the network. And not have to remember ip addresses of my network clients, or have to manually define a DNS for each client on the network.

2. KVM – For the most I don’t need to use windows for common tasks. The one thing I find myself using windows for is disk mounting tools like Daemon tools lite. So I want to host a virtual windows machine that I can use to mount a disk image and extract the files from the disk on the network.

3. Samba – This is a pretty simple, samba is a useful utility for hosting files on a network.

4. Nextcloud – I tried hosting this on a Pi and it was slow. So I want to try the latte-panda to see if works better with an intel processor and 2GB of RAM.

Approach:

In terms of approach I want to host the system on the 32 GB of internal storage and then /var on the 256 GB micro-sd card. Next I want to try getting the access point. And from there KVM. For KVM i can probably get away with the NAt interface as I plan on using everything with samba, so I don’t need a bridged network or anything like that. For samba i can host the files on /var/data. And for nextcloud I can store the files on /var/www/apache, or /var/www/nextcloud? I think I want to use apache for nextcloud exclusively and then use nginx as a reverse proxy server.

Leave a Reply

Your email address will not be published. Required fields are marked *