Deploy the Components

The function and client files are now ready to be deployed to the Catalyst remote console and made live. You can learn about deploying your Catalyst components in detail from the Deploy Resources help page. 

Let's deploy the files from the CLI. Navigate to the project directory (CATALYST_PROJECT_HOME) in the CLI and execute the following command:

$ catalyst deploy

This will deploy both the functions and the client resources in your project directory. 

The functions directory is deployed first. The CLI deploys each function to the URL that is displayed in the terminal. You can access the function's endpoint from this URL.

Once a resource is properly deployed, the CLI will display a successful deployment message.

The client directory is deployed next. This will also generate a URL endpoint for the hosted web client.

You can access the web app by opening the URL in a browser. 

When a user signs up in this page, they will receive a verification email which contains a link for them to set up a password to access the application. This email will be sent automatically from Catalyst.

You can customize this verification email by navigating to Email Templates in the Authentication component in the Catalyst console. However, the default email template that Catalyst provides satisfies our needs. We will therefore skip this step for this tutorial. You can learn more about this in detail from the Email Templates help page.

After the user has set up a password through the verification email and completed this sign up process, they will receive the automated onboarding email that we configured earlier. To make this happen, we must associate the event function with the user signup using an event listener.