Developer Onboarding

Developer Onboarding

Welcome to the Wealthy platform! This guide will help new developers get up to speed with our systems, tools, and development processes.

Getting Started

Follow these steps to successfully onboard as a developer on the Wealthy platform:

Step 1: Environment Setup

• Set up development environment
• Install required tools and dependencies
• Configure IDE and development tools
• Access version control systems

Step 2: Platform Overview

• Understand the Wealthy platform architecture
• Review system components and services
• Learn about our technology stack
• Study API documentation

Step 3: Access and Permissions

• GitHub Access: Contact tmahesh@wealthy.in for repository access
• VPN Setup:
  1. Download and install Pritunl Client
  2. Login to https://vpn53.wealthy.systems/login using your Google account
  3. Copy the profile link after login
  4. Import the profile into Pritunl Client and connect
• GCP Access: Contact tmahesh@wealthy.in for dev and prod GCP environment access
• General Access Requests: Use the #access-approval Slack group for any other access needs

Step 4: Kubernetes Cluster Access

Prerequisites

Install the following tools using Homebrew:

1brew install google-cloud-sdk
2gcloud components install gke-gcloud-auth-plugin
3brew install azure-cli
4brew install --cask openlens

After installation, contact tmahesh@wealthy.in to grant you access to the clusters.

GKE Production Cluster Setup

1. Authenticate with Google Cloud:

   1gcloud auth login
   

2. Get cluster credentials:

   1gcloud container clusters get-credentials wealthyprod --zone asia-south1-a --project wealthy-prod-app-669
   

AKS Development Cluster Setup

1. Authenticate with Azure:

   1az login
   

2. Set the subscription:

   1az account set --subscription 5aca110d-cddd-4c1a-814c-8fae51a68859
   

3. Get cluster credentials:

   1az aks get-credentials --resource-group wealthy-dev-rg --name wealthy --overwrite-existing
   

OpenLens Configuration

By default, OpenLens imports all clusters added in the kube config. If clusters don’t appear automatically:

1. Navigate to your kubeconfig:

   1cd ~/.kube
   2cat config
   

2. Copy the complete config file content

3. In OpenLens:

   • Go to Browse clusters in catalog
   • Click Add from kubeconfig
   • Paste the content copied
   • Click Add clusters

The clusters will now show up in OpenLens.

Step 5: Code and Documentation

• Clone repositories and codebases
• Review coding standards and guidelines
• Understand testing procedures
• Familiarize with deployment processes

Step 6: Team Integration

• Meet the development team
• Join relevant communication channels
• Join Telegram alerts channel for system notifications
• Understand project management workflows
• Review current sprint and roadmap

Resources

Documentation

• Home - Platform overview and getting started
• Teams - Team structure and organization
• Products & Services - Platform capabilities
• Applications - Client applications
• API Reference - Trading API documentation

Development Tools

• Version Control: Git workflows and branching strategy
• Project Management: Issue tracking and sprint planning
• Communication: Team channels and meeting schedules

Support

• GitHub & GCP Access: Contact tmahesh@wealthy.in
• Grafana Monitoring Access: Contact tmahesh@wealthy.in for http://graf.wealthy.systems/
• Airflow Access: Contact tmahesh@wealthy.in for http://airflow.wealthy.systems/
• OpenLens Kubernetes Access: Contact tmahesh@wealthy.in for Kubernetes cluster access
• Hardware & Laptop Setup: Contact Bomesh Bahadur
• General Access Requests: Use #access-approval Slack group
• Technical Questions: Development team leads
• VPN Issues: IT support team
• General Onboarding & HR: Contact manjunath@wealthy.in

Next Steps

Once you’ve completed the onboarding checklist:

1. Start with your first assigned task or project
2. Participate in code reviews and team meetings
3. Contribute to documentation and knowledge sharing
4. Provide feedback on the onboarding process

This onboarding guide is continuously updated. Please provide feedback to help improve the experience for future developers.