👨‍💻 Enea Zani’s Post

📝Day10 of Sharing my DevOps Series... Docker files Ubuntu + Apache Dockerfile FROM ubuntu:22.04 RUN apt-get update && apt-get install apache2 -y COPY index.html /var/www/html/ EXPOSE 80 CMD ["apachectl", "-D", "FOREGROUND"] python docker file FROM python:3.11-slim WORKDIR /app COPY requirements.txt . RUN pip install -r requirements.txt COPY . . EXPOSE 8000 CMD ["python", "app.py"] Node.js file FROM node:20-alpine WORKDIR /app COPY package*.json ./ RUN npm install COPY . . EXPOSE 3000 CMD ["node", "server.js"] Java docker file FROM maven:3.9-eclipse-temurin-17 WORKDIR /app COPY . . RUN mvn clean package EXPOSE 8080 CMD ["java", "-jar", "target/app.jar"]

Most bash scripts I've seen in the wild are missing three flags that could prevent serious production damage. When I started learning bash scripting as part of my Linux fundamentals work, I came across this: #!/bin/bash set -euo pipefail Two lines. Every professional script should start with them. Here's why each flag matters: -e — Exit immediately if any command fails Without this, bash happily continues running after an error. Your script fails silently on step 3 and keeps executing through step 10. In production that means partial changes, broken state, and damage that's hard to trace. -u — Treat undefined variables as errors Without this, a typo in a variable name becomes an empty string. That empty string gets passed to commands, used in file paths, or fed into conditionals — and your script keeps running with garbage data. -o pipefail — Catch failures inside pipes Without this, a command like: failing_command | grep foo ...returns success because grep succeeded, even though the first command failed. Pipe failures are completely invisible without this flag. Three flags. One line. The difference between a script that fails safely and one that causes silent damage. I wrote six scripts this week working through bash fundamentals — from hello world to argument validation, loops, functions, and error handling. Every single one starts with this header now. Small habits. Production mindset from day one. All notes are documented and versioned in my homelab GitHub repo. #Linux #Bash #DevOps #Scripting #Homelab #BuildInPublic #SRE

Three dev tooling updates worth knowing about today. 🛠️ IntelliJ IDEA 2026.1: Cursor integration and platform upgrades Cursor now plugs into IntelliJ through the ACP Registry. This release also adds Java 26 support, makes Wayland the default on Linux, and expands built-in JavaScript and TypeScript features. Source: https://lnkd.in/eJQqDdFG 🛠️ Windsurf Wave 13: Parallel multi-agent sessions and Git worktrees Wave 13 adds first-class parallel agent sessions, side-by-side Cascade panes, Git worktree support, and a terminal profile aimed at steadier agent runs. SWE-1.5 Free is also the default model for the next three months. Source: https://lnkd.in/eiyhshyY 🛠️ DeepSeek-V4 preview: 1M-token context for long-running agents Hugging Face highlights DeepSeek-V4-Pro and DeepSeek-V4-Flash with 1M-token context, lower per-token compute, and smaller KV cache footprints. That makes long-context coding and tool-use agents more practical to run. Source: https://lnkd.in/eRsap-TK Full intel feed with daily updates: solomonneas.dev/intel

This bug cost me hours and it wasn’t even visible. Pushed code that worked perfectly on my machine. CI pipeline failed instantly on Linux. The culprit? Something most developers never notice. We were migrating a Java Spring Boot application to Azure, with a Bitbucket CI/CD pipeline running on Linux. All tests passed locally on Windows. But the pipeline kept failing with this cryptic error: [ERROR] SomeTest.java:[1,1] illegal character: '\ufeff' [ERROR] class, interface, enum, or record expected No logic issue. No syntax error. The problem was UTF-8 with BOM, Windows had added 3 invisible bytes at the start of Java files. The Linux Java compiler doesn’t accept it. Fix: Re-saved files as UTF-8 without BOM -> pipeline turned green. 7 files affected. Hours saved (after hours lost 😄). Cross-platform differences (encoding, line endings, case sensitivity) can silently break CI pipelines. If you code on Windows but build on Linux, check your file encoding. Invisible characters can break very visible things. #Java #CICD #DevOps #SpringBoot #CloudMigration #TIL

“Bash is only for basic scripts.” That’s what I used to think. Until I tried building something real with it. 💻 So I built a CLI Quiz App using Bash. At first, it felt simple… But things got interesting when I tried to: 🔹 Load questions from a JSON file 🔹 Randomize them every time using $RANDOM 🔹 Show MCQs in the terminal 🔹 Validate answers correctly (this part broke a few times 😅) And that’s where the real learning happened. 🚀 What this project does: ✔️ Dynamically loads questions ✔️ Random question selection ✔️ Interactive MCQ system in terminal ✔️ Instant feedback on answers 🛠️ Tech Used: Bash scripting jq (for parsing JSON) Ubuntu/Linux 💡 Biggest realization: You don’t really learn tools like Git or Bash by watching tutorials… You learn when things break — and you fix them. 🔗 GitHub: https://lnkd.in/gSgmiX5v 📌 What I’ll improve next: Score tracking Timer-based quiz Better user experience If you’ve ever struggled with Git, Bash, or CLI tools — you’re not alone. We all start messy. We improve by building. Utkarsh Agarwal Gunjan Saini Charu Jain SAMI ANAND Dr. Harpal Thethi Lovely Professional University Xebia #Linux #Bash #GitHub #CodingJourney #Developers #lpu #xebia

Bash is the fifth most-used programming language in the world. >49% of developers use it actively -- ahead of TypeScript. And 80% of the Bash code on GitHub is absolute garbage. Not my word: ACM, 2022, 1.35 million scripts analysed. Quoting failures, word-splitting errors, missing error handling. Schoolboy errors across millions of repositories. We are talking about the language that runs on 96.3% of the world's top million web servers. The language in every CI/CD pipeline, every container entrypoint, every deployment workflow. Treated like a weekend hack. See my full rant in first comment -- with the data, the bad tutorials, and some bad language. #Bash #DevOps #ShellScripting #SoftwareEngineering #Linux

After the fifth httpd deployment, permissions start to blur. You migrate a site or push an update, and suddenly the permissions are a mess. Is it www-data? Is it apache? Is it /var/www or /srv/www? I wrote DistroChown to handle the "Permission Drift" automatically. It reads the distro via /etc/os-release and aligns everything to the correct standards (755/644) for your specific distribution (Debian, Rocky, RHEL, SUSE). You literally clone the script anywhere, and run it. 🛠️ Lightweight. No dependencies. A simple Python script. Check it out on GitHub: https://lnkd.in/ddKMCe8Z #Linux #SysAdmin #Python #Automation #DevOps

Today lets know about "what is SHEBANG" in Linux scripting 😊 Shebang is the first line in the script. "#!/bin/bash" it tells the system which interpreter to run the script Without shebang, the system may not know how to run the script properly, it is very important for scripting and automation. now let us write shebang with different interpreters #!/bin/bash - runs with Bash #!/usr/bin/python3 - runs with Python #!/usr/bin/php - runs with PHP #DevOps #Linux #AWS #ShellScripting #CloudComputing #Automation

bdh-linux v4.2.7 is working perfectly on Arch/Manjaro! 🚀 Set up your entire backend dev environment in under 10 minutes — automatically. ✅ Python, FastAPI, PostgreSQL, Docker, Git & more ✅ One command. Zero manual config. ✅ Built for Arch/Manjaro developers pipx install bdh-linux bdh-linux setup Try it → PyPI: bdh-linux Source → https://lnkd.in/gX2fnEXQ Built with ❤️ by the BDH open-source community. #BackendDevelopment #Linux #Manjaro #ArchLinux #OpenSource #FastAPI #Python #DevTools #BDH

bdh-linux v4.2.7is working perfectly on Arch/Manjaro! 🚀 Set up your entire backend dev environment in under 10 minutes — automatically. ✅ Python, FastAPI, PostgreSQL, Docker, Git & more ✅ One command. Zero manual config. ✅ Built for Arch/Manjaro developers pipx install bdh-linux bdh-linux setup Try it → PyPI: bdh-linux Source → https://lnkd.in/gX2fnEXQ Built with ❤️ by the BDH open-source community. #BackendDevelopment #Linux #Manjaro #ArchLinux #OpenSource #FastAPI #Python #DevTools #BDH