Deployment Evidence
Docker, Git and GitHub Versioning
This page documents how the portfolio is prepared for Docker-based local review and a dedicated GitHub repository. The scope is isolated to this subdomain project.
Docker-ready project
The subdomain ships with `docker-compose.yml`, `README.md` and an isolated layout for local review of the WordPress stack without touching the other services on this server.
docker-compose.yml
Git versioning scope
The intended versioning scope covers only portfolio assets: theme, plugin, MU plugins, deployment files, README and documentation. WordPress core, uploads, cache and secrets stay out of version control.
.gitignore
GitHub publication
The published folder is not initialized as a Git repository on this server yet, but it already contains the structure required for publication and rollback tagging.
git init && git remote add origin git@github.com:YOUR_USER/portfolio.fusioncore.com.br.git
Repository commands
cd /var/www/portfolio.fusioncore.com.br
git init
git add README.md docker-compose.yml .gitignore public/wp-content/themes/lago-process public/wp-content/plugins/lucas-portfolio-toolkit public/wp-content/mu-plugins deployment
git commit -m "Initial portfolio.fusioncore.com.br source snapshot"
git branch -M main
git remote add origin git@github.com:YOUR_USER/portfolio.fusioncore.com.br.git
git push -u origin main