Team & Users

Azure Server Users (4.180.181.86)

Users with home directories on Azure:

User	Access Level	SSH Key	Purpose
kaks	sudo	Yes (philkjehovah@gmail.com)	DevOps — manages all stacks, deploys, infra
ewakoko	user	No	Team member
smallgod	user	No	Development support

Note

Only kaks has an SSH key configured on Azure. The other users have home directories but no SSH key set up.

Contabo Server Users (84.247.134.135)

Users with home directories on Contabo:

User	Access Level	SSH Key	Purpose
pk	sudo	Yes (philkjehovah@gmail.com)	DevOps — deploys, runner management
daphine	user	No	Team member
enock	user	No	Team member
odora	user	No	Team member
sharif	user	No	Team member
smallgod	user	No	Development support
wakoko	user	No	Team member

Caution

There is no kaks user on Contabo. The primary DevOps user on Contabo is pk. All stack files are managed from Azure (where the kaks user lives). Contabo restricts SSH login via AllowUsers in /etc/ssh/sshd_config. Password authentication is disabled — SSH keys only.

GitHub Actions Runners

Runner	GitHub Org	System User	Service
actions.runner.ayinza.vmi2912133	ayinza	pk	systemd on Contabo
actions.runner.sseris.vmi2912133	sseris	sharif	systemd on Contabo

Both runners are active and running on Contabo.

Service Accounts & Credentials

Service	Username	Where Stored	Notes
Harbor	admin	Harbor UI	Container registry admin
Portainer	admin	Portainer UI	Docker management
Keycloak (DEV)	admin	Keycloak admin console	DEV realm management
Keycloak (UAT)	admin	Keycloak admin console	UAT realm management
PostgreSQL (DEV)	—	Docker env vars	In stack YAML
PostgreSQL (UAT)	—	Docker env vars	In stack YAML
RabbitMQ	—	Docker env vars	In stack YAML
docs.ayinza.dev	devops	nginx htpasswd config	Basic auth for this docs site

Note

All service credentials are stored as environment variables in the stack YAML files at /home/kaks/stacks/ on Azure. See Secrets & Credentials for details.

Adding a New Team Member

1. Create their SSH key pair or get their public key
2. Azure: Add public key to the target user’s ~/.ssh/authorized_keys (e.g., /home/kaks/.ssh/authorized_keys)
3. Contabo: Add public key to target user’s authorized_keys, add username to AllowUsers in /etc/ssh/sshd_config, restart sshd
4. Harbor: Create user account in Harbor admin panel
5. GitHub: Invite to the relevant org (ayinza / sseris)
6. Share this docs site: https://docs.ayinza.dev (user: devops)