<p>The best way to go is build it locally then upload it.</p>

<p>After the initial upload, if you use a smart FTP client like <a href="http://panic.com/transmit">Transmit</a> you can sync both version to update your local version before making local changes then re-sync to upload them.</p>

<p>Editing online can be done but for me it is crucial that you always have a local backup just in case something happens, so even if I do edit online I then sync my changes.</p>

<p>PS. To keep both version running without changes you’ll have to take advantage of <a href="https://craftcms.com/docs/multi-environment-configs">Craft multi environment configs</a>.</p>

CC BY-SA 3.0
2016-07-22T12:55:33.527Z
Sublime Text with Sublime SFTP works well for me working on the server for minor stuff. You can set it to upload when a file is saved, meaning it's saved locally first, then uploaded so you've always got the latest files local ready for git.
Clive Portman
CC BY-SA 3.0
2016-06-23T11:07:01.727Z
2016-06-23T11:07:01.727Z
fdelaneau
<p>I absolutely agree with "build locally and then upload it".</p>

<p><a href="https://deploybot.com/">Deploybot</a> can deploy with ftp, and makes it quite painless to keep local and remote and git repo all in sync.</p>

<p>I make debugging sorts of changes directly on the server (tweak the config, tweak .htaccess, that sort of thing), but any change I want to keep I make sure to get into git.</p>

CC BY-SA 3.0
2016-06-24T18:48:31.290Z
We also use Deploybot. And we use bitbucket with 2 branches.
Martijn La Feber
CC BY-SA 3.0
2016-06-23T16:32:29.600Z
2016-06-23T16:32:29.600Z
Marion Newlevant
<p>I'm building a simple low traffic website in Craft for a customer whose web server only allows access over ftp. How would you have done the work in practical terms? Building the site locally and then copy everything manually over FTP when done?</p>

<p>Is it for this kind of websites completely wrong to make minor adjustments directly on the server? </p>

<deployment><workflow>
Workflow when you only have FTP access?
# Workflow when you only have FTP access?

(Asked by: username_0 on 2016-06-23)

I'm building a simple low traffic website in Craft for a customer whose web server only allows access over ftp. How would you have done the work in practical terms? Building the site locally and then copy everything manually over FTP when done?

Is it for this kind of websites completely wrong to make minor adjustments directly on the server?

**Tags:** deployment, workflow


---

## 2 answers

### Answer by username_3 on 2016-06-23. Score: 7 | Accepted answer

I absolutely agree with "build locally and then upload it".

[Deploybot](https://deploybot.com/) can deploy with ftp, and makes it quite painless to keep local and remote and git repo all in sync.

I make debugging sorts of changes directly on the server (tweak the config, tweak .htaccess, that sort of thing), but any change I want to keep I make sure to get into git.

> **Comments:**
> **username_4**: We also use Deploybot. And we use bitbucket with 2 branches.  

---

### Answer by username_1 on 2016-06-23. Score: 5

The best way to go is build it locally then upload it.

After the initial upload, if you use a smart FTP client like [Transmit](http://panic.com/transmit) you can sync both version to update your local version before making local changes then re-sync to upload them.

Editing online can be done but for me it is crucial that you always have a local backup just in case something happens, so even if I do edit online I then sync my changes.

PS. To keep both version running without changes you’ll have to take advantage of [Craft multi environment configs](https://craftcms.com/docs/multi-environment-configs).

> **Comments:**
> **username_2**: Sublime Text with Sublime SFTP works well for me working on the server for minor stuff. You can set it to upload when a file is saved, meaning it's saved locally first, then uploaded so you've always got the latest files local ready for git.  

---

