https://github.com/jamesread/vitae

The lifecycle tool for your software. Plan, Visualize, Document, Integrate, and Replace.
https://github.com/jamesread/vitae

maturity-prototype

Last synced: 9 months ago
JSON representation

The lifecycle tool for your software. Plan, Visualize, Document, Integrate, and Replace.

• Host: GitHub
• URL: https://github.com/jamesread/vitae
• Owner: jamesread
• Created: 2013-12-30T14:08:41.000Z (over 12 years ago)
• Default Branch: main
• Last Pushed: 2025-04-11T23:58:09.000Z (about 1 year ago)
• Last Synced: 2025-10-13T14:24:37.646Z (9 months ago)
• Topics: maturity-prototype
• Language: JavaScript
• Homepage: http://jamesread.github.io/Vitae/
• Size: 1.98 MB
• Stars: 6
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • Code of conduct: CODE_OF_CONDUCT.md
  • Security: SECURITY.md

Awesome Lists containing this project

README

          


  

  
Vitae

  (recently renamed from SolutionBuilder)


The lifecycle tool for your software. Plan, Visualize, Document, Integrate, and Replace. 

![Maturity Badge](https://img.shields.io/badge/maturity-prototype-red)

[![Discord](https://img.shields.io/discord/846737624960860180?label=Discord%20Server)](https://discord.gg/jhYWWpNJ3v)



# Screenshots 

Playing around with some ideas. This was a project I developed back in about 2012, and I've recently just added some new apps as it might be useful for people's homelabs. 

![image](var/screenshot1.png)

# Use cases

1. **Plan** your deployment - does it have an IP address, a vlan, which host will it be deployed to. What are the problems I hope this deployment will solve? 

1. **Visualize** - how the software relates to hardware, clusters, stacks, VMs, Containers, and their relationships, all without having to draw boxes. Click and browse abuilt-in database of self hosted software.

   1. Future idea: scan your network, or docker.sock, and build the diagram automatically.

   2. Future idea: "Enhance" - zoom in on portions of the diagram to show a single server, or single docker network.

   3. Future idea: easily toggle areas of the diagram, like VLANS, IP Addresses, etc.

   4. Future idea: export as PNG, SVG, etc

     

3. **Document** the various parts of your infrastructure. Pull in notes in any markdown format. Prompts you to add the "why" to the "what". Why are we using Fedora here, or KVM, or Proxmox? Add those notes.

   1. eg: How is this part of the infrastrucutre backed up?

   2. eg: How is this part of the infrastructure authenticated?

   3. eg: Does this part of the infrastructure rely on an unstable release?

      

5. **Integrate** - suggests popular integration points 

   1. Future idea: eg: App A has a plugin for the App B you are using.

   2. Future idea: eg: App A and App B both support OIDC.

6. **Replace** - from your requirements, explore alternatives and replacments. 

   1. Future idea: Easily browse alternatives for a Load Balancer, that meet your requirements (eg, like a selfhosted AlternativeTo.net).