Hosting with Forge

Deploy your Hammer sites to production in seconds with Forge. One-click deployment with lightning-fast hosting, global CDN, and automatic HTTPS.

Introduction

Forge provides production-ready hosting for your Hammer sites. Once connected, you can deploy your sites with a single click directly from Hammer. Forge handles everything, from global CDN distribution to automatic HTTPS certificates.

Using Forge for hosting offers:

  • One-click deployment directly from Hammer
  • Lightning-fast hosting with global CDN
  • Automatic HTTPS for all your sites
  • Environment management for staging and production
  • Organizational workspaces for team collaboration

Connecting Your Forge Account

To get started with Forge hosting, you'll need to connect your Forge account to Hammer through the Settings.

Step 1: Open Hammer Settings

Navigate to Hammer Settings and select the Forge tab. This is where you'll configure your Forge integration.

Step 2: Create a Forge Account

If you don't already have a Forge account, you'll need to create one:

  1. Visit getforge.com to register
  2. Create your account using your email address
  3. Verify your email to activate your account
Tip: You can click the "Visit Forge" button in Hammer Settings to open Forge in your browser.

Getting Your API Token

To connect Hammer to Forge, you'll need an API token from your Forge account. This token authenticates Hammer and allows it to deploy sites on your behalf.

Step 1: Access Profile Settings

In your Forge account, navigate to your profile settings page:

  1. Log in to your Forge account at getforge.com
  2. Click on your profile or account settings
  3. Navigate to the API tokens section

Step 2: Copy Your API Token

On your profile settings page:

  1. Locate your API token (or generate a new one if needed)
  2. Click to copy the token to your clipboard
  3. Return to Hammer Settings
Tip: You can use the "Profile Settings" button in Hammer Settings to quickly navigate to your Forge profile page.

Step 3: Paste the Token in Hammer

In Hammer Settings, paste your API token into the "Forge API Token" field. Hammer will verify the token and save your connection.

Your API token is securely stored and used to authenticate deployments to Forge. Never share your API token publicly or commit it to version control.

Selecting Your Forge Workspace

Forge supports both personal accounts and organizational workspaces. When deploying a site, you can choose which workspace the site belongs to.

Personal Account

By default, sites are deployed to your personal Forge account. This is perfect for personal projects or when you're working independently.

Organizational Workspaces

If you're part of an organization on Forge, you can select that workspace when deploying. This allows team members to collaborate on sites and share deployment responsibilities.

  • Select the organization from the workspace dropdown in deployment settings
  • Sites deployed to an organization are visible to all team members with appropriate permissions
  • You can switch between personal and organizational workspaces as needed
Note: If no sites are found in your selected workspace, make sure you have the appropriate permissions or try switching to a different workspace.

Linking Your Forge Site to Hammer

Once your Forge account is connected, you can link a Forge site to your Hammer project. This enables one-click deployment from within Hammer.

Step 1: Create a Site in Forge

Before linking, you'll need a site in your Forge account:

  1. Log in to your Forge account
  2. Create a new site or select an existing one
  3. Note the site name or ID

Step 2: Link the Site in Hammer

In Hammer's deployment settings:

  1. Select your Forge workspace (personal or organization)
  2. Choose the Forge site you want to link from the list
  3. Save the deployment configuration

Once linked, you can deploy your Hammer site to Forge with a single click. Hammer will automatically upload your build directory to the linked Forge site.

One-Click Deployment

After linking your site:

  • Build your Hammer site as usual
  • Click the Deploy to Forge button in Hammer
  • Your site will be uploaded and live in seconds

Hammer handles the entire deployment process automatically, including file uploads, cache clearing, and CDN propagation.

Exporting Your Build

While Forge provides seamless integration with Hammer, you can also export your build as a ZIP file to deploy to any hosting service you prefer.

Exporting as ZIP

To export your Hammer build:

  1. Build your Hammer site
  2. Navigate to the Export option in Hammer
  3. Select Export as ZIP
  4. Choose where to save the ZIP file

The exported ZIP file contains your complete built site, ready for deployment to any static hosting service.

Deploying Elsewhere

Your exported build can be deployed to:

  • Any static hosting service that supports ZIP uploads
  • Traditional web servers via FTP or SFTP
  • Cloud storage services configured for static hosting
  • Other hosting platforms that accept static site deployments
Tip: The exported ZIP contains only the files from your Build directory, ensuring a clean, production-ready package without source files or development tools.

Next Steps

Now that you're set up with Forge hosting, you might want to learn about: