> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/classic/user-manual/publishing/publishing-to-chillidog.md).

# Publishing to Chillidog

How to Publish with RapidWeaver to Chillidog Hosting

This guide will walk you through publishing your website with RapidWeaver via FTP or SFTP to your [Chillidog Hosting](https://billing.chillidoghosting.com/aff.php?aff=113) account.

{% hint style="info" %}
Every aspect of [Chillidog’s hosting](https://billing.chillidoghosting.com/aff.php?aff=113) is built to ensure absolute compatibility with RapidWeaver, and all the friendly support staff at [Chillidog](https://billing.chillidoghosting.com/aff.php?aff=113) are all familiar with RapidWeaver.
{% endhint %}

[Chillidog Hosting](https://billing.chillidoghosting.com/aff.php?aff=113) offers two different ways you can upload your site to your server. Here are the settings for FTP.

### FTP Publishing

Publishing Method: **FTP**

Server: **ftp.yourwebsite.url**

Connections: **6 (Lightning Fast!)**

Username: **your cpanel username** (provided in your New Account email from Chillidog)

{% hint style="info" %}
Your **cpanel username** will never be an email address.
{% endhint %}

Password: **your cpanel password** (provided in your New Account email from Chillidog)

Path: **public\_html/** if you only have one site on the server. If you have created [**Addon Domains**](https://chillidoghosting.com/help/how-do-i-add-an-additional-site-addon-domain-to-my-hosting) via your cpanel at Chillidog, then you can use the Browse button and look for the appropriate folder.

Mode: **Extended Passive**

### SFTP Publishing

If you wish, you can also **Publish** to your Chillidog server via **SFTP.** Here are the settings:

Publishing Method: **SFTP**

Server: **ftp.yourwebsite.url:23261**

Connections: **6 (Lightning Fast!)**

Username: **your cpanel username** (provided in your New Account email from Chillidog)

{% hint style="info" %}
Your **cpanel username** will never be an email address.
{% endhint %}

Password: **your cpanel password** (provided in your New Account email from Chillidog)

Path: **public\_html/** if you only have one site on the server. If you have created [**Addon Domains**](https://chillidoghosting.com/help/how-do-i-add-an-additional-site-addon-domain-to-my-hosting) via your cpanel at Chillidog, then you can use the Browse button and look for the appropriate folder.

### Custom 404 Page

To have a custom 404 page, you'll need to create a page at the root of your project and name it "404.shtml" - notice the "s" in ".shtml".

This is very important as if you name the page "404.html" the page will be ignored by the server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/classic/user-manual/publishing/publishing-to-chillidog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.