https://github.com/tbauriedel/resource-nexus

Graphical user interface for terraform provisioning
https://github.com/tbauriedel/resource-nexus

gui terraform

Last synced: 5 months ago
JSON representation

Graphical user interface for terraform provisioning

• Host: GitHub
• URL: https://github.com/tbauriedel/resource-nexus
• Owner: tbauriedel
• License: mit
• Created: 2025-12-14T16:41:31.000Z (7 months ago)
• Default Branch: main
• Last Pushed: 2026-01-06T13:31:09.000Z (6 months ago)
• Last Synced: 2026-01-09T08:25:22.032Z (6 months ago)
• Topics: gui, terraform
• Language: Go
• Homepage:
• Size: 2.97 MB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Notice: NOTICE.md

Awesome Lists containing this project

README

          
[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)

![Go Version](https://img.shields.io/badge/go-1.25.3+-blue)

![GoLang CI](https://github.com/tbauriedel/resource-nexus/actions/workflows/go.yml/badge.svg)

# resource-nexus

> `resource-nexus` is under development. A first release candidate will be released "soon".

Graphical user interface to manage Terraform resources, without dealing directly with the configuration files or the underlying infrastructure.

More details can be found in the [idea description](./IDEA.md).

## Components

`resource-nexus` consists of two components.

### resource-nexus-core

**resource-nexus-core** is the backbone of the whole stack.  

Triggered via REST API, resource-nexus-core executes Terraform commands to provision infrastructure.

Source code and detailed documentation is located under [resource-nexus-core](resource-nexus-core)

### resource-nexus-web

Not developed yet.

# Development

Please make sure to read the following guidelines before contributing to `resource-nexus`.

Contributing "rules" can be found [here](./CONTRIBUTING.md).

## Commit messages

Since this is a "mono-repository" for more than one component of `resource-nexus`, consistent commit names are important. This allows commits to be grouped and assigned to the corresponding component.  

Commit naming:

- `gh-actions - ...`: Prefix for GitHub Action changes

- `resource-nexus-core - ..`: Prefix for backend changes

- `resource-nexus-web - ...`: Prefix for frontend changes

Changes that are not part of actions, backend or frontend doenst need a consistent prefix.

It is important to separate changes to the backend and frontend into separate commits.

# Disclaimer

`resource-nexus` is an OSS project that uses and builds on Terraform. It is not affiliated with HashiCorp or Terraform.

# LICENSE

MIT © Tobias Bauriedel