In this section we will walk you through what you will need to start using Zephyr and enjoy its benefits by deploying an application through Zephyr and modifying configuration. We will start with installing and creating your account, then create a standalone React app. At the end of this guide, you will have your first React app deployed to Zephyr's managed cloud with Rspack as bundler and use our version control feature to preview all versions that's deployed.
If you are curious to read more about us, you can dive into our architecture, recipes (for more frameworks and bundlers) and features. Below guide is written based on Google Chrome thus other browser's behavior might differ (see a list of supported browsers)
Because of Cloudflare Caching, the time to propagate deployed assets (for deployment to be visible) might take from within one minute to an hour and the timing is non-deterministic.
This is a known issue we are still investigating and seeking for improvements.
Issue might be happening to:
If you are following the get started guide without custom deployment provider you will be using our managed cloud.
Read more about how to configure Cloudflare and how to configure Netlify as your default cloud provider.
If you don't have nvm
to manage your node version yet, head to the official nvm guide to install it.
Once the prerequisites are fulfilled, we can start scaffolding our application in the terminal:
If you are using our managed cloud (Cloudflare) or custom deployment integration through Cloudflare, when you are adding assets, naming your application in package.json
or module federation configuration, make sure the name doesn't include capital letter to avoid query problem with Cloudflare.
The creation process will ask you for project folder name and project template, we will be choosing react
in this example:
Press
Follow the console output to open the app in browser running on localhost.
Open the project folder we created with code editor of your choice. Within current working directory, install Zephyr's plugin by running:
After install the plugin, open the file rspack.config.ts
in project root and replace the original configuration as below:
The next step is configure the git configuration for your project.
Behind the scene, we map your git configuration to Zephyr (remote origin url, organization or username, repository name and branch) to deploy your application. Without this step your deployment will fail.
Click here to create a new repository named rspack-project on Github. Choosing either Private or Public won't affect our deployment. And then click on Create repository.
On the next page where your repository has been created on Github, copy paste the command lines under ...or create a new repository on the command line and execute them in terminal within the project.
After we finished configuring the project, within your terminal run:
If you haven't register an account with us, or you haven't sign in for a while, your default browser will pop up and prompt you to sign up to our dashboard. If you already have an account or signed in recently, the browser will notify that you already signed in.
Within the terminal you should see your deployed URL. Press
Note that this URL will live as long you don't delete your account and you can share it with anyone to preview it. We will discuss how and where you can find your deployed URL within our platform next.
You can check the application you just deployed in our chrome extension and you can preview every version of the application you deploy.
Head to Chrome Web Store to install our chrome extension - Zephyr Mission Control. Click on Add to Chrome and confirm with Add extension. After you finish remember to pin the extension by clicking on on extension management tab to provide you a quicker access to Zephyr's side panel.
Once you click on the side panel will pop up and prompt you to log in. You might need to right click on the extension and choose Open Side Panel if you are using it for the first time.
While we are loggin you in, we are storing your authorization information locally under ~/.zephyr
in your root directly. Whenever you want to clean up your local profile information (they are JWT claims for each of the project you deployed through Zephyr), you can enter your root directory in terminal and run:
Open your side panel by clicking on . Note that this URL is alive as long you don't delete your account and you can share it with anyone to preview it.
Every application you have deployed on Zephyr (under the same account) will be displayed under Name, categorized by repository name and their package name. Click on the dropdown menu under Version you will see the versions of your app. Items under Tags denotate the tag rules of this application, both auto generated by us or set up by you.
Now you have deployed the first version, let's add modify the app and deploy a new version. Open the file src/App.jsx
to change the content of your website:
Next in your terminal run:
The console output will return the latest deployed URL. On Chrome ChromeExtension, the latest deployed version will be under Version dropdown in as the first option. You should see the app's heading is changed to Rspack + React + Zephyr
Now the latest version of your app is deployed. You can check the source code till this stage here:
The names of your versions are generated by Zephyr. The first part of the name is the branch name, serialised version of your email, followed by the version number.
Once you have deployed a new version of your application, the latest deployed version will show up in browser as soon as you select it under Name
.
Our chrome extension is only supported on Chromium based browsers. See a list of supported browser.
If you want to see all your projects and their versions, sign in on dashboard and you will see all your projects and their dependencies.
More detailed explaination on how to use our dashboard is coming soon.