By geneatwell on

I have a static site that I am going to replace with Drupal. Having researched, piddled, cursed and come to truly enjoy working with this CMS over the last year, I am finally ready to begin the final phases of the project. I created a local site and experimented with Drupal to the point that I now want to do the last bit of development on the server instead of my localhost.

The static site is currently on a shared hosting service, where it will stay when I convert to Drupal, and I am restricted to using the public_html sub directory for the index.html or index.php in order to display the domain name without any subdirectories being displayed. (if I put it in the drupal sub directory of public_html, then the URL displayed will be mydomain.org/drupal and I want to avoid that and tech support says any kludges will be more headache than helpful.)

My solution is to install Drupal in the public_html sub directory and point the .htaccess to the index.html file until I have finished developing the Drupal site at which point I will point it to the index.php file. My thinking is that I should be able to access the development site at mydomain.org/index.php until I am happy with the new Drupal site and then change the .htaccess file.

Am I out of my mind or will this work?

If it will work, can anybody who has done so tell me what were some of the pitfalls that you can remember?

Thanks in advance

⋅ Categories: Drupal 6.x

Comments

bwv’s picture

bwv commented

This sounds fine to me -- frankly I do not understand why people start out creating their site on a home computer, especially when one has the option of using .htaccess to redirect visitors to another index file as you intend to do. I hope you do not encounter problems after you upload your local version of your site -- I have seen several posts in the last couple of weeks from folks who developed their site locally, uploaded to the server, and then encountered multiple 404 errors. If you have not created much content on your local machine, you might want to consider starting with a fresh install on the webhost server. Just my 2 cents.

geneatwell’s picture

geneatwell commented

The database is small enough that I will most likely recreate the whole shebang on the server since the reason I am moving to the server now is because I do not want to download thousands of photos to the new site and then upload them back to the server. I'll take your 2 cents, bwv, and thanks for the advice and quick response.