Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans and versioning #79

Closed
quentinguidee opened this issue Oct 16, 2023 · 1 comment
Closed

Plans and versioning #79

quentinguidee opened this issue Oct 16, 2023 · 1 comment

Comments

@quentinguidee
Copy link
Member

quentinguidee commented Oct 16, 2023

GitHub release (with filter)

About

Currently, there are no good self-hosted softwares that I like to manage my self-hosted environment. There are tools to manage containers, tools to manage network, etc. But none of these can be setup in 2 minutes like most Cloud Providers platform do.

Vertex aims to fix this gap by doing a fully open-source software (MIT License), visually appealing, easy to use, and with a very low learning curve.

Current plans

The main goal of Vertex is to have a powerful platform (like some Cloud Providers have), but as a self-hosted service.

Vertex will first stabilize its API and apps. Then, plan to support entirely 3rd party apps, with a plugin system. Vertex architecture is already designed with this idea in mind. After that, move forward to support horizontal scaling.

Future plans are not determined yet, but a cool idea would be to export parts of Vertex as packages, to benefit the community outside of the self-hosted community.

Note

These packages will be created at least after the 1.0 release, as Vertex is still doing big changes to its codebase.

Versioning

Definition:
If the version is 1.2.3, 1=major 2=minor 3=patch.

Before Vertex 1.0

Before Vertex 1.0, major changes are pushed on each new minor releases. (e.g. Between 0.11.x and 0.12.0). This means that:

  • Breaking changes can appear between two minor versions if you use the external API
  • Security is not guaranteed at all, we strongly recommend to keep all Vertex ports private.
  • If you want to propose a big change in the architecture of Vertex, this is the ideal time to propose it!

That being said, I use Vertex in a daily basis, running 24/24 in my production environment, which means that:

  • Vertex is working perfectly in its current state
  • Vertex has a migration tool to support automatic updates between the versions
  • All pushed versions already have a pretty good stability.

After Vertex 1.0

After Vertex 1.0, major changes will only be done on major releases. (e.g. Between 1.x.x and 2.0.0) You'll therefore be able to use it for larger environments after this release.

@quentinguidee quentinguidee pinned this issue Oct 16, 2023
@vertex-center vertex-center locked and limited conversation to collaborators Oct 16, 2023
@quentinguidee
Copy link
Member Author

To discuss about this, please do one of the following:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant