Comprehensive Study Notes: Cloudflare Domain Setup and Raspberry Pi OS Deployment

Domain Setup and Cloudflare Infrastructure

  • Domain Registration and Management:

    • Domain purchasing and platform setup are managed through name.com.
    • Public internet exposure and edge management are handled via Cloudflare.

  • Network Tunneling and Traffic Forwarding:

    • Cloudflare terminal tools expose local network services directly to the public internet.
    • The underlying process of Cloudflare tunneling operates identically to traditional port forwarding, enabling locally hosted websites to be publicly accessible via standard URLs.
    • Active target URL for public accessibility testing: mysoil.click.
    • Financial cost for domain acquisition: 2.022.02 to 2.21352.2135 dollars.

  • Database Routing and API Architecture:

    • Local development setups run websites and web applications directly from a local laptop over the internet.
    • Advanced routing involves establishing dedicated database endpoints or alternative sub-domain routes rather than exposing raw database interfaces directly to mysoil.click.
    • Security and architectural best practice mandates routing database access through an API layer rather than allowing direct public access to the raw database.
    • Designated API sub-domain endpoint: api.soil (or api.mysoil.click).
    • Service port configuration: The API database connection is mapped to custom Port 80808080 (configured as port8080api.soil).

Online Class Structure and Midterm Requirements

  • Course Deliverables and Objectives:

    • Hands-on self-hosted server configuration and custom domain setup constitute the core requirements for final assessments.
    • Midterm evaluation expectations include:
    • Submission of a finalized midterm layout and functional output.
    • Practical testing of self-hosted server components and infrastructure setup.

  • Demonstration Protocol:

    • Live practical demonstrations focus on Operating System (OS) installation and edge hardware deployment.
    • Presenters share full desktop screens, verify active browser tabs, and ensure audience visibility prior to executing configuration steps.

Raspberry Pi Hardware and OS Selection

  • Software Tools:

    • OS installation requires downloading the official Raspberry Pi Imager software directly from the official Raspberry Pi website.

  • Storage Device Options and Performance Comparison:

    • Compatible storage media includes SD cards, Hard Disk Drives (HDDs), and Solid State Drives (SSDs).
    • Performance hierarchy: SSDs are explicitly preferred over HDDs and SD cards due to substantially superior read and write speeds.
    • Alternative storage setups utilize SD card slots or external SD card enclosures.
    • Selected physical storage media for setup: Kingston SSD.

  • Hardware Compatibility:

    • Targeted hardware platform: Raspberry Pi 3 family (encompassing Model A, Model B, Model B+, and related variants).
    • Exact hardware unit deployed: Raspberry Pi 3 Model B.

  • Operating System Architecture:

    • Recommended image: Raspberry Pi OS 64-bit edition with desktop Graphical User Interface (GUI).
    • 64-bit system architecture is preferred over 32-bit systems for supported hardware.
    • Legacy desktop environment options remain available within the imager for specialized or older Raspberry Pi OS deployments.

OS Customization and Localization Settings

  • System Interaction Modes:

    • Raspberry Pi units can operate in headless terminal mode (command line interface via display) or full desktop GUI mode (recommended default for general mini-computer tasks).

  • Storage Protection Protocols:

    • During storage drive selection in the imager, system drives on the host machine must be carefully excluded to prevent accidental OS overwrites.
    • System prompts display explicit I/O installation warnings before executing disk operations.
    • Target drive selected for flashing: Kingston SSD.

  • Hostname Configuration:

    • Purpose: Bypasses default values to set custom host identifiers.
    • Network Function: Upon connecting to a local Wi-Fi router or mobile hotspot, the configured hostname provides an accessible local domain name, serving as a human-readable alternative to static or dynamic local IP addresses.
    • Configured Hostname: ARPAI / Raspberry Pi.

  • Localization Parameters:

    • Timezone configuration: Configured to Philippines Standard Time using the Asia/Singapore regional time zone setting (representing capital city mapping).
    • Keyboard layout: Set to standard localized keyboard mapping.

Network Credentials and Security Authentication

  • User Account Provisioning:

    • Local authentication credentials must be configured for system access and user display.
    • Minimum security standard: Passwords must be at least 88 characters long.
    • User Account Setup:
    • Hostname: ARPAI / Raspberry Pi
    • Username: Raspberry Pi
    • Example Password: 12345678 (or Jester123 / Gesture123).

  • Pre-Configured Network Access:

    • Wi-Fi settings are pre-configured within the image so the Raspberry Pi automatically connects to the designated wireless network immediately upon initial bootup.
    • Target Wireless Hotspot SSID: Jester123456.
    • Target Wireless Hotspot Password: Jester123.

Remote Access Protocols and Security Setup

  • SSH (Secure Shell) Administration:

    • Enabling SSH permits complete headless remote access without attaching physical peripherals (keyboard, mouse, or monitor) to the Raspberry Pi.
    • Access interface: Operations are managed via terminal, Command Prompt (cmd), or remote shell sessions from an external machine.
    • Command Syntax: ssh username@hostname (e.g., ssh username@ARPAI).
    • Hostname resolution allows connecting without knowing or entering the exact numeric local IP address.
    • Crucial Requirement: The administrative client machine and the Raspberry Pi must be connected to the exact same Wi-Fi network/subnet.
    • Authentication configuration: Password-based authentication is enabled.

  • RealVNC Remote Desktop Infrastructure:

    • RealVNC provides full graphical remote desktop interface (GUI) access across different external networks.
    • Operating requirements: Requires creating and linking a dedicated RealVNC account.
    • Free-tier limitation: Restricted to a maximum of 1010 registered devices per account.
    • Implementation decision: Disabled in favor of lightweight SSH command-line management.

  • Final Pre-Flashing Configuration Summary:

    • Target Device: Raspberry Pi 3 (Model A, A+, B, B+).
    • Operating System: Recommended 64-bit Raspberry Pi OS with Desktop GUI.
    • Target Storage Drive: Kingston SSD.
    • System Hostname: ARPAI.
    • Timezone: Asia/Singapore (Philippines Timezone).
    • Local User: Username and Password configured.
    • Network Integration: Auto-connect Wi-Fi enabled (SSID: Jester123456).
    • Protocol Access: SSH enabled with password authentication.

OS Flashing and Verification Procedure

  • Flashing Execution Workflow:

    1. Click Write inside the Raspberry Pi Imager interface.
    2. System Warning Prompt: A prompt warns that proceeding will permanently delete and erase all existing data on the target storage drive (Kingston SSD).
    3. User Confirmation: Select Understand and Erase/Write to proceed.
    4. OS Writing Phase: The imager writes the system image to the Kingston SSD.
    5. Verification Phase: Automatic verification of written data blocks to ensure image integrity.
    6. Completion: Final notification confirming successful completion of writing and verification.

  • Physical Deployment:

    • Upon completion of the write and verification process, safely disconnect/unplug the Kingston SSD from the host computer.
    • Insert/connect the target SSD into the Raspberry Pi hardware unit.
    • Storage Compatibility: SSD boot functionality applies to Raspberry Pi version 3 and higher hardware models.

Questions and Discussion

  • Data Integrity and Formatting Warnings:

    • Concerns regarding storage wiping during OS image flashing are clarified: all existing files on the selected media are permanently erased during the format and write process.

  • Midterm Submission Guidelines:

    • Students are required to capture screenshots and unedited recording data as proof of component testing and OS installation.
    • Video recordings and output verification logs must be submitted without editing to confirm valid setup execution.