Deploying your code or website to <a href="https://www.greengeeks.com/" target="_blank">GreenGeeks</a> is straightforward with DeployHQ.

**Important:** SSH is not enabled by default on GreenGeeks shared hosting. You must contact GreenGeeks support to request shell access activation before you can connect from DeployHQ.

Firstly, you'll need to set up your DeployHQ project, then connect to your GreenGeeks server.

## Setting up your project

Head to the **Projects** screen in DeployHQ, then click the **New Project** button to get started.

You'll be prompted to enter a name for your project, then select where your repository is hosted.

{screenshot: 9}

Next, click **Create project** and you'll be taken to a screen where you can log in with your repository hosting account to authorise access and then choose your repository.

* [Adding a Bitbucket repository](Article: #17)
* [Adding a Codebase repository](Article: #19)
* [Adding a GitHub repository](Article: #21)
* [Adding a GitLab repository](Article: #23)
* [Adding a repository manually](Article: #25)

## Setting up GreenGeeks

Once you've configured your repository, you'll need to connect to your GreenGeeks server.

### Enable SSH access

GreenGeeks disables SSH on shared hosting by default. To enable it:

1. Log in to your GreenGeeks **Account Manager** at `my.greengeeks.com`
2. Open a **support ticket** requesting shell access activation for your account
3. GreenGeeks support will enable SSH — this usually takes a few hours

Once SSH is enabled, set up key authentication:

1. Open **cPanel** for your hosting account
2. Go to **Security > SSH Access**
3. Click **Manage SSH Keys**
4. Click **Import Key** and paste the DeployHQ public key shown on the server configuration page in DeployHQ
5. Click **Manage** next to the imported key and **Authorize** it

Head to **Servers & Groups** in DeployHQ, and click the **New Server** button. Choose **SSH/SFTP** as the protocol.

Enter the following details:

- **Hostname**: Your server's hostname (the hostname portion of your cPanel URL, before `:2083`)
- **Username**: Your cPanel username
- **Port**: `22`

Then set the **Deployment path**:

- **Primary domain**: `/home/yourusername/public_html/`
- **Addon domain**: `/home/yourusername/public_html/addondomain.com/`

For WordPress theme deployments, append the path to the theme directory.

Under **Deployment options**, you can enable automatic deployments and set a **Deployment subdirectory** if needed.

Click **Create Server** to save, then proceed to your first deployment.

## Run your first deployment

By default, DeployHQ will upload your entire repository on the first deployment, since there's no previously deployed commit to compare against.

If your files are already on the server and up to date with the latest commit, you can skip that initial upload:

* [Don't deploy your whole repository on the first deployment](Article: #129)

Otherwise, follow this guide to start your first deployment — after the first run, only changed files will be uploaded:

* [Running your first deployment](Article: #43)

That's it! You've now set up automated deployments to your GreenGeeks server.

## Further reading

* Compile assets with the [Build pipeline](Article: #301)
* Run commands on your server with [SSH commands](Article: #57)
* Prevent certain files from uploading using [Excluded files](https://www.deployhq.com/support/excluded-files)
* Keep sensitive config out of your repository using [Config files](Article: #47)
* Notify your team and integrate with other services via [Integrations](Article: #327)

----------

_Need help with your deployment? Check out our [documentation](https://www.deployhq.com/support) or [contact our support team](https://www.deployhq.com/contact) for assistance._