How to use the command 'now' (with examples)

The ’now’ command was a versatile tool used for deploying projects to the cloud using the Zeit platform, which is now known as Vercel. This command-line utility allowed users to effortlessly deploy their web applications and manage their deployments with ease. Although ’now’ has been deprecated and replaced by the new ‘vercel’ command, it’s useful to understand its previous capabilities as it laid the foundation for modern cloud deployment practices.

Use case 1: Deploy the current directory

Code:

now

Motivation:

Deploying a project to the cloud has become a fundamental aspect of modern web development. The ’now’ command allowed developers to instantly deploy the contents of their current working directory, facilitating rapid iteration and testing. This tool was ideal for developers looking to share their work with collaborators or deploy a project quickly without needing extensive configuration.

Explanation:

• This command ’now’ assumes the current directory contains the code that you wish to deploy. By running the command, it packages the directory’s content and sends it to the Zeit platform for hosting.
• There are no additional arguments provided in this example, making it straightforward for developers who want a hassle-free deployment experience without worrying about complex setup processes.

Example output:

> Deploying ~/Projects/my-app
> Using Node.js v12.x
> Ready! https://my-app-123.now.sh

Use case 2: Display a list of deployments

Code:

now list

Motivation:

Managing multiple deployments is a common task for developers, especially in agile environments where applications are continuously updated. The ’now list’ command empowered developers by providing a straightforward way to view all active deployments. This overview is crucial for identifying live environments or deciding which deployments might need updates or removals.

Explanation:

• The command ’now list’ doesn’t require any additional arguments, which simplifies the process of querying active deployments.
• By running this command, developers can retrieve a list of their deployments along with essential information such as deployment URLs and IDs.

Example output:

> Fetched deployments
my-app-123.now.sh      Deployment ID: abcdefg
my-second-app.now.sh   Deployment ID: hijklmn

Use case 3: Display information related to a deployment

Code:

now inspect deployment_url

Motivation:

Understanding the details of a specific deployment can be critical for troubleshooting, optimization, or ensuring compliance with deployment standards. The ’now inspect’ command provided developers with a detailed look at a specific deployment, offering deep insights into its configuration, environment variables, and versioning details.

Explanation:

• The argument ‘deployment_url’ should be replaced with the actual URL or deployment identifier of the deployment you wish to inspect.
• This command fetches comprehensive data about a specific deployment, allowing developers to examine environmental settings and deployment history.

Example output:

> Inspecting deployment abcdefg
URL: https://my-app-123.now.sh
Created at: 2023-05-01
Environment: Production
Node.js version: 12.x

Use case 4: Remove a deployment

Code:

now remove deployment_id

Motivation:

Keeping a deployment space clean and manageable is vital. Whether it’s due to outdated deployments, test environments, or failed updates, sometimes it’s necessary to remove deployments. The ’now remove’ command allowed developers to clean up their deployment space by removing unnecessary deployments, optimizing resource usage and avoiding clutter.

Explanation:

• The ‘deployment_id’ is a unique identifier for each deployment, allowing precise targeting of deployments that need to be removed.
• This operation is crucial for maintaining an organized deployment strategy and ensuring only relevant and current code remains active.

Example output:

> Removing deployment abcdefg
> Deployment successfully removed

Use case 5: Log in into an account or create a new one

Code:

now login

Motivation:

Secure authentication and access management are foundational for any cloud platform. The ’now login’ command streamlined the process of logging into an existing Zeit account or creating a new one effortlessly, thus allowing developers to start deploying their applications without delay.

Explanation:

• This command initiates an interactive login process where developers are prompted to provide their credentials or create a new account.
• By signing in, developers gain access to deploy and manage their projects effectively on the Zeit platform.

Example output:

> Please enter your email to login or create a new account: 
[Interactive authentication prompts follow]

Use case 6: Initialize an example project

Code:

now init

Motivation:

For developers looking to start a new project, having a boilerplate ready can be incredibly helpful. The ’now init’ command facilitated this by creating a new directory with pre-configured files necessary for a typical serverless application, thus accelerating the development process.

Explanation:

• This command generates a new directory structure with languages and frameworks commonly used in serverless applications.
• It’s particularly beneficial for developers unfamiliar with serverless configurations, as it provides a pre-set environment to begin development smoothly.

Example output:

> Initializing example project
> Created directory my-new-project
> Ready to code in my-new-project

Conclusion:

Although the ’now’ command is deprecated, understanding its utility and application across different scenarios is beneficial for grasping the fundamentals of serverless deployment. These use cases exemplify the command’s ability to streamline deployment processes, reinforce platform security, and provide swift access to an array of deployment management tasks. The transition to ‘vercel’ continues to build upon these core functionalities, enhancing the deployment experience even further.