Enter Mealie. It's a self-hosted recipe manager and meal planner built for privacy and control. It's the perfect addition to the sovereign homestead's digital toolkit, putting your culinary data back where it belongs: under your ownership.

Why Self-Host Your Recipes?

Before we dive into the "how," let's cover the "why." As a Bitcoiner or Monero enthusiast, you already understand the principles:

• Data Ownership: Your recipes, meal plans, and shopping lists are your data. With Mealie, they are stored in a database you control, on hardware you control. No company can mine this data, sell it, or lock you out of your own account.
• Privacy: No tracking pixels, no analytics, no "smart" recommendations based on your dietary habits. Your cooking habits remain private.
• Censorship Resistance: Your service can't be de-platformed. As long as your server runs, Mealie runs.
• Offline-First Mindset: Hosted on your local network, Mealie is fast and accessible even when your internet connection is flaky. It's a truly resilient system.
• Customization and Control: You control the environment, the backups, and the integrations.

Installing Mealie with Docker Compose

For a bare metal server, Docker Compose is the cleanest and most manageable way to deploy Mealie. It isolates the application and its dependencies, making updates and maintenance straightforward.

This guide assumes you have a server running a Linux distribution with Docker and Docker Compose installed.

Step 1: Create the Project Directory

SSH into your server and create a dedicated directory for Mealie.

mkdir mealie
cd mealie

Step 2: Create the ,docker-compose.yml, File

This file defines the Mealie service and its configuration. Create a new file named docker-compose.yml and paste the following content into it.

version: '3.8'

services:
  mealie:
    image: hkotel/mealie:latest
    container_name: mealie
    restart: unless-stopped
    ports:
      - "80:80" # Exposes Mealie on port 80. Change if needed.
    volumes:
      - ./data:/app/data/ # Persists all Mealie data.
    environment:
      # 
      # Using SQLite is the simplest for a single-user setup.
      # For multi-user or more robust setups, consider PostgreSQL.
      DB_TYPE: sqlite
      # 
      # The default API token for the initial setup. Change this immediately.
      DEFAULT_EMAIL: admin@example.com
      # 
      # Set your initial admin credentials.
      # These are only used on first run if the database is empty.
      # IMPORTANT: Change these before your first run!
      INITIAL_ADMIN_EMAIL: your-admin@email.com
      INITIAL_ADMIN_PASSWORD: your-secure-password

Key Configuration Points:

• ports: This maps port 80 on your host to the Mealie container. If you have another service using port 80 (like a reverse proxy), change the host port (e.g., "8090:80").

• volumes: This is crucial. It maps the ./data directory on your host to the /app/data directory inside the container. This is where all your recipes, user data, and the database will live. Back up this directory regularly.

• environment:

• DEFAULT_EMAIL: This is the default email for API access. It's good practice to set it to your admin email.

• INITIAL_ADMIN_EMAIL & INITIAL_ADMIN_PASSWORD: Change these now. These credentials are used to create the first administrator account the first time Mealie starts up. After the initial setup, these variables are ignored.

Step 3: Launch Mealie

With the docker-compose.yml file in place, you can start the service.

docker-compose up -d

The -d flag runs the container in detached mode (in the background). Docker will pull the latest Mealie image and start the container. This may take a few minutes on the first run as it initializes the database.

Step 4: Initial Setup and Hardening

1. Navigate to http://your-server-ip in your browser.
2. You should see the Mealie setup screen. Create your admin account using the INITIAL_ADMIN_EMAIL and INITIAL_ADMIN_PASSWORD you set in the compose file.
3. Once logged in, immediately go to the Admin Settings and change the default API token (DEFAULT_EMAIL).
4. Explore the settings and configure Mealie to your liking.

Your sovereign recipe manager is now running.

Understanding the Recipe JSON Structure

One of Mealie's most powerful features for the sovereignty-minded is its transparent and structured data format. Recipes are stored as simple JSON objects, making them easy to back up, edit manually, and even script. This is the antithesis of opaque, proprietary formats.

Here is an overview of the main sections in a recipe's JSON structure. You can view this by editing any recipe in Mealie and looking at its raw data.

Core Recipe Object

{
  "name": "Classic Beef Tacos",
  "description": "A simple and flavorful ground beef taco recipe.",
  "image": "images/recipes/12345678-1234-1234-1234-123456789012.jpg",
  "recipeYield": "4 servings",
  "recipeIngredient": [
    "1 lb ground beef",
    "1 packet taco seasoning",
    "1/2 cup water",
    "8 taco shells",
    "1 cup shredded cheese",
    "1 cup shredded lettuce",
    "1 tomato, diced",
    "1/2 cup sour cream"
  ],
  "recipeInstructions": [
    {
      "text": "Brown the ground beef in a skillet over medium-high heat."
    },
    {
      "text": "Drain the excess fat from the skillet."
    },
    {
      "text": "Add the taco seasoning and water to the beef. Stir and simmer until thickened."
    },
    {
      "text": "Warm the taco shells according to package directions."
    },
    {
      "text": "Fill the shells with the beef mixture and top with your favorite toppings."
    }
  ],
  "nutrition": {
    "calories": "350 kcal",
    "proteinContent": "25 g"
  },
  "orgURL": "https://example.com/original-recipe",
  "categories": ["Main Dish", "Beef", "Mexican"],
  "tags": ["quick", "weeknight", "kid-friendly"]
}

Key JSON Fields Breakdown

• name: The title of your recipe.
• description: A short summary or notes about the recipe.
• image: A relative path to the recipe's image file, stored within your ./data volume.
• recipeYield: How much the recipe makes (e.g., "4 servings", "1 loaf").
• recipeIngredient: An array of strings, where each string is a single ingredient. This is perfect for parsing into a shopping list.
• recipeInstructions: An array of instruction objects. Each object has a text field containing a step. This structured approach is far superior to a single block of text.
• nutrition: An object containing nutritional information like calories, protein, fat, etc. All are optional.
• orgURL: If you imported the recipe from a website, Mealie keeps a link to the original source.
• categories: An array of strings for broad categorization (e.g., "Dessert", "Dinner").
• tags: An array of strings for more specific, searchable tags (e.g., "gluten-free", "spicy", "grilling").

This simple, human-readable structure is the foundation of Mealie's power. You can export your entire recipe collection as a single JSON file, providing a true, vendor-agnostic backup of your culinary knowledge.

The first piece of our infrastructure is a personal database running on a server that you control. Think of this as your digital filing cabinet, sitting right in your own home or office.

• What it is: We'll use a database server called CouchDB. It's lightweight, reliable for storing documents, and designed for replication—the perfect partner for syncing your notes.
• How it's hosted: You will run CouchDB on your own server. This could be a spare desktop computer, a dedicated small-form-factor PC, or a single-board computer like a Raspberry Pi. The key is that the hardware is yours.
• How it's secured: This is where we break from traditional methods. Instead of dealing with public IP addresses, domain names, and complex HTTPS certificates, we will use Tailscale. Tailscale creates a private, encrypted network between your devices, kind of like your own personal internet. Your laptop and your office server will be on this "Tailnet," allowing them to communicate securely without ever exposing your database to the public internet.

The outcome of this stage is a secure, always-on database running on your own hardware, accessible only to you.

Part 2: The Private Bridge – Connecting Obsidian via Tailscale

With a secure filing cabinet in place on your Tailnet, the next step is to connect your Obsidian vault to it. This bridge uses your private Tailscale network, making the connection both simple and incredibly secure.

• The Tool: We will use the "LiveSync" plugin for Obsidian. This is the specialized tool that knows how to talk to a CouchDB database.
• The Concept: After you've installed Tailscale on both your writing computer and your server, they can see each other using simple, private names. LiveSync will connect to your CouchDB instance through this secure Tailscale tunnel. It works in the background, automatically sending any new notes or changes you make in Obsidian directly to your server.
• The Magic of Sync: This remains a two-way street. It keeps your local vault and the remote database perfectly in sync. Whether you edit on your laptop or a desktop in another room, LiveSync ensures all your data is consistent and backed up on your own server, all traffic protected by Tailscale's end-to-end encryption.

The outcome of this stage is a continuously backed-up Obsidian vault, with your data flowing securely over a private network to your own physical hardware.

Part 3: The Public Megaphone – Publishing from Obsidian to Nostr

Your thoughts are now safe, synchronized, and completely under your control on your own infrastructure. The final step is to turn select parts of that private vault into a public broadcast for the decentralized web.

• The Plugin: We will install the "Nostr Writer" plugin into Obsidian. Its sole purpose is to format your notes and publish them to the Nostr network as permanent articles.
• The Protocol: Nostr is a decentralized, censorship-resistant social protocol. When you publish, your content is distributed across thousands of relays run by different people around the world. It effectively cannot be de-platformed or removed.
• The Workflow: The process is beautifully simple. You write an article within your synced vault. You add a small block of metadata at the top of the note (called frontmatter) to specify its title, summary, and tags. Then, with a single command from within Obsidian, the Nostr Writer plugin sends that note out to the Nostr network as a long-form, immutable event.

The outcome is the ultimate goal: a thought born in your private mind, organized in your private vault on your private network, is now broadcast to the entire world as a permanent public record—all on your own terms and without ever leaving the comfort of your editor.

Conclusion: You Hold the Hardware and the Keys

By leveraging your own server and the simplicity of Tailscale, you have built a system that is the epitome of data sovereignty. Your work is private by default, backed up on hardware you own, and instantly publishable on your own terms. You are no longer just a writer; you are the master of your digital domain, from the steel of your server to the fabric of the decentralized internet.

1. Installing Ubuntu Server
2. Installing Docker on Linux Server

Installation

Open a Terminal session and write the following command to make sure that Docker is running:

sudo systemctl status docker

You should get a screen with the docker.service as "running". To get back to command line do CTRL+C

Then, create the volume that Portainer Server will use to store its database:

sudo docker volume create portainer_data

You are now ready for the on-liner installation:

sudo docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

To validate the installer, prompt the following command:

sudo docker ps

You should see Portainer's container running.

To access Portainer Server, go to the following adress:
https://localhost:9443

Et voila!

1. Installing Ubuntu Server

Installation

Open a Terminal session and write the following command:

sudo apt install docker.io

You will be ask permission to install and continue

y

Validation of the installation

To validate the installer, prompt the following command:

docker --version

You should get:

Docker version 26.1.3, build 26.1.3-0ubuntu1~24.04.1

To test if it is running, prompt the following command:

sudo systemctl status docker

You should get a screen with the docker.service as "running".
To get back to command line do CTRL+C

Test Installation

To make sure that everything runs smoothly, write the following command:

sudo docker run hello-world

You should get a Hello from Docker.

You are ready to enjoy pulling docker images!

originally posted at https://stacker.news/items/917064

In this project, I will guide you through the basics of cryptocurrency mining and how to get started.

First of all, sorry pals, mining cryptocurrencies will not make you rich. There will be no Lambo. It is easy to get caught up with Crypto Twitter and YouTube influencers. The reality is that in order to make a living mining crypto is to have sponsors.

Now that we got the boring part out of the way, you must wonder what the hell is crypto mining.

In a nutshell, crypto mining is using computing power to try solving an equation and get reward for the right answer. This Proof of Work (POW) is beneficial to the blockchain and contributes to increase its security. But you must wonder “how do I do this”? The answer is simple, you need a mining rig. Let’s build one together!

You don’t need any technical background, I will guide you and take your hand through this awesome journey. Here is a preview of what you will need and what will be discussed in some upcoming notes:

• Power Supply (PSU)
• Motherboard (MOBO)
• Memory Sticks (RAM)
• Computer Processor (CPU)
• Graphic Cards (GPU)
• Operating System (OS)

Don’t worry, I’ll let all this sink in and will explain more into details the relation between the hardware and tips on how to select it.

See you soon!

Your own Node hardware

Installing & Configuring Bitcoin Core

1. Download the file

Go into your “home” directory and create the following folders
mkdir fulcrum
mkdir fulcrum_db

Go to the Fulcrum Github release page and download the latest release
cd downloads

wget https://github.com/cculianu/Fulcrum/releases/download/v1.9.1/Fulcrum-1.9.1-x86_64-linux-ub16.tar.gz

wget https://github.com/cculianu/Fulcrum/releases/download/v1.9.1/Fulcrum-1.9.1-x86_64-linux-ub16.tar.gz.asc

sha256sum --ignore-missing --check SHA256SUMS

Extract the file
tar xvf Fulcrum-1.9.1-x86_64-linux-ub16.tar.gz

Move the files to fulcrum folder
mv Fulcrum-1.9.1-x86_64-linux-ub16/* /home/"user"/fulcrum
cd ..
cd fulcrum

2. Creating the Key and Cert

Creating the keys
openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem

Generating a RSA private key

Press "enter: for all the defaults parameters. The files keys.perm and cert.perm should have been created in your fulcrum folder.

3. Configuration file

rename the config file
mv fulcrum-example-config.conf fulcrum.conf

Modify the config file
nano fulcrum.conf

Change the following in the config file:

• Change path of the datadir: home/"username"/fulcrum_db
• rpcuser: use the same one as the bitcoin.conf file
• rpcpassword: use the one used for the rpcauthy while setting up the bitcoin.conf file
• remove the # for the SSL= 0.0.0.0:50002
• remove the # for the certificate and put correct path home/"username"/fulcrum/cert.pem
• remove the # for the key and put correct path home/"username"/fulcrum/key.pem
• remove the # for peering and change for peering=false
• remove the # for fast-sync and change for what you are confortable fast-sync = 4000 (4g of ram)

CTRL-X, Y, ENTER

4.Creating the service file

Creating service file
sudo nano /etc/systemd/system/fulcrum.service

Paste de following in the file and replace "user" by your server username.

[Unit]
Description=Fulcrum After=network.target
[Service]
ExecStart=/home/"user"/fulcrum/Fulcrum /home/"user"/fulcrum/fulcrum.conf User="user"
LimitNOFILE=8192
TimeoutStopSec=30min
[Install]
WantedBy=multi-user.target

CTRL+X, Y, Enter

***Start this service

sudo systemctl enable fulcrum.service
sudo systemctl start fulcrum.service
sudo systemctl status fulcrum.service

To see the log
journalctl -fu fulcrum.service

Et Voila!

This is extremely useful for when you need to flash an image on a Stick.

This exemple will creat a bootable stick with the newest version of Ubuntu. I will be using this sitck in another article when I will upgrade my current laptop.

Prerequisite

• ubuntu-22.04.3-live-server-amd64.iso
• Any version of Linux
• USB Key

Let's Go!

The first step is to see what is the correct path of the USB Key.
In order to do so, type the following commande without the USB Key

ls -1 /dev/sd?

I get this

/dev/sda
/dev/sdb

Afer, insert the USB Key and repeat

ls -1 /dev/sd?
I then get this

/dev/sda
/dev/sdb
/dev/sdc

The USB Key path is clearly /dev/sdc

Now, all you need to put is a one liner command:

sudo dd bs=4M if=/path/to/file.iso of=/dev/sdc status=progress oflag=sync

Here /path/to/file.iso is simply the path to your file and /dev/sdc is the path to your USB that we have earlier determined.

To make things easier, I often go into the folder in which I have the ISO.
cd Downloads/Ubuntu

After, I am able to only write the image name

sudo dd bs=4M if=ubuntu-22.04.3-live-server-amd64.iso of=/dev/sdc status=progress oflag=sync

Et voila! No need for a special software! You can now create any bootable stick!

• A dedicated computer
• Ubuntu Server

1- Installing Bitcoin Core

This section will be done remotely from another computer by connecting to your Node using SSH. Please follow previous Chapter to make sure your hardware is adequate, and you have followed Ubuntu Server installation.

***First of all, we will validate that the installation was done properly and that the Ubuntu installation was NOT setup as a virtual machine **

df -h

Looking for updates

sudo apt update

Updating

sudo apt upgrade

Lets start by creating a “downloads” folder

mkdir downloads

***Go in the downloads folder

cd downloads

It is now important to understand what you are about to do. There are different ways to install Bitcoin Core. My preferred way is to download the release from Bitcoin Core here https://bitcoincore.org/en/download/
and do the GPG Key verification with the key list here https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-commits/trusted-keys on Github.

Download the files from the Bitcoin Core website

wget https://bitcoincore.org/bin/bitcoin-core-24.0.1/bitcoin-24.0.1-x86_64-linux-gnu.tar.gz

wget https://bitcoincore.org/bin/bitcoin-core-24.0.1/SHA256SUMS

wget https://bitcoincore.org/bin/bitcoin-core-24.0.1/SHA256SUMS.asc

Validate that the release file is listed in the checksums file

sha256sum --ignore-missing --check SHA256SUMS

Use GPG to load keys locally from individuals found on the Github site
Ignore any warning and failures, but you must be sure that the lists “OK” after the name of the release file downloaded

Use GPG to load keys locally from individuals found on the Github site

gpg --keyserver hkps://keys.openpgp.org --recv-keys E777299FC265DD04793070EB944D35F9AC3DB76A

gpg --keyserver hkps://keys.openpgp.org --recv-keys D1DBF2C4B96F2DEBF4C16654410108112E7EA81F

Verify that the checksum file is verified

gpg --verify SHA256SUMS.asc

You should receive a “Good signature” beside the name associated to the key

Extract the tar file. It will create a folder called bitcoin-24.0.1 so it is important that you call it in the next command line.

tar xzf bitcoin-24.0.1-x86_64-linux-gnu.tar.gz

Install the content in the following directory. It is IMPORTANT that you write the correct folder name based on your release number. If you have installed the release 25.0, the folder name has to be bitcoin-25.0

sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-24.0.1/bin/*

Cross your fingers and launch Bitcoin Core

bitcoind -daemon

***Get blockchain info to see which block your node is at

bitcoin-cli getblockchaininfo

Validate your node is connected to how many peers

bitcoin-cli getconnectioncount

***If you want to follow the log of your node synchronization, you should open secondary Terminal window and write the following command

tail -f .bitcoin/debug.log

2. Configuring Bitcoin Core

While the blockchain is synchronizing, you can start the configuration. In order to be fully synchronized, it will take approximately 18 hours. I found a great tutorial on youtube here: https://www.youtube.com/watch?v=fx_mLXISrfM

Open a new therminal window and go to the /.bitcoin folder

cd /.bitcoin

*** We need to create a new configuration file***

nano bitcoin.conf

Paste de following text in the bitcoin.conf file

server=1
txindex=1
daemon=1
rpcport=8332
rpcbind=0.0.0.0
rpcallowip=127.0.0.1
rpcallowip=10.0.0.0/8
rpcallowip=172.0.0.0/8
rpcallowip=192.0.0.0/8
zmqpubrawblock=tcp://0.0.0.0:28332
zmqpubrawtx=tcp://0.0.0.0:28333
zmqpubhashblock=tcp://0.0.0.0:28334
whitelist=127.0.0.1
rpcauth="username":[output of rpcauth.py]

Keep this terminal window open and go back to the main window

We will create a username and password for the RPC Authentification of the bitcoin.conf file we have created in the other terminal window and modify it

In the original terminal window, be sure you are in your “downloads” folder

cd downloads

*** In order to add a "username" and "password" to access to your node, go to Github.com/bitcoin/bitcoin and search for rpcauth.py. Go to the raw file and copy the link***

wget https://github.com/bitcoin/bitcoin/blob/master/share/rpcauth/rpcauth.py

Make the file executable
chmod +x rpcauth.py

Execute the file with a "username" & "password" at the end of the command line
./rpcauth.py "username" "password"

Copy the string and paste it in the configuration file of the auxiliary termina window

Modify the "username" and "password" in the bitcon.conf file

#Output for your username and password
rpcauth="username":[output of rpcauth.py]

CTRL+X and save Yes

Restart your node
Bitcoin-cli stop
Bitcoind

3.Creating the service file for automatic boot on start-up

*** Go back to Github.com/bitcoin/bitcoin and search for .service file. https://raw.githubusercontent.com/bitcoin/bitcoin/663f6cd9ddadeec30b27ec12f0f5ed49f3146cc9/contrib/init/bitcoind.service***

Important note: The new service file does not work properly. The link above is for the service file from 2021

Download the .service file in your systemd folder
cd /etc/systemd/system

sudo wget https://raw.githubusercontent.com/bitcoin/bitcoin/663f6cd9ddadeec30b27ec12f0f5ed49f3146cc9/contrib/init/bitcoind.service

sudo nano bitcoind.service

Change the file

In the [service] section, make the following changes:

• Make sure that the “ExecStart” has the right path for the folder “bitcoind” on the same line as “daemonwait” (you can verify the path in another terminal with the command “whereis bitcoind”)
• you need to remove the “wait” in -daemonwait to have only -daemon
• Make sure that the bitcoin.conf file has the right path. 
• Change also the path for the datadir.
• Put a # in front of ExecStartPre=
• Change “user” and “group” for the actual user of the server instead of Bitcoin and Bitcoin
• Put a # in front of ProtectHome

Press CTRL + X to save it, Y, enter

Shutdown Bitcoin
bitcoin-cli stop

Activate the new service file
sudo systemctl enable bitcoind
sudo systemctl start bitcoind

Validate the status
sudo systemctl status bitcoind

4. Enable TOR

Go back to home directory
sudo apt install tor

Validate that TOR has been activated
sudo systemctl status tor

Edit TOR rc file
sudo nano /etc/tor/torrc

Go all the way to bottom and enter 3 lines
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1

CTRL-X, Save

Restart Tor
sudo systemctl restart tor

sudo usermod -a -G debian-tor "username"

Modify bitcoin.conf to add TOR lines
nano .bitcoin/bitcoin.conf

Add the following lines at the end of the file:

proxy=127.0.0.1:9050
listen=1 b
bind=127.0.0.1
onlynet=onion
addnode=ty5nq4ua4v47jmebyib7wtk6b25exd735twap6g3rckbfhvlzvrkdhid.onion:8333

CTRL+X, Y

Reboot your node
sudo reboot

Et voila!

Prerequisites

1. Create a Ubuntu Bootable Stick

Installing Ubuntu Server

1. Connect your device up with a keyboard/mouse, ethernet cable, screen and with the boot USB inserted into the device but still powered off.
2. With the USB inserted, turn on your device. If it brings you to a Ubuntu screen then great move on to step 4, if not carry out the next step.
3. If the device does not boot to a Ubuntu screen with the USB plugged in, we need to tell it to boot from a USB rather than the internal hard drive. Shut the device. Turn it back on and hold “ALT” key once the computer is starting to boot. The “ALT” key is replacing the “OPTION” key on a Mac. Please select UEFI in the menu in order to reboot with the Boot stick.
4. You will arrive on the Ubuntu Server.
5. Next choose your desired language.
6. Select to update to new installer if any updates available.
7. Allow it to detect or select your regional keyboard layout.
8. Choose the basic installation, do not select any additional options.
9. At the next stage it will like you to connect to the internet, the WiFi will not work at this stage so you will need to plug in via ethernet if not already done.
10. Once connected to the internet an IP address is shown on the screen, write it down and press Done
11. Unless you’re using a proxy on the next screen (Configure Proxy) press Done.
12. Leave the default Mirror address by pressing Done. 
13. At the next screen Guided Storage Configuration you can select the disk setup, Uncheck “Set up this disk as a LVM” since you want to use the whole disk as your node and press Done.
14. The next screen will confirm the file system summary click Done.
15. Ensure you have opted for the correct disk and confirm action at the pop-up screen.
16. At the profile screen, you can provide your name, the servers name and provide the username.
17. It will ask you if you want to enable Ubuntu Pro, select skip for now.
18. At the SSH Setup screen, select to install OpenSSH server and select Done.
19. We did not opt to install any additional features at the next screen (Featured Server Snaps) this is to keep the Umbrel OS very lightweight click Done.
20. Once the install completes, the screen will show you (Install Complete!).
21. Select Reboot now.
22. Remove the USB drive when it tells you and press Enter.

This should now complete the Ubuntu installation stage, next we need to SSH to the server.

Connecting to the Ubuntu Server using SSH

Now that your Ubuntu Server is online, the rest of the operation will be done via another computer with SSH connection using Terminal. From now on, I will start the comments with # so they will not be confused with commands to enter into Terminal.

To connect to your server, you will need to use the following command with the name of the server from step 16 and the IP address noted down in the step 10 from the previous section

ssh "server name"@"IP address"

You will be prompt to enter the password from step 16

"enter password"

Congratulation, you are now connected and ready to start installing your node applications!

It is important to select adequately the hardware that will be used to build your Node. The Node will be running 24h /7 days and will countain your lightning channels. It is important to use high quality hardware and spend the extra dollars for it.

At the time of building my Node, there was a shortage of Raspberry Pi and I was looking for an optimal alternative. I have decided to go ahead and purchase a used Mac Mini (late 2012).

It is recommended NOT to purchase a Mac Mini newer than 2012 (i.e 2014 and up) because Apple started to solder the RAM to the Logic Board after 2012. The Mac Mini Late 2012 is the last model that is fully customizable with SSD and RAM upgrades.

Here is the list of hardware that will be used in this build:

• 2 x 8G DDR3L Sodim 1600Mhz 1.35V
• 1 x Mac Mini (Late 2012) 2.5Ghz
• 1 x Samsung Evo 870 1Tb SSD ^

^ Note: As discussed earlier, it is important to select hardware of quality. I had initially purchased a low cost 2Tb SSD but it failed while trying to download the Bitcoin blockchain.

##2. Hardware Upgrade

To facilitate the upgrade of the hardware, you will need the proper tools to remove some T6 & T8 screws.

Here are the steps to dismount the few components of the Mac Mini to upgrade the hardware:

1. Unplug the Mac Mini.

2. Turn it upside down with the black cover facing up.

3. Put your thumbs in the 2 grooves of the cover and turn the piece counterclockwise.
   

4. Remove the cover.

5. Remove 3 x T6 screws holding the fan.
   

6. Lift the fan and disconnect the connector by pulling gently straight up the wires.

7. Remove 1x T6 screw at the bottom of the shroud (black plastic piece on the left of the fan).
   

8. Remove the shroud by holding the top right part with your fingers and turning it clockwise.
   

9. Remove 4 x T8 screws of the grill WIFI cover.
   

10. The top of the grill is mounted under the Mac Mini case. Lift gently the bottom of the grill and pull towards yourself to remove the grill.

11. Move the grill aside, you do not have to disconnect the WIFI sensor, just be careful.

2.1 Upgrading the RAM

The RAM is visible and accessible from the moment you remove the cover. Simply release each RAM by releasing the clips on the side. Once disengaged, the RAM will spring in a 45-degree angle. Remove it and put back the upgraded RAM at a 45 degree angle and push it down for it to clip.

2.2 Upgrading the SSD

It is important to note that the Mac Mini has 2 SSD bay. They are referred to as the “upper bay” and “lower bay”. Since we have flipped the Mac Mini upside down to remove the bottom cover, the “upper bay” is located under the “lower bay”.

The “upper bay” is mounted with an expansion kit that holds the SSD in position whereas the “lower bay” SSD is simply resting on top of the “upper bay” SSD.

One important aspect is that the connecting cables for the “lower bay” and “upper bay” SSD are not the same. The “upper bay” SSD connects on the logic board on the right and the “lower bay” SSD cable connects on the left. Removing the “upper bay” SSD requires removing the logic board therefore requires more work. It is recommended to install the new SSD in the “lower” bay. Here are the 2 scenarios:

1.Your Mac Mini has already a Hard Drive installed in the “lower” bay. In that case insert a credit card under the HD and gently pry it upwards. You will be able to slide it out of the bay. The reason to pry it gently is because since there is no “upper” bay drive, The HD is being held in the air by 2 screws on the side that are aligned in 2 holes in the Mac Mini case. Once the HD is removed, transfer the connecting cable and the 2 screws to the new SSD. To put back the new SSD, it is easier to rotate the Mac Mini 90 degree and have the mounting holes at the bottom and use the gravity to get the 2 mounting screws in the holes. After, connect the connector to the logic board.

2. Your Mac Mini has already a Hard Drive installed in the “upper bay”? Leave it there, you do not need mounting screws, but you need a new connecting cable. You will have to buy a “lower bay connector”. Once installed on the SSD, slide the SSD on top of the original one. The connector will plug on the logic board on the left of the “upper bay” SSD connector.

A good preparation would be to go in “Disk Utility” menu on MacOS and search for “upper” or “lower” position before starting to disassemble.

Reassemble everything and you are done.

Plant-Based option: Use veggie ground.

Gluten Free option: Use GF soy sauce or tamari and GF hoisin.

Nutrition Information:

• Calories: 404/serving
• Carbs: 49.8g/serving
• Protein: 25.3g/serving
• Fat: 11.5g/serving
• Fiber: 3.5g/serving
• Sugar: 6.5g/serving
• Sodium: 433.2mg/serving

Details

• ⏲️ Prep time: 5 min
• 🍳 Cook time: 25 min

Ingredients

• 1 cup rice, uncooked
• 1lb ground (beef, checken, turkey, or veggie ground)
• 1/2 yellow onion, diced
• 4 garlic cloves, minced
• 2 teaspoons grated ginger
• 4 cups coleslaw mix
• 2 tablespoons low sodium soy sauce
• 2 tablespoons hoisin
• 1 1/2 teaspoons rice vinegar
• 1 1/2 teaspoons sesame oil
• 2 green onions, diced

Directions

1. Cook rice according to package directions.
2. While de rice cooks, add the ground to a large skillet over medium high heat, cook 5-6 minutes until browned and just cooked through (add a little bit of oil if using a lean ground).
3. Add onions to the pan and cook until soft and translucent, around 4-5 minutes.
4. Add the garlic and ginger and cook until fragrant, around 30 seconds.
5. Add the coleslaw mix and cook 1-2 minutes until tender.
6. Stir in the soy sauce, hoisin, rice vinegar, and sesame oil.
7. Garnish with green onions and serve over the rice.