cd ~
git clone https://github.com/overleaf/toolkit.git
cd toolkit
bin/init

Change listening IP and port

sudo vim config/overleaf.rc

• change YourPORTChoice in OVERLEAF_PORT=YourPORTChoice
• change  OVERLEAF_LISTEN_IPto 0.0.0.0

Build docker images for ARM

This is the key part. One needs to build the arm version of the docker images using the command below.

cd ~
git clone https://github.com/overleaf/overleaf.git
cd overleaf/server-ce

make ARCH=arm build-base
make ARCH=arm build-community

Change image names

The image needs to be renamed, correponding to the version mentioned in the version file below.

docker image tag sharelatex/sharelatex:main sharelatex/sharelatex: x.x.x

Note:
- x.x.x comes from ~/toolkit/config/version

Start service

bin/up -d

Verify the service is accessible

• Access the below link in your browser:

YourServerIP:YourPORTChoice

Creating a new user

bin/docker-compose exec sharelatex /bin/bash -ce "cd /overleaf/services/web && node modules/server-ce-scripts/scripts/add-user --email=your_email_address"

In case the SSD  planned to move the installation to already has data which should be kept, the following steps can be followed.

Create partitions for RPi on the SSD

All the following partition operations can be done inGParted.

First, two partitions corresponding to the micro SD card need to be created on the SSD: bootfs and rootfs. If necessary the existing partition on the SSD should be resized on the left side to allow for the new partitions. The size of these two partitions should be the same as those on the micro SD card.

Clone micro SD partitions into the two partitions on SSD

The following commands can be used to clone the partitions:

sudo dd bs=512M  if=/dev/your_microSD_boot_partition of=/dev/your_ssd_boot_partition
sudo dd bs=512M  if=/dev/your_microSD_root_partition of=/dev/your_ssd_root_partition

The cloned partitions should be checked in GParted to check no errors are given.

UUID settings

Partition UUIDs  need to be adjusted to point to these on the SSD. This includes two parts: /cmdline.txt in bootfs

and /etc/fstab in rootfs. They can be changed by mounting partitions on another Linux machine.

How to check partition PARTUUID and UUID

The PARTUUID and UUID of a partition can be checked by the blow command:

sudo blkid /dev/partition_to_check

cmdline.txt in bootfs partition

Change xxxxxxxx below to the PARTUUID of rootfs partition on the SSD.

root=PARTUUID=xxxxxxxx

/etc/fstab in rootfs partition

Change yyyyyyyy below to the UUID of bootfs partition on the SSD.

Change zzzzzzzz below to the UUID of rootfs partition on the SSD.

proc            /proc           proc    defaults          0       0
UUID=yyyyyyyy /boot/firmware  vfat    defaults          0       2
UUID=zzzzzzzz /               ext4    defaults,noatime  0       1

Now, plug your SSD to the Raspberry Pi without your micro SD card plugged. Start the RPi and enjoy!

1. On the GoDaddy settings page, go to the DNS management page
   1. Remove GoDaddy default name servers
   2. Add the following name servers from Dynu

      1. NS1.DYNU.COM
         NS2.DYNU.COM
         NS3.DYNU.COM
         NS4.DYNU.COM
         NS5.DYNU.COM
         NS6.DYNU.COM
         NS10.DYNU.COM
         NS11.DYNU.COM

      2. Here, NS10 and NS11 are from Europe. If not added the DNS propagation takes very long for myself to see the change. So just remember to add the NS from your region
   3. Other than this, nothing needs to be done (no c name no a record no site redirection)
2. On Dynu website:
   1. register your domain
   2. Follow this tutorial to enable the local service of Dynu on rpi4 (which I’m using to host this site)
      1. Use md5 of password for safety
      2. echo "password"| md5  is wrong, should be echo -n "password" | md5 which does not keep the trailing new line character
   3. Back to Dynu website, go to DDNS services:
      1. check your domain is there and the ip address was just updated
      2. this can also be done by checking the log file on the script folder on rpi4
      3. or you can directly enter the url in the script file in a browser and see if there’s any error

Now you are good to go! To me, using name servers from a DDNS provider seems to be faster than redirecting the whole site to a DDNS url (which points to my real public IP) on the GoDaddy website.

Backup

Remote way

If you prefer to do it remotely via SSH, use this command:

ssh root@your_rpi_ip "dd if=/dev/your_rpi_sd_card bs=1m | gzip -1 -" | pv | dd of=rpi.gz

your_rpi_ip can be obtained by hostname -I . if is followed by the your sd card path when mounted on RPi, which can be obtained by lsblk -p (make sure the disk you believe to be the SD card matches the size of your SD card!). pv is used here so that the progress of dd can be constantly checked. If you don’t have it, install it using brew install pv if you have homebrew installed. 

Depending on the size of your SD card and your connection speed, it could take some time. So go and get a coffee!

Local way (RPi end)

Similarly, you should be able to dd locally on RPi then scp the image to your PC/Mac. As a result, the SSH part will be stripped away:

dd if=/dev/your_rpi_sd_card bs=1m | gzip -1 - | pv | dd of=rpi.gz

After it’s done, you can use scp to transfer the image file to your PC/Mac.

Local way (PC/Mac end)

This is recommended since it’s faster due to the fact that the SD card is physically connected to your PC/Mac.

1. Remove the SD card from your RPi and connect it to your computer.
2. Check the disk name on your Mac using: diskutil list. Similarly, double check the disk size so that you don’t make a mistake.
3. Same as the local way on RPi end: dd if=/dev/your_rpi_sd_card bs=1m | gzip -1 - | pv | dd of=rpi.gz.

Restoring

It’s also pretty straight-forward for the restoring. The steps are:

1. Connect the SD card to your computer.
2. Check the name of the disk using the method mentioned above
3. Unmount (not eject) the SD card by diskutil unmountDisk /dev/disk_nr
4. Burn the image file into your SD card using: gzip -dc yourRPiImage | pv | sudo dd of=/dev/disk_nr bs=1m

After another coffee, you can plug your SD card back into your RPi. Enjoy your back-to-life RPi.

P.S.

Instead of using pv, progress and watch can be used together to check the status. So run the above commands without pv, and open another terminal and run watch progress, you now even have a progress bar!

Precondition

• apache2 and php already installed and set up on your raspberry pi (raspbian)

 Download and run the automated install (Reference)

Run this command in the terminal:

curl -sSL https://install.pi-hole.net | bash

1. Select interface: wlan0 (depending on your need, wlan0 is for wifi and eth0 is for the wired connection)
2. Select DNS provider: OpenDNS
3. IPv4&v6: both
4. Use static IP?: Yes
5. Web admin interface: yes
6. Install web server?: No
7. Log query: On
8. Privacy: full

After these steps, a message will appear in the terminal telling you the IP and the password of the admin page (something like http://192.168.x.xxx). Note this down as you will need it later.

Two warnings

The installation finished with two warnings:

1. xxx modules are missing for php
2. the web server user needs to be member of the “pihole” group for full functionality

The first can be solved using sudo apt install php-xxx to install these packages.

The second can be solved by sudo usermod -a -G pihole your_apache2_user.

Some setup on the admin page

On the left, go to group management -> Adlists to add custom list. Below are some that I use:

• Easy list
• Easy privacy
• Developer Dan’s ads&tracking list
• Neohosts basic
• Easylist China

After adding your lists, go to tools -> update gravity -> update.

Check it’s working

Go to a site that you are certain that is riddled with ads or a ab backer checker site (such as this one), and you show see that most of the ads are gone!

Now, enjoy a more pleasant online experience!