https://github.com/myselfakashagarwal/pweb

Portfolio website with containerised & continuous- dev , build & delivery pipeline
https://github.com/myselfakashagarwal/pweb

cicd docker jenkins nginx threejs

Last synced: about 2 months ago
JSON representation

Portfolio website with containerised & continuous- dev , build & delivery pipeline

• Host: GitHub
• URL: https://github.com/myselfakashagarwal/pweb
• Owner: myselfakashagarwal
• Created: 2024-02-23T10:57:19.000Z (10 months ago)
• Default Branch: legacy
• Last Pushed: 2024-08-05T19:44:35.000Z (5 months ago)
• Last Synced: 2024-08-05T22:59:53.964Z (5 months ago)
• Topics: cicd, docker, jenkins, nginx, threejs
• Language: HTML
• Homepage: http://myselfakashagarwal.rocks
• Size: 27.2 MB
• Stars: 0
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        


## About 

pweb is a codebase intigrated, containerised modular pipeline with Continuous Intigrations & Devivery with semi automatic deployments. Used for building webGL portfolio website.

## Components 

- Develop   - for continious intigrations and development

- Build     - for creating deployable builds and pushing them to artifact repository 

- Deploy    - for deployments 

- Update    - for updating old deployments with new ones 

### Develop

The development phase is handled with containers init the complete legacy codebase is mounted with its compatiable environment at the run time, this combination removes the environment dependency errors needed by the legacy codebase but also provides features like hot reload and ability to freely develop in the controlled environment.

### Build 

The build phase is handled by pweb:build containerised instance this image is build on top of jenkins with two jobs pweb_build pweb_push, the build job generates needed generic static files required from the code base using bundler, after that creates a deployable AMI with nginx base image. The deployable build created is then pushed to registery by the pweb_push job. The modularity is such that the builds which are created are stored on the host, configuration files are mounted from the codebase (provides flexibility to change any configurations) and host daemon is used to run containers for tasks inside jobs.

### Deploy & Update 

Meanwhile a cloud VM instance with docker setup is kept running with two instances, one the deployable build created during the build phase and other watch tower. The watch tower handles the work of automatic deployments by automaticially pulling the new builds (on push) and replacing them with old version with same configurations and graceful shutdowns.  

## Working 

The whole pipeline can be abstracted with pweb.yml a docker-compose file which contains multiple configured environments. The profiles are defined within fro spawning envs as per needed, like development profile for development phase build profle for building phase and deploy and update for the cloud.

## Use

(assumed user in present inside the cloned repo)

To spawn the environment ANY 

```bash

docker-compose -f pweb.yml --profile ${DESIRED-ENV} up

```

To spawn the environment for development 

```bash

docker-compose -f pweb.yml --profile development up

```

To spawn the environment for creatinfg and pushing builds 

```bash

docker-compose -f pweb.yml --profile build up

```

To spawn complete pipeline 

```

docker-compose -f pweb.yml --profile pweb up

```