<p>In general, developing a website on the live server is a risky thing. Should something go wrong while you're developing then you risk the live website. It's unlikely, but an accidental upload to the wrong folder, or a wonky SQL statement, or anything like that can happen.</p>

<p>If you must run the site on the live server though, your best bet is to set up a sub-domain such as beta.mywebsite.com. Host that on your live server and do all the development there. Then, when it's time to retire the old site and make the new one 'live', you can move the files across from the beta directory to the www one.</p>

<p>I wouldn't recommend doing that though. Much less risky to get your local machine set up as a development server, do it all on that, and then put the site live.</p>

CC BY-SA 3.0
2015-08-07T00:03:51.467Z
Thanks so much Matt. I'd like the client to be able to see what's going on though. So I'm thinking I should back up the live site and then set up a sub-domain. Does Craft transfer over well just by moving the files? I should upload craft and go through the installation process in the live domain before moving the files over I imagine?
Heyward
CC BY-SA 3.0
2015-08-10T11:43:45.673Z
If you're going to be doing this sort of thing regularly it sounds like what you really could do with is a staging server - a cheap linode or something would do. It's just somewhere to show clients work, and maybe have them do data entry, which isn't your local machine and isn't a live server.

Backing up is always a good idea. Moving Craft from a sub-domain to the main domain ought to be no more than moving the files across, and perhaps changing a path in the config.php file. You shouldn't need to re-install anything if you're just moving from a sub domain to the main one.
Matt Wilcox
CC BY-SA 3.0
2015-08-06T08:07:58.377Z
2015-08-06T08:07:58.377Z
Matt Wilcox
<p>I'm gungho to get started building in Craft but I don't want the complications of moving the site over from a development directory. Is there a way to easily do this while the current site is up and running?</p>

CC BY-SA 3.0
2015-08-06T05:38:09.463Z
I'm a bit confused... are you asking if you can have the live site at `domain.com` and the in-development site at `www.domain.com`?  Or do you want the live site to live at both of those domains and have the development site live at something like `dev.domain.com`? Regardless, is anything stopping you from just developing locally first and deploying to live when you're ready?
Brad Bell
CC BY-SA 3.0
2015-08-07T00:06:07.857Z
I was wondering if I could just rename index.php to home.php or something like that and do it all in one domain. But it seems like a sub-domain makes more sense. I'd do it locally but I need the client to be able to easily see what's going on. Thank you so much for responding. any futrher advice would be greatly appreciated.
Heyward
<installation><hosting>
Can you beta build a Craft site in the www directory while the current site is still running?
# Can you beta build a Craft site in the www directory while the current site is still running?

(Asked by: username_0 on 2015-08-06)

I'm gungho to get started building in Craft but I don't want the complications of moving the site over from a development directory. Is there a way to easily do this while the current site is up and running?

**Tags:** installation, hosting
> **Comments:**
> **username_1**: I'm a bit confused... are you asking if you can have the live site at `domain.com` and the in-development site at `www.domain.com`?  Or do you want the live site to live at both of those domains and have the development site live at something like `dev.domain.com`? Regardless, is anything stopping you from just developing locally first and deploying to live when you're ready?  
> **username_0**: I was wondering if I could just rename index.php to home.php or something like that and do it all in one domain. But it seems like a sub-domain makes more sense. I'd do it locally but I need the client to be able to easily see what's going on. Thank you so much for responding. any futrher advice would be greatly appreciated.  

---

## 1 answers

### Answer by username_2 on 2015-08-06. Score: 2 | Accepted answer

In general, developing a website on the live server is a risky thing. Should something go wrong while you're developing then you risk the live website. It's unlikely, but an accidental upload to the wrong folder, or a wonky SQL statement, or anything like that can happen.

If you must run the site on the live server though, your best bet is to set up a sub-domain such as beta.mywebsite.com. Host that on your live server and do all the development there. Then, when it's time to retire the old site and make the new one 'live', you can move the files across from the beta directory to the www one.

I wouldn't recommend doing that though. Much less risky to get your local machine set up as a development server, do it all on that, and then put the site live.

> **Comments:**
> **username_0**: Thanks so much Matt. I'd like the client to be able to see what's going on though. So I'm thinking I should back up the live site and then set up a sub-domain. Does Craft transfer over well just by moving the files? I should upload craft and go through the installation process in the live domain before moving the files over I imagine?  
> **username_2**: If you're going to be doing this sort of thing regularly it sounds like what you really could do with is a staging server - a cheap linode or something would do. It's just somewhere to show clients work, and maybe have them do data entry, which isn't your local machine and isn't a live server.  Backing up is always a good idea. Moving Craft from a sub-domain to the main domain ought to be no more than moving the files across, and perhaps changing a path in the config.php file. You shouldn't need to re-install anything if you're just moving from a sub domain to the main one.  

---

