DEV Community: lechat

I Built a Laravel-like Web Framework for Rust

lechat — Sat, 18 Apr 2026 22:26:06 +0000

I recently built a Rust web framework called Willow Forge:

👉 https://github.com/lechatthecat/willow-forge

It’s a Laravel-like layer on top of axum, designed to give you structure, productivity, and a batteries-included developer experience — something I personally missed when building apps in Rust.

What Willow Forge Is

Willow Forge is a productivity-focused framework for Rust web development, inspired by Laravel and Rails.

It provides:

MVC-style project structure
Controllers, middleware
Request validation
Server-side HTML rendering + JSON APIs
Routing separation (web.rs / api.rs)
Migrations

Under the hood, it uses axum, but instead of starting from a blank slate every time, you get a structured foundation.

Why I Built It

Every time I started a new Rust web project with axum, I found myself rebuilding the same things:

Folder structure
Routing organization
Validation layer
Middleware grouping
Basic app architecture

Rust gives you power — but not much guidance.

In contrast, frameworks like Laravel or Rails give you:

A clear place for everything
Consistent patterns
Fast onboarding
Less decision fatigue

I wanted that experience — but in Rust.

Who This Is For

Willow Forge is probably a good fit if:

You like Laravel style structure
You don’t want to reinvent app architecture every time
You’re building:
- CRUD apps
- internal tools
- dashboards
- SSR + API combined apps

Create a k8s development environment by Minikube

lechat — Thu, 20 Mar 2025 17:39:16 +0000

Prerequisites

My environment is Windows10.

Download tools

Please install minikube from here:

https://minikube.sigs.k8s.io/docs/star

Let's use virtualbox driver for minikube.

Please install virtualbox from here:

http://virtualbox.org/wiki/Downloads

We will use Git too. Please install Git from here:

https://git-scm.com/downloads

Let's install skaffold too:

https://skaffold.dev/docs/install/

Then please install kubernetes too:

https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/

(If you use choco or scoop, it is easy to install)

After installing them, let's confirm if you can access minikube from Powershell.
Open Powershell then run the following command:

minikube version

Then you get minikube version

minikube version: v1.35.0
commit: dd5d320e41b5451cdf3c01891bc4e13d189586ed-dirty

In the same way, please check git version too:

git -v
git version 2.47.1.windows.2

Now let's make a test project for this test.

cd Documents
mkdir projects
cd projects
mkdir test-project
cd test-project

Minikube start (minikube cluster)

terminology

What are Containers?

Containers are lightweight, isolated runtime environments that package an application and its dependencies. They ensure consistency across different computing environments.

What are Pods?

A Pod is the smallest deployable unit in Kubernetes, acting as a wrapper for one or more containers.

What is a Cluster?

A Cluster is the highest-level component in Kubernetes, consisting of multiple worker nodes that run Pods.

Start a minikube cluster

Please run this command:

minikube start --driver=virtualbox

Then minikube will start. Please note that, if it is docker driver, you can use mount option like

minikube start --mount --mount-string="$HOME:/src" --driver=docker

but unfortunately this is impossible with virtualbox driver. (but virtualbox is free unlike docker desktop...)

Now let's install kubernetes. But we will just install kubernetes via minikube:

minikube kubectl -- version

After kubernetes is installed, kubernetes version is displayed like:

minikube kubectl -- version
Client Version: v1.32.0
Kustomize Version: v5.5.0
Server Version: v1.32.0

Create pods

Let's create PHP, Nginx, MariaDB environment.

At first, enable ingress:

minikube addons enable ingress

Then please save the following as php-mariadb.yaml. This file contains definition of containers in the pods. Please note that you must use "LF" for this file's linebreaks not "CRLF":

# MariaDB Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  # Deployment name
  name: mariadb
  # Labels for identifying the deployment
  labels:
    app: mariadb
spec:
  # Number of MariaDB instances
  replicas: 1
  selector:
    # Matching labels for pods
    matchLabels:
      app: mariadb
  template:
    metadata:
      labels:
        app: mariadb
    spec:
      containers:
        - name: mariadb
          # Docker image for MariaDB
          image: mariadb:11.3
          # Port on which MariaDB runs
          ports:
            - containerPort: 3306
          # Environment variables for MariaDB
          env:
            - name: MYSQL_ROOT_PASSWORD
              value: "rootpassword"
            - name: MYSQL_DATABASE
              value: "mydatabase"
            - name: MYSQL_USER
              value: "myuser"
            - name: MYSQL_PASSWORD
              value: "mypassword"
          # Volume mounting for MariaDB data storage
          volumeMounts:
            - name: mariadb-storage
              mountPath: /var/lib/mysql
      # Definition of volumes
      volumes:
        - name: mariadb-storage
          emptyDir: {}
---
# MariaDB Service
apiVersion: v1
kind: Service
metadata:
  # Service name for MariaDB
  name: mariadb
spec:
  ports:
    - port: 3306
  selector:
    # Selector for connecting to MariaDB pods
    app: mariadb
---
# PHP Application Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  # Deployment name
  name: php-app
  # Labels for identifying the PHP deployment
  labels:
    app: php-app
spec:
  # Number of PHP application instances
  replicas: 1
  selector:
    matchLabels:
      app: php-app
  template:
    metadata:
      labels:
        app: php-app
    spec:
      containers:
        - name: php-app
          # Docker image for PHP application
          image: php:8.3-apache
          # Port on which PHP Apache runs
          ports:
            - containerPort: 80
          # Volume mounting for PHP application code from host machine
          volumeMounts:
            - name: php-app-code
              mountPath: /var/www/html
            - name: apache-config
              mountPath: /etc/apache2/sites-enabled/000-default.conf
              subPath: default
      # Definition of volumes
      volumes:
        - name: php-app-code
          hostPath:
            path: "/mnt/project"
            type: Directory
        - name: apache-config
          configMap:
            name: apache-config
---
# ConfigMap for Apache Configuration
apiVersion: v1
kind: ConfigMap
metadata:
  name: apache-config
data:
  default: |
    <VirtualHost *:80>
        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/html
        <Directory "/var/www/html">
            Options Indexes FollowSymLinks
            AllowOverride All
            Require all granted
            DirectoryIndex index.html index.php
        </Directory>
        ErrorLog /var/log/apache2/error.log
        CustomLog /var/log/apache2/access.log combined
    </VirtualHost>
---
# PHP Application Service
apiVersion: v1
kind: Service
metadata:
  # Service name for PHP application
  name: php-app-service
spec:
  type: ClusterIP
  ports:
    - port: 80
      targetPort: 80
  selector:
    # Selector for connecting to PHP pods
    app: php-app
---
# Ingress resource for PHP Application
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: php-app-ingress
spec:
  ingressClassName: nginx
  rules:
    - host: localhost
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: php-app-service
                port:
                  number: 80

Then please save the following as skaffold.yaml:

apiVersion: skaffold/v4beta12
kind: Config
metadata:
  name: php-mariadb-app
deploy:
  kubectl: {}
manifests:
  rawYaml:
    - php-mariadb.yaml

Now our environment is ready to go!

Before starting our environment, let's create a mount directory:

mkdir mounttest
minikube mount "$Home\\Documents\\projects\\test-project\\mounttest:/mnt/project"

This mount command will keep running. For subsequent commands, please open a new terminal and run the commands on it.

Please run this command (please make sure you in the test-project directory):

cd {the test-project directory}
skaffold delete
skaffold run --force

This command will keep running. For subsequent commands, please open a new terminal and run the commands on it.

Please wait a while... Your kubernetes environment is being created in the minikube cluster. This will take time.

See here for more skaffold examples: https://github.com/GoogleContainerTools/skaffold/tree/main/examples

For available paramters: https://skaffold.dev/docs/references/yaml/

Now your php and mariadb should be running. Let's check it by kubectl get pods:

kubectl get pods
NAME                      READY   STATUS    RESTARTS   AGE
mariadb-998f96ddb-84kqs   1/1     Running   0          64s
php-app-bf6f77579-454jl   1/1     Running   0          64s

If all of them are "Ready 1/1", it means your environment is running without problem.

By the way, these are called pods:

mariadb-998f96ddb-84kqs (pod)
php-app-bf6f77579-454jl (pod)

Our containers defined by the yaml file are in the pods. One pod can have multiple containers inside.

Sometimes we define logger container and put them in the pod together with a php container.
Such containers are called "sidecar container."

If any of the pods is not ready, please check the pod:

kubectl describe pod php-app-bf6f77579-454jl

Or check the standard output:

kubectl logs php-app-bf6f77579-454jl

To see cluster-wide information:

kubectl get events --sort-by='.metadata.creationTimestamp'

When the creation is done, to access minikube environment from host, let's run this command:

minikube tunnel

This command will keep running. For subsequent commands, please open a new terminal and run the commands on it.

Mount /var/www/html to the host PC and access the file through ingress

Now let's see if you can access the ingress. Run this command and get ingress information:

kubectl get ingress
NAME              CLASS    HOSTS       ADDRESS          PORTS   AGE
php-app-ingress   <none>   localhost   192.168.59.100   80      103s

And, following this information, if you access 192.168.59.100 from your browser, you will see 404.

If you can see the 404, you are ready to go further.

Please check the ingress ip by:

kubectl get ingress
NAME              CLASS   HOSTS       ADDRESS          PORTS   AGE
php-app-ingress   nginx   localhost   192.168.59.100   80      93s

My IP is 192.168.59.100, so please update the php-mariadb.yaml's ingress configuration:

# Ingress resource for PHP Application
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: php-app-ingress
spec:
  ingressClassName: nginx
  rules:
    - host: 192.168.59.100.nip.io #!!! Change here !!!!
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: php-app-service
                port:
                  number: 80

We have mounted our "mounttest" to "/mnt/project" (of minikube) and this "/mnt/project" is mounted again to "/var/www/html" of php-appache pod. So let's create index.php like this:

<?php
echo "Hello World!";

Please save it in the mounttest of your project folder.

Now open http://192.168.59.100.nip.io/ from your browser. You should see Hello World! If you change the php code, you can see that the change is reflected in real time (if not, please disable opcache from your php.ini). Your PHP code is working in a k8s cluster!

Now you can edit your php in your mounttest folder and the edit is reflected to the php pod in the kubernetes cluster in real time. If you need, you can even set php debug for your development. But, if you with minikube & kubernetes in your local, please don't forget to disable opcache in your php.ini:

opcache.enable=0
opcache.validate_timestamps=1
opcache.revalidate_freq=0

Why did it return 404 at first, but started working after changing the IP from localhost to 192.168.59.100.nip.io?

In the initial Ingress definition inside the .yaml file, it was configured like this:

rules:
  - host: localhost

This means the Ingress rule is set to only handle requests where the hostname is localhost.

However, the virtual network created by Minikube (e.g., 192.168.59.100) exists outside the host OS's localhost.
So when you access 192.168.59.100 in your browser, the Ingress controller:

sees that the hostname doesn't match (localhost ≠ 192.168.59.100)
finds no matching rule
and returns a 404 error

So why does it work when you change to 192.168.59.100.nip.io?

When you change the rule like this:

rules:
  - host: 192.168.59.100.nip.io

Ingress recognizes the hostname and thinks:

"Ah, this is the hostname I'm in charge of!"

As a result, it correctly applies the routing rule.

Use MariaDB from host pc

Let's change MariaDB's service:

# MariaDB Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  # Deployment name
  name: mariadb
  # Labels for identifying the deployment
  labels:
    app: mariadb
spec:
  # Number of MariaDB instances
  replicas: 1
  selector:
    # Matching labels for pods
    matchLabels:
      app: mariadb
  template:
    metadata:
      labels:
        app: mariadb
    spec:
      containers:
        - name: mariadb
          # Docker image for MariaDB
          image: mariadb:11.3
          # Port on which MariaDB runs
          ports:
            - containerPort: 3306
          # Environment variables for MariaDB
          env:
            - name: MYSQL_ROOT_PASSWORD
              value: "rootpassword"
            - name: MYSQL_DATABASE
              value: "mydatabase"
            - name: MYSQL_USER
              value: "myuser"
            - name: MYSQL_PASSWORD
              value: "mypassword"
          # Volume mounting for MariaDB data storage
          volumeMounts:
            - name: mariadb-storage
              mountPath: /var/lib/mysql
      # Definition of volumes
      volumes:
        - name: mariadb-storage
          emptyDir: {}
---
kind: Service
apiVersion: v1
metadata:
  name: mariadb
spec:
  type: NodePort
  selector:
    app: mariadb
  ports:
    - port: 3306
      targetPort: 3306
      protocol: TCP
      nodePort: 30036   # for example (must be within the allowed range, e.g., 30000-32767)
---
# PHP Application Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  # Deployment name
  name: php-app
  # Labels for identifying the PHP deployment
  labels:
    app: php-app
spec:
  # Number of PHP application instances
  replicas: 1
  selector:
    matchLabels:
      app: php-app
  template:
    metadata:
      labels:
        app: php-app
    spec:
      containers:
        - name: php-app
          # Docker image for PHP application
          image: php:8.3-apache
          # Port on which PHP Apache runs
          ports:
            - containerPort: 80
          # Volume mounting for PHP application code from host machine
          volumeMounts:
            - name: php-app-code
              mountPath: /var/www/html
            - name: apache-config
              mountPath: /etc/apache2/sites-enabled/000-default.conf
              subPath: default
      # Definition of volumes
      volumes:
        - name: php-app-code
          hostPath:
            path: "/mnt/project"
            type: Directory
        - name: apache-config
          configMap:
            name: apache-config
---
# ConfigMap for Apache Configuration
apiVersion: v1
kind: ConfigMap
metadata:
  name: apache-config
data:
  default: |
    <VirtualHost *:80>
        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/html
        <Directory "/var/www/html">
            Options Indexes FollowSymLinks
            AllowOverride All
            Require all granted
            DirectoryIndex index.html index.php
        </Directory>
        ErrorLog /var/log/apache2/error.log
        CustomLog /var/log/apache2/access.log combined
    </VirtualHost>
---
# PHP Application Service
apiVersion: v1
kind: Service
metadata:
  # Service name for PHP application
  name: php-app-service
spec:
  type: ClusterIP
  ports:
    - port: 80
      targetPort: 80
  selector:
    # Selector for connecting to PHP pods
    app: php-app
---
# Ingress resource for PHP Application
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: php-app-ingress
spec:
  ingressClassName: nginx
  rules:
    - host: 192.168.59.100.nip.io #!!! Change here !!!!
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: php-app-service
                port:
                  number: 80

You can see that the MariaDB service is using NodePort now.

Stop the skaffold run from the terminal where you executed the command (by ctrl+c), then start again by:

cd {the test-project directory}
skaffold delete
skaffold run --force

Check minikube IP by:

minikube ip

It will give you the IP address of minikube. You can use this IP and the NodePort to access the MariaDB.

For me, the IP address was 192.168.59.100
The NodePort is defined as 30036 in the yaml file.

So by using both 192.168.59.100:30036, you can access the MariaDB.
Please note that the environment of MariaDB is configured this way:

- name: MYSQL_ROOT_PASSWORD
  value: "rootpassword"
- name: MYSQL_DATABASE
  value: "mydatabase"
- name: MYSQL_USER
  value: "myuser"
- name: MYSQL_PASSWORD
  value: "mypassword"

I'm scared of AI that automates coding in very high level..

lechat — Sun, 12 Jan 2025 19:20:53 +0000

Building a Developer-Focused Search Engine in Rust: Lessons Learned and Challenges Overcome 🚀

lechat — Sat, 11 Jan 2025 06:57:34 +0000

As developers, we all know the struggle of wading through irrelevant search results to find that one golden line of code. So, I thought, why not build a search engine tailored for us devs? With Rust, Actix, Elasticsearch, React, and Next.js, I created a search engine for developers.

Here is what I made:
https://dev-search.com/

I am not a senior dev, so if I am doing something stupid, please let me know 😅

🎯 The Mission

The goal was simple: create a developer's information-focused search engine with:

Frontend: React + Next.js (SSG for speed and SEO)

Backend: Rust and Elasticsearch for robust, scalable search functionality

🚧 Challenges Faced

Search by Elasticsearch is slow 😢

Because there are more than 10 million documents, the search of elesticsearch was slow.

I found that the problem that was slowing it down was:

"track_total_hits": {big number like 10000}

The Solution

Actually keeping that number big like 10000 is as slow as actually fetching 10000 documents from elasticsearch. By changing this to

"track_total_hits": false

made the search a lot faster. But this change disables ability to track how many records were hit by a search, so you must consider well if it is good for your use case.

Too Many Malicious Users Scanning the Website 👽

Ah, the joys of running a public-facing site! Within days of launching, I noticed strange requests hitting my server logs. From bots pretending to be browsers to outright weird payloads like \x00\x00SMB, my site became a playground for malicious users. Here's a gem from my logs:

35.203.211.8 - - [30/Dec/2024:05:15:37 +0000] "\x00\x00\x00\xAC\xFESMB..."

The Solution: Fail2Ban

Fail2Ban came to the rescue! This nifty tool monitors log files and dynamically bans IPs that show malicious behavior. Here's how I set it up:

Defined a Fail2Ban Jail for Nginx:

[nginx-malicious]
enabled = true
port = http,https
logpath = /var/log/nginx/access.log
maxretry = 5
findtime = 300
bantime = 600
action = iptables[name=nginx-malicious, port="http,https", protocol=tcp]

Filter to Detect Malicious Patterns:

[Definition]
failregex = ^<HOST> - - .*SMB.*
ignoreregex =

Dynamic Blocking in Action:

When Fail2Ban detects malicious requests, it updates the firewall to block the offending IP:

sudo iptables -L -n | grep DROP

With Fail2Ban, malicious IPs were swiftly banned, and my server logs became much cleaner. Lesson learned: Bots will come, but so will the ban hammer. 🛠️

Please note that, if you are using Docker/Docker compose, you might need the following:
https://github.com/fail2ban/fail2ban/issues/2376#issuecomment-2565534465

Adsense not showing 😿

As you can see on the capture:

Even though Adsense is set, the Adsense often doesn't show up...
I investigated why it is not showing up, but I guess there are 2 reasons:

My website's reputation is low
Google cannot find ad for the specified ad size

Well, I cannot change the first reason, but maybe I can do something for the second one. What I did is as follows.

The Solution

At first, I tried the fixed sized ad because I wanted a not too large ad:

<GoogleAdUnit>
    <ins class="adsbygoogle"
        style="display:inline-block;width:300px;height:90px"
        data-ad-client="ca-pub-{ad-client-id}"
        data-ad-slot="{slot id}">
    </ins>
</GoogleAdUnit>

But this often fails to show the ad.

Please note that I am using nextjs13_google_adsense because I am using Next.js.

So, after that, I tried a responsive ad. The default code of the responsive ad is:

<GoogleAdUnit>
    <ins
        className="adsbygoogle"
        style={{ display: 'block', width: '100%' }}
        data-ad-client="ca-pub-{ad-client-id}" // Replace with your AdSense client ID
        data-ad-slot='{slot id}' // Replace with your Ad slot ID
        data-ad-format="auto"
        data-full-width-responsive="true"
    />
</GoogleAdUnit>

This is the best because the size is changed in accordance with the ad size. But, to me, the auto sized ad looked too big 😅

So I limited the height like this. Please note that I am using the "horizontal" for the data-ad-format because I wanted a not-too-big horizontal ad.

<GoogleAdUnit>
    <ins
        className="adsbygoogle"
        style={{ display: 'block', width: '100%', height: '50px' }} // limit height
        data-ad-client="ca-pub-{ad-client-id}" // Replace with your AdSense client ID
        data-ad-slot='{slot id}' // Replace with your Ad slot ID
        data-ad-format="horizontal" // horizontal
        data-full-width-responsive="true"
    />
</GoogleAdUnit>

It still sometimes fail to show ad, but ad more often appear on my website now because there is not limitation for the width 😀

Unsolved Problems

Website Design is too simple
The search accuracy is low
The returned data is almost always only stackoverflow because large amount of the database is records from stackoverflow. Not sure whether this is OK..

🙏 Thanks for Reading!

I created a simple app by very fast Rust web framework Actix web. Please use this as a sample code.

lechat — Thu, 15 Aug 2024 03:36:21 +0000

Background

I believe it was last year when I had an interview at a company. As part of the technical assessment, I created a simple web application using Rust, React, and Next.js. Since I built it in just a few days specifically for the interview, it may not be highly polished, but I aimed to make it as robust as possible for production use. Therefore, I think it could be a good reference for those looking to create something with Actix web. The application uses Next.js for SSG, so it should load quickly.
https://github.com/lechatthecat/assignment

Every time I start a new development project, I find it tedious to repeatedly implement the same things, like the Docker Compose YAML file, API handlers, and Next.js configurations. I also often find myself wondering, "How did I do that again?" Because of this, I think developing based on this working project could save time.

Although I didn't end up joining the company, I wanted to share this repository with everyone instead of letting it go unused. I've removed any parts related to that company and erased them from the Git history as well.

However, one of the interview conditions was not to use any ORM libraries (such as Diesel), so there are no ORMs included. If you plan to use this as a reference, please keep this in mind, and you’ll likely need to incorporate Diesel or another ORM if you build upon it.

Lastly, please don't use the test code as a reference—it's something I put together quickly under time constraints. I'm sharing this purely as a reference.

By the way, it seems that Actix web, the Rust web framework, is incredibly fast. A few years ago, it topped the charts in the benchmark below.
https://www.techempower.com/benchmarks/#hw=ph&test=fortune&section=data-r22

Although its ranking has dropped quite a bit, as of August 15, 2024, Actix ecosystem's actix-http is still in 12th place. It's probably still one of the faster frameworks, especially among the more mature ones.

How to use

This is witten in the Readme.md too:

$ git clone https://github.com/lechatthecat/assignment
$ cd assignment
$ docker compose up --build -d

This will start release build of the Rust code. When it is done, you can access the app from this URL.
http://localhost/login

Please use the following information to login.
name: test_user1
password: password

For development

If you want to use the docker compose file for development:

$ docker compose -f docker-compose-dev.yml up -d --build

What does the app do?

Structure

The app is divided into an API server built with Actix web and a React + Next.js application that calls it. To see which APIs are available, please refer to the API handlers.
https://github.com/lechatthecat/assignment/blob/main/simple_restaurant_api/src/api/api_handler/handlers.rs

The API server, nginx, and PostgreSQL are all set up as separate containers using Docker Compose. The code in the frontend folder is automatically synchronized within the nginx container, which serves the frontend. However, any request that starts with /api is redirected (via reverse proxy) by nginx to the Actix web server. All other requests are handled by the frontend inside the nginx container.

Overview

This is a simple SPA (though technically it's SSG with Next.js, so I'm not sure if SPA is the right term) designed for use in a restaurant with 10 tables. The idea is that each waiter has a tablet, and when taking orders, they first select the table from which the order is being placed.

After selecting the table, you'll be taken to a screen showing the list of currently received orders for that table.

When you press "Menu," you'll be taken to a page displaying the full menu, where you can click on the items that have been ordered. Each menu item includes the price and the estimated time until it's ready. By pressing "Add this to order," you can add the selected menu item to the list of received orders.

Once you add an order, a real-time countdown begins until the preparation is complete. When it reaches zero, the waiter is expected to go to the kitchen to pick up the dish and serve it to the customer at that table. You can also see the estimated time when the dish will be ready.

To be honest, the functionality itself isn't anything special. As I mentioned before, I built this in just a few days for an interview, so I only implemented the bare minimum.

Additional Recommendations

Here are a few things that I think should be added to the to-do list:

There’s no documentation for the API yet, so I think it would be a good idea to implement Swagger for that.
Implementing caching with Redis on the API side, as well as using a CDN like Cloudflare, could help reduce server load. In this case, since it’s only being used internally, I didn’t bother with it. However, if this were a publicly available app, caching would be necessary.
If you're hosting a service that might experience high traffic, it’s better to separate containers for the API server, frontend, and load balancer, and use Kubernetes for container management instead of Docker Compose. This makes scaling out much easier.
In the docker-compose.yml file, the myrust volume is bound file-by-file, as shown below. This is to avoid overwriting the container’s target folder (built within the container) with an empty target folder from the host. However, for local development, it might be more convenient to sync entire folders instead of individual files. For example, you could set up a shell script that automatically builds the project whenever the container starts. That said, this isn’t mandatory, and using a separate docker-compose.yml for development could also work. I didn’t include the shell script because, during the interview, I wanted to avoid confusing the interviewer with a 404 error that would occur while waiting for the build command (by the script) to finish, even after running docker compose up. Docker compose command wouldn't wait for the script execution to finish if it is executed as command of Dockerfile or docker compose file.

volumes:
    # log
    - ./logs:/simple_restaurant_api/log
    # Rust code
    - ./simple_restaurant_api/src:/simple_restaurant_api/src
    - ./simple_restaurant_api/Cargo.lock:/simple_restaurant_api/Cargo.lock
    - ./simple_restaurant_api/Cargo.toml:/simple_restaurant_api/Cargo.toml

On the frontend, I committed the Next.js out directory, but ideally, it would be better to generate it each time the container is started using npm run build, rather than committing it. Since the focus of the interview was on the API implementation, I didn’t want to require the interviewer to run the npm run build command manually. However, for a production environment, this should be fixed (for example, by setting up an automated script to handle the build process).
Normally, there would be a step where the customer confirms their order (something like "Is this order correct?") before it's sent to the kitchen. This would require an additional feature to temporarily hold the order for confirmation before actually submitting it. However, since the main focus of this test was the API, I skipped it.
I used the unwrap function outside of tests, which isn’t good practice in Rust, especially for production environments. It would be better to replace it with the expect function (which allows for custom error messages) or, for cases where errors are likely in production, handle them explicitly with a match statement or the or_else function.

How to "permanently" remove annoying websites from your google's search result

lechat — Wed, 14 Aug 2024 17:55:45 +0000

Motivation

I dislike annoying websites like pinterest or tiktok. I don't want to create an account just to see some normal pictures or some short videos of baseball. I want those to disappear from my google search result, so I always search like "baseball -tiktok", but I don't want to write "-tiktok" every time I google search, so I checked how to make it default.

After writing this article, I realized that with this approach, it would also filter out news articles that have 'TikTok' in the title. So, instead of just 'TikTok,' it might be better to specify the URL, like using -inurl:tiktok. If this concerns you, give it a try this:



https://www.google.com/search?q=-site:tiktok.*+-site:*.tiktok.*+-site:pinterest.*+-site:*.pinterest.*+%s

Android

Install kiwi browser from playstore.
Write chrome://settings/ in the kiwi browser's search bar.
Click on the browser configuration icon
You will find Search engine. Tap it. Then tap on the Manage search engines..
Add a new search engine from Add of Site search. The name and keyword of the new search engine to be added can be anything like noiseless google for the name and @nggl for the keyword. The url for the new search engine is https://www.google.com/search?q=-tiktok+-pinterest+%s and save it.
Make this the default search engine.
Now, when you google something from your chrome browser, your search result filters the specified websites by default.
Please note that you can restore to the old search engine configuration from kiwi browser's Setting page.

PC chrome

Open Chrome browser
Write chrome://settings/ in the chrome browser's search bar.
Look for Search configuration and open it. Click on the Manage search engines..
Add a new search engine from the lowest of the list. The name and keyword of the new search engine to be added can be anything like noiseless google for the name and @nggl for the keyword. The url for the new search engine is https://www.google.com/search?q=-tiktok+-pinterest+%s and save it.
Make this the default search engine.
Now, when you google something from your browser, your search result filters the specified websites by default.
Please note that you can restore to the old search engine configuration from the browser's Setting page.

References

https://conpath.net/columns/filter-google-search-results-by-default/ Images of PC chrome section are cited from here

My language now can make instances

lechat — Sun, 10 Jul 2022 02:23:56 +0000

I made a language and the language now can make instances:

class A {
    pub name = "john";
    pub weight = 10;
    pub fn f() {
        return "cat";
    }
}
let b = new A();
print(b.name);
print(b.f());

Wow, I'm happy for this :)

You sure you will go with Laravel Horizon?

lechat — Thu, 17 Feb 2022 12:55:00 +0000

You sure you will go with Laravel horizon? In some cases, you shouldn't. Especially when you use Redis cluster.

Horizon doesn't work with Redis cluster

Horizon doesn't work with Redis cluster if it has multiple shards. But this is not mentioned in the doc. You will notice it when you increase number of shards of Redis cluster, or when you find this issue. As a workaround, I tried hash tag keys, but Laravel horizon still didn't work alongside Redis cluster with mutiple shards.

Laravel queues work with Redis cluster?

On the other hand, queues of Laravel seems working with Redis cluster. It's confusing to me. Please note that I haven't tested queues alongside Redis cluster with multiple shards, so actually I don't know if it really works, but queues seems better bet.

Even if you go with laravel queues, if you use database driver with MySQL that is older than 8.0, it might cause deadlocks. I think this is not mentioned in the doc too.

You cannot use multi/exec/watch/unwatch in Redis cluster with multiple shards (at least with predis)

You know, to keep data consistency, you sometimes must use watch/unwatch/multi/exec (to start something like transaction) to save dave data in Redis. But this doesn't work in redis cluster. It might work in your dev environment that uses single Redis node but not in production that uses Redis cluster with multiple shards.

Conclusion

In some situations, queues is a better bet.

I made an android app that has JS quizzes and you can write and run answers inside

lechat — Tue, 21 Sep 2021 15:30:11 +0000

Do you know websites like Confingbat? I really like that kind of websites and spent a lot of time to solve programming quizzes there.

But, after solving many quizzes there, I wondered if there is an android app where you can do something like that. It would be better if I could solve quizzes on android app. You know, it would be more relaxing if I could do it on sofa or bed with my phone.

Well, as far as I searched, I could not find any android app like that.

So I made such android app by myself. On this Android app, with Javascript, you can solve quizzes by writing and running the answer directly on the app.

https://play.google.com/store/apps/details?id=com.notesoneverythin.jsprogrammingprac

SPA with Springboot+JWT+Vue.js+Web socket

lechat — Sun, 20 Jun 2021 12:59:06 +0000

As I wrote before, I made a SPA with Springboot+JWT+Vue.js+Web socket, but only a few people tested it, maybe because, to test the project, people needed to prepare Postgresql by themselves. It is really tiring to install and init DB. Even worse, it is also tiring removing DB once it is installed.

So, today, I moved the Postgresql DB in docker container. And if you want to test my project, you can do the preparation almost automatically. And it is very easy to remove containers after testing.

You can test the project from here:
https://github.com/lechatthecat/JavaChatSPA

How to test the project

Prerequisites

Java 11
Maven 3.*
Docker 20.10.6
Docker-compose 1.29.1

How to run:

$ git clone https://github.com/lechatthecat/JavaChatSPA.git
$ cd JavaChatSpa
$ docker-compose up -d --build
$ npm i
$ npm run build
$ mvn clean package
$ mvn spring-boot:run

Working example:
https://chatboard.page/boards/lounge/0

Let's use reduce, map, filter, foreach and be more functional in javascript

lechat — Fri, 16 Apr 2021 15:50:51 +0000

console.log([1,2,3,4].reduce((x,y) => { return x  + y })) // 10 
// Elements reduced to one value

console.log([1,2,3,4].map((x) => { return x  + 5 })) // [6,7,8,9] 
// Do something for each value and make a new array

console.log([1,2,3,4].filter((x) => { return x  % 2 === 0 })) // [2,4] 
// Filter the elements and make a new array

const array1 = [1, 2, 3, 4];

array1.forEach(x => { console.log(x)});
// For each loop.

As a first project in Rust, I made a programming language on my own

lechat — Sat, 20 Mar 2021 14:23:52 +0000

This is the project:
https://github.com/lechatthecat/oran

You can test it by:

$ git clone https://github.com/lechatthecat/oran.git
$ cd oran
$ cargo build --release
$ ./target/release/oran -f ./examples/hello.orn
$ ./target/release/oran -f ./examples/example.orn

Motivation

1. Rust seems cool, so I wanted to make something.

And I think it is a very nice language.

2. String concatenation or addition of numbers?

In many scripting languages, the concatenation of string is done by "aaaa" + "bbbb". This will make a value "aaaabbbb".

I really don't like this syntax. Let's suppose that we just want to add up two integers:

let val = 5 + 6;

and what if they happen to be String typed integers?

let val = "5" + "6";

The variable val's value will end up being "56" because both of them are String, not integers.

If they aren't stored in variables, it is obvious that you need to change them to numbers beforehand, but what if they are stored in variables?

let val = varfive + varsix;

The value of val cannot be known until I check the value in debug mode. Even though I just wanted 11 out of 5 + 6, the value is actually "56". This would cause a serious bug.

The problem is, in most scripting languages, you cannot know what type the variables have. In scripting languages, variable types are dynamically changed.

So in my language, you have to use "<<" to concatenate string values:

fn test () {
    let test = ' test';
    for i in 0..5 {
        println(i << test); // Like this.
    }
}
test();

When "<<" is used, the variables are always treated as String. Meanwhile, when "+" is used, the variables are always treated as numbers.

3. Immutability

Immutable variables are not often used in scripting languages like PHP, Python, Ruby. But immutable/mutable variables are often used in Javascript by putting const/let in front of variable names. I feel this is quite useful feature, that should be available in PHP, Python, Ruby also. And if variables are immutable by default like in Rust, it is even better.

So in my language, variables are immutable by default.

fn test () {
    let test = 'hey'; 
    test = "hello"; // Error!!
    println(test);
}
test();

You have to use mut to make it mutable variable.

fn test () {
    let mut test = 'hey'; 
    test = "hello"; // Now it works.
    println(test);
}
test();

Conclusion

Rust is a great language even though I am not familiar with this language at all. The good point of Rust is, the more I learn this language, the more nice things I can get to know, like, immutable variables, option and match, memory management, difference between passing by val and by ref, functional programming style etc...

DEV Community: lechat

I Built a Laravel-like Web Framework for Rust

What Willow Forge Is

Why I Built It

Who This Is For

Create a k8s development environment by Minikube

Prerequisites

Download tools

Minikube start (minikube cluster)

terminology

What are Containers?

What are Pods?

What is a Cluster?

Start a minikube cluster

Create pods

Mount /var/www/html to the host PC and access the file through ingress

Use MariaDB from host pc

I'm scared of AI that automates coding in very high level..

Building a Developer-Focused Search Engine in Rust: Lessons Learned and Challenges Overcome 🚀

🎯 The Mission

🚧 Challenges Faced

Search by Elasticsearch is slow 😢

The Solution

Too Many Malicious Users Scanning the Website 👽

The Solution: Fail2Ban

Defined a Fail2Ban Jail for Nginx:

Filter to Detect Malicious Patterns:

Dynamic Blocking in Action:

Adsense not showing 😿

The Solution

Unsolved Problems

🙏 Thanks for Reading!

I created a simple app by very fast Rust web framework Actix web. Please use this as a sample code.

Background

How to use

For development

What does the app do?

Structure

Overview

Additional Recommendations

How to "permanently" remove annoying websites from your google's search result

Motivation

Android

PC chrome

References

See also

My language now can make instances

You sure you will go with Laravel Horizon?

Horizon doesn't work with Redis cluster

Laravel queues work with Redis cluster?

You cannot use multi/exec/watch/unwatch in Redis cluster with multiple shards (at least with predis)

Conclusion

I made an android app that has JS quizzes and you can write and run answers inside

SPA with Springboot+JWT+Vue.js+Web socket

How to test the project

Let's use reduce, map, filter, foreach and be more functional in javascript

As a first project in Rust, I made a programming language on my own

Motivation

1. Rust seems cool, so I wanted to make something.

2. String concatenation or addition of numbers?

3. Immutability

Conclusion