QA Artifact

Ubuntu, Terminal, Git, Docker, and WordPress Multisite in Practice

Public artifact showing practical command-line, Git, Docker, and WordPress Multisite usage through the SlotsOne and QA Portfolio Multisite projects.

Artifact content

Public sources: github.com/pyavchik/slotsone, github.com/pyavchik/qa-portfolio-multisite, WordPress Multisite in Practice

This artifact shows practical use of Ubuntu, terminal workflows, Git, Docker, and WordPress Multisite through real project work rather than abstract tool lists.

  • Ubuntu / terminal: shell-based development and operational workflows, command-driven setup, environment checks, and deployment verification
  • Git: repository structure, commit history, branch-based collaboration, GitHub remote workflow, and code-based deployment
  • Docker: local and deployment-oriented container workflows in SlotsOne, including docker compose setup for application services
  • WordPress Multisite: subdomain-based shared architecture with reusable theme and MU plugin logic in QA Portfolio Multisite

SlotsOne is useful evidence of terminal, Git, and Docker usage because the repository includes command-line setup and run flows, Docker Compose files, development scripts, backend/frontend split, and deployment-oriented operational files. Public examples include scripts/dev.sh, docker-compose.yml, docker-compose.prod.yml, and ops/server/bootstrap_deploy_user.sh.

QA Portfolio Multisite is useful evidence of Git and WordPress Multisite practice because it documents a shared-code, multi-site WordPress setup with deployment workflow and admin operating model. Public examples include .github/workflows/deploy.yml, docs/DEPLOYMENT.md, and docs/MULTISITE-ADMIN.md.

The practical value of these tools in QA work is straightforward: terminal usage speeds up setup and verification, Git helps track and review changes, Docker helps create repeatable environments, and WordPress Multisite experience shows I can work with shared architecture, reusable components, and multi-site admin logic in a real product context.

Together, these projects show that I do not treat Ubuntu, terminal commands, Git, Docker, and Multisite as separate buzzwords. I use them as part of real web-product work, deployment flow, environment management, and QA-focused investigation.

Artifact details

Type:

Objective:

Coverage:

Tools

Recruiter note: