Progress in my DevOps journey: manually wrote a systemd service file for Tomcat.
Learned how strict systemd is about syntax, User, WorkingDirectory, ExecStart vs ExecStop. Got it to active (running) and enabled on boot.
#BuildInPublic#DevOps#Linux
Progress in my DevOps journey: automated a full website setup with one Vagrant provisioning script.
Install httpd, download and extract a site template, deploy to Apache's web root, restart the service. Fresh VM boots up already serving a live website.
#BuildInPublic#DevOps
Progress in my DevOps journey: set up WordPress on Ubuntu.
Downloaded and extracted via a single piped curl+tar command as www-data, configured Apache, enabled the site with a2ensite.
From installing a web server to hosting something on it.
#BuildInPublic#DevOps#Linux
Progress in my DevOps journey: covered Syncing Directories in Vagrant.
Custom synced folders (scripts to /opt/scripts), networking, and resource allocation (memory/CPU), all defined in the Vagrantfile and applied with vagrant reload.
#BuildInPublic#DevOps#Vagrant
Progress in my DevOps journey: wrapped up Git, branching, rollbacks, SSH auth, tags, and semantic versioning.
Doing it all from the terminal now, commit, tag, push.
#BuildInPublic#DevOps#Git
Progress in my DevOps journey: wrapped up Archiving.
tar, zip, unzip, compressing and restoring files cleanly. Simple but genuinely essential for backups and log management on real servers.
#BuildInPublic#DevOps#Linux
Progress in my DevOps journey: rounded up Processes.
ps -ef, kill vs kill -9, PID/PPID, orphans and zombies, watching httpd processes spawn, die, and restart in real time.
#BuildInPublic#DevOps#Linux
Progress in my DevOps journey: wrapped up package management.
dnf, rpm, dependency resolution, and a real DNS troubleshooting detour along the way (broken resolv.conf, fixed with 8.8.8.8).
Understanding what's happening underneath the commands now
#BuildInPublic#DevOps#Linux
Progress in my DevOps journey: wrapped up Users and Groups, File Permissions, and Sudo.
Understanding UIDs, GIDs, chmod, and how sudo/visudo control privilege escalation safely.
Security fundamentals, not just commands to memorize.
#BuildInPublic#DevOps#Linux
Progress in my DevOps journey: wrapped up Linux redirections.
, >>, <, |, 2> โ small operators that let you chain simple commands into powerful pipelines.
#BuildInPublic#DevOps#Linux
Looking for full-stack/backend roles (Python/FastAPI, Node.js, React, PostgreSQL, MongoDB).
Built a payment processor with double-entry bookkeeping and a multi-tenant SaaS platform, both production-ready.
4+ years experience, available immediately.
Know anyone hiring? ๐
Rounded up Linux file types (regular, directory, link, block) and filters like grep and cut.
Linux is starting to feel less like memorized commands and more like a toolkit.
#BuildInPublic#DevOps#Linux
@shikheronline You are very correct. Understanding the reason for hypervisors form the core of DevOps. Also, after going through the hassle of manual installation of CentOS and Ubuntu on VirtualBox which took several hours, I appreciated Vagrant a lot, took few minutes.
Progress in my DevOps journey: virtualization.
Learned Host, Guest VM, Hypervisor (Type 1 vs Type 2).
Clean win with Ubuntu Server, logged in via Git Bash.
Next: Vagrant.
#BuildInPublic#DevOps
Wrapped up Vim, mode-based editing clicked, plus practical shortcuts: :se nu, gg/Shift+G, dd, yy, p/P.
Now on to Linux file types, learning how everything on a Linux system is represented as a file.
#BuildInPublic#DevOps#Linux
Wrapped Linux fundamentals: paths, permissions, navigation, writing to files.
Compared CentOS vs Ubuntu, different prompts and package managers, same core commands underneath.
Now diving into Vim. Time to stop relying on nano.
#BuildInPublic#DevOps#Linux
Vagrant automation just clicked for me.
After manually installing CentOS and Ubuntu (and the network struggles that came with it), spinning up VMs with Vagrant felt like magic.
vagrant up = instant VM from a prebuilt box.
#BuildInPublic#DevOps