Self-hosting Appwrite gives you complete control over your backend infrastructure, data, and costs. It’s a powerful solution for developers who want a flexible Backend-as-a-Service (BaaS) without vendor lock-in. However, a common challenge arises when you want to deploy Appwrite on a Virtual Private Server (VPS) that’s already running other websites using an Nginx web server.

The command line is where you get real control in Linux. It lets you dig into the system, automate tasks, and solve problems directly.

Introduction

In the last level, we used grep to find a known pattern in a file. For Bandit Level 8 to 9, the challenge is more abstract: we need to find a line that is unique within a file filled with duplicates. The password isn’t next to a keyword; the password is the unique line itself.

This requires us to move beyond single commands and learn how to create a pipeline, chaining multiple tools together to perform a complex data analysis task in a single line.

Introduction

We have successfully used the find command to locate files based on their metadata. Now, for Bandit Level 7 to 8, our focus shifts from finding the file to finding specific data inside a file.

This level introduces grep, one of the most fundamental and widely used text-processing utilities in the Linux command-line world. 🕵️

The Challenge: Level 7 Goal

The goal for this level is described as follows:

Introduction

In the previous level, we used find to search within a specific directory. Now, in Bandit Level 6 to 7, we’re taking the training wheels off. The password file could be anywhere on the entire server, and we must once again use its properties to locate it.

This level introduces the challenge of running a search with broad scope, which often generates a lot of noise. We will learn how to filter out that noise to find exactly what we’re looking for.