WWNIT SOLUTIONS
RUEN

Hi! I'm Ivan.

I build services and automate processes. I help with infrastructure, launch and ongoing support.

Solutions

Service development, infrastructure and automation for a specific challenge.

Cases

Real challenges, the solutions and the project outcomes.

Process

From the first conversation to launch and support.

Journal

Engineering notes and articles from practice.

Research

Technical studies, experiments and scientific publications.

Resume

Work experience, skills and a PDF resume.

Have a project in mind?

Get in touch through Telegram or email.

WWNIT Solutions
RUEN

Cases

Back
WWN
IT SOLUTIONSPROJECT FILE01 / 05

CLOUD-NATIVE PLATFORM

Launching projects in the cloud

The user connects a project from GitHub or GitLab. The platform detects the stack, prepares dependencies and launches the application in the cloud. The user gets a project URL and logs.

01

Challenge

Launch the project without setting up its environment

The user already has a project in GitHub or GitLab. They want a running service quickly, without spending time choosing tools, installing libraries and preparing a cloud deployment. They need a short path from repository to running application.

02

Solution

Project preparation and launch in one platform

The web platform combines repository connection, project preparation and cloud launch. Stack detection and preparation of the required tools and libraries happen on the platform. The user works through the interface and receives the application URL and logs.

03

In practice

Repository → launch → URL and logs

The user does not have to assemble the environment manually: the platform prepares and launches the project.

  1. The user connects a project from GitHub or GitLab and clicks the launch button.

  2. The platform retrieves the project, detects its stack and prepares the required tools and libraries.

  3. The application launches in the cloud. The user receives a URL to open it and its logs.

Technical diagram and tools
Technical diagramLOGICAL CONNECTIONS

→ action or data flow · — functional relationship. Repeated blocks refer to the same component.

Application

  1. Next.jsPlatform interface
    Requests
  2. FastAPIPlatform backend
    Tasks
  3. CeleryBackground tasks

Build

  1. GitSource code
    Source code
  2. CI/CDBuild and delivery

GitOps

  1. GitEnvironment definitions
    Desired state
  2. Argo CDGitOps
    Reconciliation
  3. KubernetesApplication environment

Environments

  1. Terraform · AnsibleInfrastructure as code
    Environment setup
  2. KubernetesApplication environment

Argo CD reconciles the cluster with configuration in Git. CI builds and GitOps reconciliation are separate processes.

Next.js
Platform interface
FastAPI
Platform backend
Celery
Platform backend
Git
Source code
CI/CD
Build and delivery
Argo CD
GitOps
Kubernetes
Shared DevOps work
Terraform · Ansible
Infrastructure as code

Next.js · Terraform · Ansible · Kubernetes · Argo CD

04

Outcome

From repository code to a running application

The user gets a URL for the cloud-hosted project and access to its logs. Tool selection, dependency preparation and launch are handled by the platform instead of requiring separate manual setup by the user.

  • Launching a GitHub or GitLab project through the interface.
  • Stack detection and preparation of tools and libraries on the platform.
  • A running application URL and logs for the user.