Harmony
React
NodeJS
Angular
VueBit empowers teams and individual developers to independently build, maintain, and release features or business domains within isolated workspaces. To start creating a workspace, initialize a Bit workspace in an empty directory:
Use cloud workspaces
For a streamlined development experience, use Cloud Workspaces for a ready-to-go, web-based and integrated development environment for maintaining composable features and business domains.
Create the workspace:
bit init
Head to the workspace and import or create the feature components and the aspect:
bit import "pied.people/**"
Install components as needed and use them as packages during development:
bit install @pied/testing.mock-provider
Learn more about using external dependencies in workspaces.
To see update and see effect of changes, import the shell application component:
bit import pied.pied-piper/pied-piper
Start the development server to see your changes reflected in the application:
bit run pied-piper
Navigate to https://localhost:3000 to see the app with your applied changes.
By default, Bit uses Ripple CI to affect of your changes on other aspects, at scale without increasing your workspace size.
Simplify onboarding for platform development by creating a starter for your platform. To get started, create your Harmony dev environment, and add a new Workspace Template. Once added, you can use the following command to create a new basic workspace:
bit new my-platform --env my-org.platform/my-platform
Bit offers a two-stage deployment process: staging and production.
It's recommended to deploy your changes to a staging environment for testing before pushing them to production. Use lanes to manage staging deployments.
Create a lane:
bit lane create introducing-billing
Create a new version:
bit snap --message 'building the billing aspect'
Initiate the deployment job:
bit export
Learn more about creating lanes in the reference documentation.
For production deployments, it's generally recommended to use a change request process to ensure a safe and controlled rollout. This process typically involves testing the impact of changes on external components and conducting product reviews.
Here's how to initiate a production deployment using a tag
Create the release tag:
bit tag --message 'releasing my feature' --major
Initiate the release CI job:
bit export
While the above command triggers a deployment pipeline, Bit also recommends following a more comprehensive release process using change requests. Refer to the Bit documentation for a detailed guide on safe and atomic deployments.
For further information on deployment configurations, refer to the Bit documentation on setting up your platform deployment.
Explore the following resources to delve deeper into Bit concepts:
