Version 1.0.0 and announcing our Team plan
With over a year of hard work and 3500+ commits, we finally reach the milestone to announce our 1.0.0 version and our Team Plan. The Team Plan includes:
The price starts at $29 per instance per month. Please visit our pricing page for more details. You can visit https://hub.bytebase.com/pricing to purchase a subscription license and manage your team plan subscription in Settings page.
If a project is linked with GitLab repository, one can sync that repositoryβs membership to the projectβs membership from the linked GitLab repository
We improve the layout for showing the current database schema change progress across all tenants.
SQL Editor
Retire issue rollback feature Previously, Bytebase allows user to specify a rollback SQL for the rollback. And if user chooses to rollback the SQL, Bytebase will use the rollback SQL to create that rollback SQL. This only sounds good in theory, because in reality, itβs already a big hurdle to write a good schema change SQL, it would be even challenging to ask the developer to provide a correct rollback SQL at the same time.
Thus, we decide to retire this feature. Meanwhile we already have ideas for a much better solution without requiring developer to write the rollback SQL manually. Please stay tuned.
Fresh install: /get-started/self-host
Upgrade: /get-started/upgrade
Warning: Bytebase does not support in-place downgrade. Make sure to back up your metadata before upgrading.
Version 1.0.0 and announcing our Team plan
With over a year of hard work and 3500+ commits, we finally reach the milestone to announce our 1.0.0 version and our Team Plan. The Team Plan includes:
The price starts at $29 per instance per month. Please visit our pricing page for more details. You can visit https://hub.bytebase.com/pricing to purchase a subscription license and manage your team plan subscription in Settings page.
If a project is linked with GitLab repository, one can sync that repositoryβs membership to the projectβs membership from the linked GitLab repository
We improve the layout for showing the current database schema change progress across all tenants.
SQL Editor
Retire issue rollback feature Previously, Bytebase allows user to specify a rollback SQL for the rollback. And if user chooses to rollback the SQL, Bytebase will use the rollback SQL to create that rollback SQL. This only sounds good in theory, because in reality, itβs already a big hurdle to write a good schema change SQL, it would be even challenging to ask the developer to provide a correct rollback SQL at the same time.
Thus, we decide to retire this feature. Meanwhile we already have ideas for a much better solution without requiring developer to write the rollback SQL manually. Please stay tuned.
Fresh install: /get-started/self-host
Upgrade: /get-started/upgrade
Warning: Bytebase does not support in-place downgrade. Make sure to back up your metadata before upgrading.