Editing Training 2022 Linux team/ (section)

==Training session on Aadani Pariyojna Traning Video - Tetra Support Staff - Manish Singh==

{{#ev:youtube|pbRovM3qp8w|640}}

'''Video summary:''' "Adani Project Training Video" -- an architecture and support-process handover for Adani's LAMP application. Two identical LAMP servers run in active-passive HA (same credentials on both, automatic failover if one goes down), plus a separate UAT server used for pre-production testing. Explains the primary recurring type of ticket: vulnerability-assessment remediation, where Adani provides a spreadsheet of specific vulnerabilities to close, applied identically to both production servers since they're kept in sync -- gives concrete past examples (disabling TRACE method via config changes, tracking exactly which of several possible methods was used for later reference; renewing an expired SSL certificate on both production servers, keeping notes on the config file paths touched at the time for future reference). Covers login access: reached via a client-provided VPN link and URL, with login requiring approval from a specific person (Rakesh) as an access-control step -- new team members needing access must go through him. Explains the collaboration model for fixes that aren't purely infrastructure-level: some vulnerability findings are developer-side (PHP/application-level) rather than server-level, requiring coordination with the client's own dev team or their assessment vendor's team via a walkthrough meeting to fully understand and properly close an issue rather than guessing. Covers service-restart etiquette: when implementing config changes that require restarting Apache or MySQL, the client should always be told the expected downtime up front (e.g. "Apache restart is roughly 30-40 seconds" or a few minutes for other changes) so they can choose a low-impact time to schedule it, rather than restarting unannounced. Clarifies database ownership: Tetra's own team (naming a colleague, Deepika, who handles the PHP/application side) manages the database directly; database credentials aren't kept readily on hand and need to be requested from her via chat when actually needed for a login.