<p>Dennis,</p>

<p>I use deploybot with Craft and easily deploy. So on your server settings you'll have this:</p>

<p>name: your site name</p>

<p>Host: ip address or domain.com</p>

<p>port: 22 or similar</p>

<p>destination path: /path/to/site_username/</p>

<p>in the destination path set it to be just above public and then you'll deploy /site_username/craft and site_username/pubic</p>

CC BY-SA 3.0
2017-01-27T12:45:02.847Z
Sounds like a plan, but isn't this giving you problems with the already excisting public folder? Or is it just deploying the contents of the public folder and not replacing the folder itself.

Deploybot support suggests two server environments leading to the same destination server and each connected to the same branch but with a different source path. 

So the public and the craft deployment run in seperate environments but lead to the same server but with a different destination and sourcepath.
Dennis
CC BY-SA 3.0
2017-01-27T14:23:39.077Z
@Dennis Deployment sends files into the already existing folder. No problems. Deploybots suggestion of two server environments seems overly complicated especially since what I'm doing already just works.
CreateSean
CC BY-SA 3.0
2017-01-25T20:57:44.443Z
2017-01-25T21:27:38.200Z
2017-01-25T21:27:38.200Z
CreateSean
<p>I would like to commit my craft project to bitbucket en deploy it with the help of Deploybot. </p>

<p>The plan is to put the templates (in craft folder) and public assets (public folder) under version control and deploy it with Deploybot. But how do i get the files published into the right directories on the live/staging server. </p>

<p>My craft folder is outside the public root and the public files/assets are inside the public root. So i have two source directories and two destination directories, and this isn't an option with Deploybot. Is there someone with the same setup and a solution? </p>

<p>Thnx in advance!</p>

CC BY-SA 3.0
2017-01-26T05:51:17.563Z
Who is your host?
a-am
CC BY-SA 3.0
2017-01-27T12:45:49.600Z
standard shared hosting with directadmin as controlpanel
Dennis
CC BY-SA 3.0
2017-01-27T14:56:24.543Z
Will you be deploying via FTP? If so when you setup your FTP credentials see if you can have access to the parent folder of `public`.  This way you can publish to that folder.
a-am
<deployment>
Craft folder deployment outside public folder
# Craft folder deployment outside public folder

(Asked by: username_0 on 2017-01-25)

I would like to commit my craft project to bitbucket en deploy it with the help of Deploybot.

The plan is to put the templates (in craft folder) and public assets (public folder) under version control and deploy it with Deploybot. But how do i get the files published into the right directories on the live/staging server.

My craft folder is outside the public root and the public files/assets are inside the public root. So i have two source directories and two destination directories, and this isn't an option with Deploybot. Is there someone with the same setup and a solution?

Thnx in advance!

**Tags:** deployment
> **Comments:**
> **username_1**: Who is your host?  
> **username_0**: standard shared hosting with directadmin as controlpanel  
> **username_1**: Will you be deploying via FTP? If so when you setup your FTP credentials see if you can have access to the parent folder of `public`.  This way you can publish to that folder.  

---

## 1 answers

### Answer by username_2 on 2017-01-25. Score: 3 | Accepted answer

Dennis,

I use deploybot with Craft and easily deploy. So on your server settings you'll have this:

name: your site name

Host: ip address or domain.com

port: 22 or similar

destination path: /path/to/site\_username/

in the destination path set it to be just above public and then you'll deploy /site\_username/craft and site\_username/pubic

> **Comments:**
> **username_0**: Sounds like a plan, but isn't this giving you problems with the already excisting public folder? Or is it just deploying the contents of the public folder and not replacing the folder itself.  Deploybot support suggests two server environments leading to the same destination server and each connected to the same branch but with a different source path.   So the public and the craft deployment run in seperate environments but lead to the same server but with a different destination and sourcepath.  
> **username_2**: @Dennis Deployment sends files into the already existing folder. No problems. Deploybots suggestion of two server environments seems overly complicated especially since what I'm doing already just works.  

---

