வோர்டுபிரஸ் ம்யூ மூலம் சப் டொமைன்

[- ரம்யாசக்திவேல்]

வோர்டுபிரஸ் ம்யூ மூலம் சப் டொமைன் வழங்குவது உள்ளது, இந்த சம்டொன் க்காக
DNS-செட்டிங்கில் செய்ய வேண்டிய மாற்றங்களை செய்துவிட்டேன்.. இருப்பினும்
ஹோஸ்டிங்கில் எப்படி மாற்றம் செய்வது என்று தெரியவில்லை..யாரேனும்
உதவுங்கள்... இணையத்தில் இதற்கான தகவல்கள் இருக்கின்றன. ஆனால்
ஆங்கிலத்தில் மட்டுமே உள்ளது. எனக்கு தமிழ்லில் யாராவது உதவ முடியுமா??

[Gilbert Raja]

உங்களது ஆங்கில தேடலை இங்கு வெளியிட்டால் என்னால் மொழிபெயர்த்து உதவ முடியும்.

உங்கள் ஹோஸ்டிங் வழங்குபவரை அழைத்தாலும் எளிதாக செய்ய இயலும்.

என்னுடைய அறிவிற்கு எட்டியவறை உங்களுடைய ஹோஸ்டிங் கணக்கில் உள் நுழைந்து சில மாற்றங்கள் செய்ய வேண்டும்.

2010/6/12 - ரம்யாசக்திவேல் <valaru...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "wordpress தமிழாக்கம்" group.
To post to this group, send email to tamil_wordpre...@googlegroups.com.
To unsubscribe from this group, send email to tamil_wordpress_tra...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tamil_wordpress_translation?hl=ta.

[AGRIINFOMEDIA-Sakthivel]

இது தான் நான் கண்டது... இதற்கு தான் எனக்கு உதவி தேவை. முடிந்தால் எனக்கு சி-பேனலில் இந்த மாற்றங்களை முயற்சித்து பாருங்கள்.. உங்கள் முகவரிக்கு சி பேனல் விபரம் அனுப்பு உள்ளேன். நன்றி... You're looking to create a custom A record. I'm pretty sure that you can use wildcards when specifying A records which would let you do something like this: *.mywebsite.com       IN  A       127.0.0.1 127.0.0.1 would be the IP address of your webserver. The method of actually adding the record will depend on your host. Doing it like http://mywebsite.com/user would be a lot easier to set up if it's an option. Then you could just add a .htaccess file that looks like this: Options +FollowSymLinks RewriteEngine On RewriteRule ^([aA-zZ])$  dostuff.php?username=$1 In the above, usernames are limited to the characters a-z The rewrite rule for grabbing the subdomain would look like this: RewriteCond %{HTTP_HOST} ^(^.*)\.mywebsite.com RewriteRule (.*)  dostuff.php?username=%1 link|flag edited Oct 8 '08 at 17:59 answered Oct 8 '08 at 17:49 Mark Biek 12.2k22064

I've offered the second option to customer, but he prefers the subdomai - it really looks better though – Skuta Oct 8 '08 at 17:53 Unless each subdomain is served off of a different server, I would thing creating Canonical Name (CNAME) records would be a better plan. en.wikipedia.org/wiki/List_of_DNS_record_types – theraccoonbear Oct 8 '08 at 17:54 The subdomain does look nice. It's going to be a lot more work to set up though because you'll have to make sure that all subdomain requests get handled properly. This isn't terrible with Apache but might be tricky in a hosted environment. – Mark Biek Oct 8 '08 at 17:55 @theraccoonbear Assuming you can use wildcards with CNAME as well, that's a thought. – Mark Biek Oct 8 '08 at 17:55 Does it actually mean that PHP code would have to add a new Rewriterule to htacccess only? – Skuta Oct 8 '08 at 17:57 show 5 more comments

1	You could [potentially] do a rewrite of the URL, but yes: you have to have control of your DNS settings so that when a user is added it gets its own subdomain. link|flag answered Oct 8 '08 at 17:40 warren 7,2402038

1

In addition to configuration changes on your WWW server to handle the new subdomain, your code would need to be making changes to your DNS records. So, unless you're running your own BIND (or similar), you'll need to figure out how to access your name server provider's configuration. If they don't offer some sort of API, this might get tricky. Update: yes, I would check with your registrar if they're also providing the name server service (as is often the case). I've never explored this option before but I suspect most of the consumer registrars do not. I Googled for GoDaddy APIs and GoDaddy DNS APIs but wasn't able to turn anything up, so I guess the best option would be to check out the online help with your provider, and if that doesn't answer the question, get a hold of their support staff. link|flag edited Oct 8 '08 at 17:49 answered Oct 8 '08 at 17:40 theraccoonbear 1,570217

1

Don't fuss around with .htaccess files when you can use Apache mass virtual hosting. From the documentation: #include part of the server name in the filenames VirtualDocumentRoot /www/hosts/%2/docs In a way it's the reverse of your question: every 'subdomain' is a user. If the user does not exist, you get an 404. The only drawback is that the environment variable DOCUMENT_ROOT is not correctly set to the used subdirectory, but the default document_root in de htconfig. link|flag answered Oct 8 '08 at 23:02 Wimmer 60427

I am not really sure how to use that.. and in the end, why not to mess up with htaccess? – Skuta Oct 9 '08 at 13:06

0	If you use Cpanel, this is a very good tutorial. link|flag answered Oct 8 '08 at 18:01 Gaurav 23615

0

I do it a little different from Mark. I pass the entire domain and grab the subdomain in php. RewriteCond {REQUEST_URI} !\.(png|gif|jpg)$ RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ /index.php?uri=$1&hostName=%{HTTP_HOST} This ignores images and maps everything else to my index.php file. So if I go to http://fred.mywebsite.com/album/Dance/now I get back http://fred.mywebsite.com/index.php?uri=album/Dance/now&hostName=fred.mywebsite.com Then in my index.php code i just explode my username off of the hostName. This gives me nice pretty SEO URLs. link|flag answered Oct 8 '08 at 18:39 gradbot 3,2651618

0

We setup wildcard DNS like they explained above. So the a record is *.yourname.com Then all of the subdomains are actually going to the same place, but php treats each subdomain as a different account. We use the following code: $url=$_SERVER["REQUEST_URL"]; $account=str_replace(".yourdomain.com","",$url); This code just sets the $account variable the same as the subdomain. You could then retrieve their files and other information based on their account. This probably isn't as efficient as the ways they list above, but if you don't have access to BIND and/or limited .htaccess this method should work (as long as your host will setup the wildcard for you). We actually use this method to connect to the customers database for a multi-company e-commerce application, but it may work for you as well.

12 ஜூன், 2010 1:19 am அன்று, Gilbert Raja <gilbe...@gmail.com> எழுதியது:

[AGRIINFOMEDIA-Sakthivel]

http://www.nerdydork.com/setting-up-wildcard-dns-subdomains-on-cpanel.html

12 ஜூன், 2010 1:19 am அன்று, Gilbert Raja <gilbe...@gmail.com> எழுதியது:

உங்களது ஆங்கில தேடலை இங்கு வெளியிட்டால் என்னால் மொழிபெயர்த்து உதவ முடியும்.

[AGRIINFOMEDIA-Sakthivel]

Installation Finished!

Congratulations!
Your WordPress µ site has been configured.

You can log in using the username "rrrrrrr" and password   xxxxxx

Warning! Wildcard DNS may not be configured correctly!

To use the subdomain feature of WordPress MU you must have a wildcard entry in your dns. The installer attempted to contact a random hostname (6df45c.media4agri.com) on your domain but failed. It returned this error message:
Couldn't resolve host '6df45c.media4agri.com'

From the README.txt:

If you want to host blogs of the form http://blog.domain.tld/ where domain.tld is the domain name of your machine then you must add a wildcard record to your DNS records.
This usually means adding a '*' hostname record pointing at your webserver in your DNS configuration tool. Matt has a more detailed explanation on his blog. If you still have problems, these forum messages may help.

You can still use your site but any subdomain you create may not be accessible. This check is not foolproof so ignore if you know your dns is correct.

Directory Permissions

Please remember to reset the permissions on the following directories:

• /home/agrimedi/public_html
• /home/agrimedi/public_html/wp-content/

You can probably use the following command to fix the permissions but check with your host if it doubt:
chmod 755  /home/agrimedi/public_html /home/agrimedi/public_html/wp-content/ 


Delete the Installer

Now that you've installed WordPress µ, you don't need the installer any more. You can safely delete index-install.php now. It's always a good idea to remove code and scripts you don't need.

Further reading

• If you run into problems, please search the WordPress µ Forums where you will most likely find a solution. Please don't post there before searching. It's not polite.
• There is also the WordPress µ Trac. That's our bug tracker.

Thanks for installing WordPress µ!

Donncha
wpmu version: 2.9.2

12 ஜூன், 2010 1:19 am அன்று, Gilbert Raja <gilbe...@gmail.com> எழுதியது:

உங்களது ஆங்கில தேடலை இங்கு வெளியிட்டால் என்னால் மொழிபெயர்த்து உதவ முடியும்.