https://github.com/50-course/buildplane

One-stop open-source cloud deployment tool
https://github.com/50-course/buildplane

build-plane developer-tools

Last synced: 24 days ago
JSON representation

One-stop open-source cloud deployment tool

• Host: GitHub
• URL: https://github.com/50-course/buildplane
• Owner: 50-Course
• Created: 2023-08-01T12:24:56.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-08-03T18:52:32.000Z (over 1 year ago)
• Last Synced: 2024-05-01T13:17:20.693Z (6 months ago)
• Topics: build-plane, developer-tools
• Homepage:
• Size: 3.91 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# buildplane

One-stop open-source cloud deployment tool

# User story

_What are some tools (open source or PaaS like Vercel) for a zero-config or interactive wizard method of deploying/Dockerizing almost any web app full-stack repository? At a minimum, run dev tasks in yarn/npm/etc since those are standardized.

 It should also be feasible to automatically detect not all but many common full-stack deployment configuration tasks.

For example detect that the app server is expecting a MongoDB and spin one up using defaults or by scanning code/readme. Of course it won't succeed in every case, but 80% is good enough.

The goal is to pick any recently-updated web app repository on Git Hub and get it fully up and running in minutes, ready to hack on._

# What is BuildPlane?

I once worked on a little deployment script for generic pipelines. The goal of `build-plane` is to create an easy cloud deployment tool, taking off about 35% of solo developers, teams, and business ops pain of a rigorous deployment process.

# Roadmap

- [ ] Support deployment to popular platforms; Vercel, Heroku, DigitalOcean, Render, Azure, and Amazon Web Services

- [ ] Utilize codesense to scan repositories for special configurations files and automatically determine build type

- [ ] Support GitHub and GitLab platforms

This is not an exhaustive roadmap - and very much an envisioned roadmap, call it version `1.0`