Releases: vertex-center/vertex
Releases · vertex-center/vertex
v0.17.0
Changelog
Added
- Each app can now run as microservices instead of a single process if scalability is needed.
- Ability to run apps in Kubernetes.
- New Vertex Logs app, aggregating all the logs from the server.
- Requests can be followed with
X-Request-ID
andX-Correlation-ID
headers. - Multiple emails per user.
- Create container from image name.
- Move the container app to a new database storage, allowing for more flexibility and scalability.
- The container owner is stored.
- Tags can be shared between containers.
- Use of the vertex-center/uuid library for better UUID documentation in the OpenAPI specs.
- Better errors propagation.
- More flexible API domains.
- Improved environment variables display.
Changed
- Services are now called templates.
- URL paths are simplified.
- The containers API returns smaller responses.
- The containers search and getAll endpoints are now merged.
- Containers now use Volumes instead of Binds.
Removed
- Vertex Service Editor removed.
- Vertex Admin Kernel removed.
- Admin: Remove the ability to add ssh keys. This is because is is harder to maintain from a Docker container.
- Admin: Remove the ability to see hardware information. This is because this was not reliable enough.
v0.16.0
Changelog
Added
- Vertex now support user accounts.
- Adding an SSH key can now be made for different users.
- New internal database for Vertex, with SQLite or Postgres.
- The internal database can be changed at any time from the admin settings.
- Vertex can now retrieve more information about the host, and supports CPUs listing.
- Check for server health on startup and at any time from the admin settings.
Changed
service.yml
v2: The ports are now defined by name instead of by default value.- The API and client URLs are cleaner and more consistent.
Fixed
- Fix an issue where recreating a container would also recreate the volumes.
- Fix an issue where the update page would not display correctly when loading.
- Fix issues with ssh keys not being installed correctly.
v0.15.0
Warning
This release introduces breaking changes in the volumes management. Please read the migration guide to learn more.
Changelog
Fixed
- Fix an issue where deleting a container failed if the volume was using custom UID/GID.
Removed
- Remove the migration tool, as it is not flexible enough for now.
v0.14.0
Changelog
Added
- Move many components to the new Vertex Components library.
- Retrieve the user from ENV variables to simplify the kernel launch.
- Support for docapi to generate the API documentation.
- APIs are now documented at Vertex Docs
beta
.
Changed
- The baselines are moved to https://bl.vx.arra.cloud/
Fixed
- Fixed margins everywhere
v0.13.1
Changelog
Added
- Entirely new update process with unified updates and more reliable beta channel.
- Improve the modularity of the server source code.
- Create a new components library that can be used by third-party apps.
- Allow apps to register their own Vertex Monitoring metrics.
- Allow apps to register code running on Vertex Kernel.
- Add a new developer tool to generate
service.yml
. - Support for 201 and 422 HTTP status codes in the API (vertex#86).
- When linking a database to a service, the database name can now be changed (vertex#87).
Fixed
- Fix an issue where vertex could fail to update if the executable was not found.
- Fix an issue where updates could be executed by multiple clients at the same time.
- Fix an issue where empty redirections could be created in the reverse proxy (vertex#85).
- Fix an issue where setting a database in Vertex Containers could corrupt the environment file (vertex#87).
- Fix the container service update process that did not detect new updates.
Contributors
- @AshwinKul28 - Reverse Proxy: Disallow empty string in source/target (vertex#85).
- @Syycorax - Added 201 and 422 http codes (vertex#86).
- @MinhDuongg - Add custom database name support (vertex#87).
v0.12.1
Changelog
Added
- Completely move to a multi-applications model. This will allow to create third-party apps for Vertex in the future.
- New Vertex SQL app for relational databases management.
- Complete overhaul of the API.
- Auto-start a Postgres instance for Vertex.
- Improve the API calls from the UI with caching and retries.
- Improve global design.
Changed
- Rename the Vertex Instances app to Vertex Containers.
- Rename
instance_settings.json
tosettings.yml
. - Container tags are now readable names instead of ids.
Fixed
- Fixed some errors with the logs.
v0.11.0
Changelog
Added
- Add a Vertex Tunnel app.
- Add a Vertex Metrics app.
- Expose a
/metrics
endpoint for Prometheus with events gathered by Vertex. - Find the server local IP automatically.
- The server can now add tags to the instances.
- Revamped navigation.
Changed
- Change the kernel CLI flags.
Fixed
- Fix an issue where the logs would recreate a deleted instance at midnight.
- Fix an issue where Vertex displays 'building' indefinitely when an error occurs during the build of an instance.
v0.10.1
Changelog
Added
- Support for startup command in the services.
v0.10.0
Changelog
Added
- Allow to change the proxy and kernel port with command args.
- Add a migration tool.
- Add ability to change the version of an instance.
- Logs can now display download progress properly.
- Revamped loading progress bars.
- Revamped UI controls size.
- Revamped instance status.
- Ignore instances start/stop when they are in a transition state.
- Details about errors are now displayed only in the logs for security purposes. The error displayed to the user has no details about the infrastructure.
Removed
- Remove the support for scripts, as the API is not good enough for public releases.
v0.9.3
Changelog
0.9.3
Added
- Beta channel for the releases.
0.9.2
Fixed
- Fix an issue building Vertex on Windows.
0.9.1
Fixed
- Fix an issue that prevents the kernel to open the port 80.
- Fix an issue that makes the kernel close before vertex, blocking instances shutdown.
0.9.0
Added
- New Vertex-Kernel, which enhances the security and stability of Vertex.
Changed
- Refined themes.
Fixed
- Fix an issue that could occur when creating new url routes in the reverse proxy.