GitLab CI & Linux Hardening
Budget: $8 – $15 AUD
I’m looking for a seasoned DevOps mind to streamline my GitHub-based CI/CD workflow and tighten the security of a handful of Linux servers.
On the CI/CD side, everything lives in GitLab. I need practical guidance on structuring .gitlab-ci.yml, optimising runner usage, and setting up automated staging-to-production deployments with roll-backs and clear version tagging. If you have shortcuts for caching, parallel jobs, or environment-specific variables, even better.
The servers behind those pipelines also need attention. Your job is to harden them—from SSH policies and firewall rules to OS-level patching and intrusion detection—so they’re production-ready once the pipeline pushes new code.
Deliverables
• A working, documented GitLab CI pipeline that builds, tests, and deploys automatically
• Hardened Linux server configuration with a summary of changes and commands used
• A short hand-off guide so I can maintain and tweak the setup on my own
I’m ready to start as soon as we agree on the approach and timeline.
On the CI/CD side, everything lives in GitLab. I need practical guidance on structuring .gitlab-ci.yml, optimising runner usage, and setting up automated staging-to-production deployments with roll-backs and clear version tagging. If you have shortcuts for caching, parallel jobs, or environment-specific variables, even better.
The servers behind those pipelines also need attention. Your job is to harden them—from SSH policies and firewall rules to OS-level patching and intrusion detection—so they’re production-ready once the pipeline pushes new code.
Deliverables
• A working, documented GitLab CI pipeline that builds, tests, and deploys automatically
• Hardened Linux server configuration with a summary of changes and commands used
• A short hand-off guide so I can maintain and tweak the setup on my own
I’m ready to start as soon as we agree on the approach and timeline.