Hiding My MODxCMS Install (For Testing)

I’m just starting out with MODxCMS. (I’ve read a lot of documentation, but never worked with the software)


So I wanted to just test out MODxCMS, and build myself a kind of temporary "sandbox."

I have a domain name I’d like to use, but I don’t want my MODxCMS "sandbox," to appear when someone visits the top-level of my domain name.
(such as example.com)



My idea for this, was simply to install MODxCMS (Revolution) to a sub-directory, and use robots.txt to block search engines from indexing that sub-directory.

In other words:
I would install MODxCMS to
example.com/testing

Rather than
example.com



- Is my plan the best method? Or might there be better way?
- If my plan will work, are there any major changes I should make to my MODxCMS installation setup?


Thank you for your time.

If all you want is to make sure it won’t turn up in search engine results it is sufficient that way.

Although if someone, somehow found your url (brute forced or if you posted a link somewhere) he’ll have no problem acccessing your site. To account for this you could easily use the .htaccess / .htpasswd combo to protect your directory from any access (if you use apache that is).

If you’re interested here is a good explanation along with a generator tool.

Just install MODx in the subdomain (or move it there and rerun setup).

If you’re using friendly urls on your sandbox, make sure to also change the rewritebase to /example/.


As for whether it’s the best method or not... there’s not a single best method. A localhost (eg xampp) may be better, but sometimes it may be easier to work on a real server. Then again, it may be easier to use a different domain all together, but in the end the only difference is a file path, probably.

Thank you both for the quick replies!


Quote from: MrDutchy at Jan 05, 2011, 07:20 AM

If all you want is to make sure it won’t turn up in search engine results it is sufficient that way

Yes, that’s my goal.

Quote from: MrDutchy at Jan 05, 2011, 07:20 AM

Although if someone, somehow found your url (brute forced or if you posted a link somewhere) he’ll have no problem acccessing your site. To account for this you could easily use the .htaccess / .htpasswd combo to protect your directory from any access (if you use apache that is).

That’s a good point; using a sub-domain won’t hide my testing from experienced eyes.


But my two objectives are, preventing bots from publishing irrelevant search results and avoiding visitor-confusion.

So security isn’t a major concern.

After all, the only thing people will find, is Lorem Ipsum and programming tests.

Quote from: MrDutchy at Jan 05, 2011, 07:20 AM

If you’re interested here is a good explanation along with a generator tool.

Ah, that may be handy one day; thank you for the link.







Quote from: Mark at Jan 05, 2011, 02:20 PM

Just install MODx in the subdomain (or move it there and rerun setup).

Great, I’m glad to hear the process is simple.


Quote from: Mark at Jan 05, 2011, 02:20 PM

If you’re using friendly urls on your sandbox, make sure to also change the rewritebase to /example/.

Aha, I had a feeling that extra steps might exist.

Thank you for saving me some headaches.


Quote from: Mark at Jan 05, 2011, 02:20 PM

As for whether it’s the best method or not... there’s not a single best method. A localhost (eg xampp) may be better, but sometimes it may be easier to work on a real server.

Yes, I did some reading about running MODx on a local server.

But the reason I wanted to test on a remote server, is to see the actual loading-times of my pages.

Local servers are helpful for many things, but I don’t want to mislead myself about page-loading times.


Quote from: Mark at Jan 05, 2011, 02:20 PM

Then again, it may be easier to use a different domain all together, but in the end the only difference is a file path, probably.

Actually, my current plan involves using a different domain for testing.

But the domain I am using for testing, will eventually be used for production.

So my objective, is to keep my testing hidden from casual visitors.

You can also install MODx on your own computer with a localhost server such as XAMPP or the equivalent. Then no one can access it but you, the file access will be much more convenient, and the browser response will be quicker.

Later, you can move the site to a live server.

Quote from: BobRay at Jan 06, 2011, 01:39 AM

You can also install MODx on your own computer with a localhost server such as XAMPP or the equivalent. Then no one can access it but you, the file access will be much more convenient, and the browser response will be quicker.

Later, you can move the site to a live server.

Downside is if you want to run it on a unix server later, you may not have correct file permissions set. That is if you develop on non-unix you won’t. This is why I personally avoid the local approach.

Also it has advantages to test without the lightning speed of a local environment. You might spot some speed issues you would have missed otherwise.

Quote from: BobRay at Jan 06, 2011, 01:39 AM

You can also install MODx on your own computer with a localhost server such as XAMPP or the equivalent. Then no one can access it but you, the file access will be much more convenient, and the browser response will be quicker.

Later, you can move the site to a live server.

I considered such an idea, but as I’ve said above (and below) I want to test for speed from the beginning; so I’m using a remote server.

By the way, thanks for publishing such easy-to-understand guides on your website!






Quote from: MrDutchy at Jan 06, 2011, 04:34 AM

Downside is if you want to run it on a unix server later, you may not have correct file permissions set. That is if you develop on non-unix you won’t. This is why I personally avoid the local approach.

Well if I ran a local server, I would using Unix on my machine.


Quote from: MrDutchy at Jan 06, 2011, 04:34 AM

Also it has advantages to test without the lightning speed of a local environment. You might spot some speed issues you would have missed otherwise.

Agreed; the main reason I want to test on a remote server, is for speed testing.

You can also configure your site to be "offline", with a specified "offline" resource that redirects or simply says the site is offline. Logged-in Manager user can see the site normally.