However, deployments were always at the root of our mission.
With the new feature of Projects landing today, we continue to pave the way for deployments in the area of more advanced use cases by allowing you to group and manage them based on the project they belong to.
How Your Workflow Changes
Not at all.
At the core of Projects is the
nameproperty of your deployments. This field is generated based on the following rules:
- It is read from the now.json file if
- When using Now CLI, the
--nameflag can overwrite the above.
- If our GitHub Integration is used to deploy, we pick the repository name if
nameis not defined in your now.json file.
- Outside of our GitHub Integration, the directory name determines it. If what you deployed is a file, it will be called "file" for a single one and "files" for multiple.
Thanks to these rules, you do not need to change your workflow of creating new deployments in any way. Projects are just another layer on top for making your deployments easier to manage after they have been created.
What Is New
The most important feature of this release is a completely revamped dashboard:
At a single glance, you can see both a list of recently updated projects in your team and a list of recent events. For each project, you can:
- Access any aliases assigned to the most recent deployment
- See who is working on it
- What the status of the latest deployment is
- How many deployments have happened under that project
The features mentioned above will compliment your daily interaction with the events stream, especially as a project owner or manager.
However, that is just the tip of the iceberg. If you need more information, each project will provide sub pages with more details by clicking on it.
For example, you can see the list of all deployments under a project:
Even a list of all aliases assigned to the project exists:
Apart from these organizational changes, we have also made our dashboard significantly faster for those slow internet connections.
Compared to the previous version, the new dashboard is much snappier when navigating between projects and loading lists of deployments.
In order for this to happen, we applied a mix of server side rendering, client side data fetching, and clever use of caching, all powered by a new data fetching layer that works with any Promise based backend.
For this concept, however, a separate introduction is needed. Stay tuned.
Changes to Now CLI
With the latest version of Now CLI, you can manage your projects right from the terminal using the new
If you want to see a list of all your projects under the current team or user, for example, run this command:
The result would be an output like this one:
In the case that you do not need one of those projects anymore, you can delete a project with the following:
After running the above command, the project "front" will be gone (including all of the deployments it contained).
You can also add a new project straight from Now CLI like this:
This would create a new project called "my-app", even though no deployments exist with that project name attached to them.
What the Future Holds
On top of Projects, many exciting features will be implemented. Having a better overview over your deployments is just the start.
In the future, improvements to aliases, secrets, team membership, and even completely new features will follow – all expanding on what Projects has achieved already.