You've built a blazing-fast web application, and now you want an equally fast way to deploy it. What if you could trigger deployments right from your team's Slack channel? This guide shows you how to set up automated deployments for your web application site using [DeployHQ](https://deployhq.com) and control everything through Slack. Perfect for teams who want to streamline their deployment workflow! **What You'll Need** - A web application in a Git, SVN, or Mercurial repository - A [Slack](https://slack.com/) workspace - A server or hosting platform, like [DigitalOcean](https://www.digitalocean.com/) - A [DeployHQ](https://deployhq.com) account (starts at $9/month, with a 10-day free trial) ## Quick Overview We'll cover two main parts: 1. Setting up automated deployments for your web application with [DeployHQ](https://www.deployhq.com) 2. Connecting [DeployHQ](https://www.deployhq.com) to Slack for deployments with simple Slack commands Let's get your deployments sorted in under 15 minutes! ## Setting up DeployHQ As an example we will deploy a simple [Astro](https://astro.build/) site to a server that we have SSH access to. Although this example is for Astro, the same steps apply to most Node.js based web applications. If you're not using Astro don't worry, we have over [25 guides for different frameworks available!](https://www.deployhq.com/guides) If you want to follow along, you can create the same Astro site that we will deploy by running the following commands: ``` npx create-astro@latest -y ``` The output will look like this: ![Deploy from Slack with DeployHQ](https://gist.github.com/user-attachments/assets/03461d9f-d2c6-4a87-9ec5-464830f3e608) Then simply push it to a Github repository of your choice. If you need help with that, we have a few awesome guides to help you get started [here](https://www.deployhq.com/git): - [Creating a repository](https://www.deployhq.com/git/creating-a-repository) - [Committing file changes](https://www.deployhq.com/git/committing-file-changes) - [Publishing local changes](https://www.deployhq.com/git/publishing-local-changes) Once you have a repository and your server credentials, you can proceed with setting up [DeployHQ](https://www.deployhq.com). ## Connecting Your Repository and Server ### Step 1: Create a New Project 1. Log in to your [DeployHQ](https://www.deployhq.com) account 2. Click New Project in the top right 3. Enter a name for your project (e.g., Astro Site) 4. Select one of the options for your repository provider and follow the instructions to connect your repository. ![Connecting repository to DeployHQ](https://gist.github.com/user-attachments/assets/71c25245-1116-41c7-a617-8c36b5d98f34) ### Step 2: Configure Your Server 1. Go to Servers & Groups in the left sidebar 2. Click New Server 3. Pick SSH and fill in the server details: - **Name** : Give your server a descriptive name (e.g., Production) - **Hostname** : Your server's IP address or domain - **Port** : Usually 22 - **Username** : Your SSH username - **Authentication** : Choose between password or SSH key - **Deployment Path** : The directory where your site will be deployed (e.g., `/var/www/html`) 4. Click Create Server 5. [DeployHQ](https://www.deployhq.com) will test the connection - if successful, you'll see that the server is getting created ![Adding a server in DeployHQ](https://gist.github.com/user-attachments/assets/47d130a3-12d2-49d8-880c-c6f9894ef7d1) ### Step 3: Configure Build Pipeline We are basically done here, just one last step is missing. Astro sites need to be built before they are deployed. To do that, we first need to run `npm install` to install the dependencies and then `npm run build` to build the site. Of course, [DeployHQ](https://www.deployhq.com) makes this super easy for us with Build Pipelines. Go to your project and click on Build Pipeline in the left sidebar. 1. Click New Command 2. Fill in the details: - **Description** : Install and build - **Command** : `npm install && npm run build && rm -rf ./node_modules` 3. Click Create Build Command This will be executed before the deployment on a secure build server. Since Astro is static, we don't need to keep the node\_modules folder. This will make our deployment a bit smaller and a lot faster! ### Step 4: Test Deployment **Houston, we are ready to deploy!** Before we automate the deployment with Slack, let's test it manually once. Again, go to your project and click on Deployments in the left sidebar. 1. Click New Deployment 2. Select the branch you want to deploy 3. Click Deploy You can follow the progress of the deployment in the [DeployHQ](https://www.deployhq.com) dashboard. Once it's done, you can check your deployment folder to see if the deployment was successful. ![Testing a deployment in DeployHQ](https://gist.github.com/user-attachments/assets/86e412ef-f835-4971-afd5-a374e3380ce7) ## Setting Up the Slack Integration Getting started with DeployHQ's Slack integration is surprisingly simple: 1- **Create a [DeployHQ](https://www.deployhq.com) Integration** - Go to your project's Integrations section - Click New Integration - Select Slack from the service picker 2- **Authorize the [DeployHQ](https://www.deployhq.com) App** - You'll be redirected to Slack - Choose which channel to send notifications to - Authorize the app for your workspace and user 3- **Configure Deployment Triggers** - Choose when to trigger notifications - Select specific servers or apply to all - Customize your notification preferences Notifications are not the only thing the [DeployHQ](https://www.deployhq.com) Slack integration can do! [DeployHQ](https://www.deployhq.com) also allows you to deploy directly from Slack. So let's do that now! ![Trying it out in Slack](https://gist.github.com/user-attachments/assets/71f929b7-f768-4f68-baa9-7918d0d92bbf) The command is `/deployhq deploy `. The perma-link can be found in the URL of your project or in the settings of your project. If you need more help, we have a dedicated [Slack guide](https://www.deployhq.com/support/integrations/slack) for you, plus a deeper walkthrough on [receiving notifications and triggering deployments from Slack](https://www.deployhq.com/blog/receive-notifications-and-trigger-deployments-with-slack). ## Why Choose DeployHQ's Slack Integration? If you (or your boss) still need some convincing, here are some more reasons why DeployHQ's Slack integration is a game-changer: - [Deploy](https://www.deployhq.com) without leaving Slack, less context switching - Real-time deployment visibility for the whole team - Secure permissions management through Slack - Quick setup (usually under 5 minutes) - Works with any hosting provider - Very easy, even for non-tech-savvy team members ## Best Practices Of course, there are some best practices to keep in mind: 1- **Channel Organization** - Create dedicated deployment channels - Use channel naming conventions (e.g., #deployments-prod, #deployments-staging) 2- **Permission Management** - Only give deployment access to necessary team members 3- **Notification Setup** - Configure meaningful notification triggers - Avoid notification fatigue with selective alerts ## Getting Started Ready to supercharge your deployments with [DeployHQ](https://www.deployhq.com) and Slack? Here's how: 1. [Sign up for DeployHQ](https://www.deployhq.com/) (10-day free trial available) 2. Connect your repository (GitHub, GitLab, or Bitbucket) 3. Set up your deployment servers 4. Add the Slack integration 5. Start deploying with simple slash commands! ## FAQ ### Is the Slack integration included in all DeployHQ plans? Yes! The [Slack integration](https://www.deployhq.com/features/integrations/slack) is available on all [DeployHQ](https://www.deployhq.com) plans, starting from $9/month. ### Can I control who can deploy through Slack? Absolutely! DeployHQ's permission system carries over to Slack commands, ensuring only authorized team members can trigger deployments. ### What happens if a deployment fails? You'll receive immediate notifications in Slack about any deployment issues, complete with error details and troubleshooting links. ### Can I use this with any hosting provider? Yes! [DeployHQ](https://www.deployhq.com) works with any hosting provider that supports SSH access, making it incredibly versatile. ### Can I change the message that is sent to Slack? Yes! You can customize the message that is sent to Slack by clicking on Edit next to the integration and then on Message Format. ## Conclusion Whether you're a small startup or a large enterprise, bringing deployments into Slack can significantly streamline your workflow. With DeployHQ's robust platform backing every deployment, you get the perfect blend of simplicity and power. Ready to make your deployments faster and easier? [Start your free trial with](https://www.deployhq.com/)[DeployHQ](https://www.deployhq.com) today!