DevOps
Culture and practices unifying software development and operations – containerization, CI/CD pipelines, infrastructure management, and monitoring.
DevOps and CI/CD
I get your website running on your own VPS or in the cloud — to the modern standards you already expect from development: everything in Docker, infrastructure described as code, and every change deployed through a CI/CD pipeline that tests it first. Deploying to a VPS or the cloud Based on traffic and budget I pick what makes sense: a virtual server or AWS. I build the environment in Docker, so it is reproducible and identical in development and production. I prepare it alongside your current setup and switch over once it is verified.
Claude Plugins – Skills for Claude Code
Status: Active development This repository contains a collection of Claude Code Skills that extend Claude Code with specialized knowledge and best practices for web application development. The project is available on GitHub: https://github.com/siva01c/claude-plugins Currently Available Skills Drupal Skills focused on Drupal development. They include best practices for: Module development Drupal Coding Standards Composer Drush DDEV Common development workflows Security Skills focused on web application security. They include guidance and reviews based on:
Website Maintenance
A website is not finished on launch day. Security updates come out, modules age and PHP versions reach end of life. I take over looking after your site – whether I built it or someone else did – and keep it up to date, backed up and safe to change. What follows is what I actually do for clients, not a catalogue of promises. What maintenance covers Security patches – I follow Drupal’s security advisories and roll out core and module patches as a priority once they are released. Daily backups with an off-site copy – the database and files are backed up every day and the copy is kept somewhere other than the site. The backup comes with a written restore procedure, so it is clear how to bring the site back instead of working it out when it is needed. Tests and CI before release – every update and change goes through automated checks and tests in CI first, and only then to production. Secure operation – passwords and keys kept out of the repository, separated access, and a server set up to expose no more than it has to. Ongoing updates and upgrades – modules, libraries and PHP, so technical debt does not pile up, and upgrades between major Drupal versions including changes to custom code. How we work together Initial review – I go through the site, the code and the hosting and write down what needs putting in order. Putting things in order – updates, backups, CI and fixes for what the review found. Regular maintenance – patches, updates and small improvements as needed. We size the scope to the site. I track my time and invoice the hours worked, so you pay exactly for what needed doing.
ClawBot – Agentic Ops Manager (IronClaw)
Status: Active development ClawBot is an agentic Ops Manager built on IronClaw. It orchestrates a team of specialized agents behind a unified MCP gateway, handling weekly SEO audits, daily OSINT monitoring, real-time support, and automatic knowledge base updates. It also manages the onboarding of new e-commerce stores and keeps Drupal and Hugo content in sync. Key features Unified MCP gateway with 20+ tools (RAG CMS, SEO crawler, OSINT, Sales) Scheduled tasks: weekly SEO audits, daily OSINT monitoring, and daily support gap analysis CMS/RAG integration: Drupal content synchronized with the knowledge base Automation: background tasks, reminders, and Canvas previews Docker-based stack for both local development and CI