Jump to content
MDDHosting Forums

kuemerle5

Clients
  • Posts

    69
  • Joined

  • Last visited

  • Days Won

    2

kuemerle5 last won the day on December 7 2011

kuemerle5 had the most liked content!

About kuemerle5

  • Birthday 06/20/1991

Profile Information

  • Gender
    Male

kuemerle5's Achievements

Member

Member (2/5)

6

Reputation

  1. All you need to do is create a folder, say "classifieds" in "/home/[username]/public_html" which is where the all of the files of your main website most likely reside. That folder will then be accessible through "www.yoursite.com/classifieds". Hope this helps!
  2. There is an option in cPanel to allow external hosts to connect to your MySQL server. Click the link for "Remote MySQL" and add the hostname or IP address of the computer that's going to be performing your backups.
  3. Absolutely! What you're asking for is called an "addon domain" and they're super easy to set up in cPanel. To start, login into cPanel and click on the "Addon Domains" link and fill in all the text fields. After you enter a domain name, cPanel will automatically suggest an FTP username and location to store files for your new domain. Type in a password and you've got another domain hosted on the same account When you add another domain like this, your DNS records should be updated automatically but Mike or Scott will correct me if I'm wrong on that. Good luck!
  4. Since the MySQL and web server run on the same machine, you can just put in "localhost" for the server address.
  5. Hmm, still a little odd with the whole email thing. That part is probably best solved with a support request. As for the "flashing," I'm not seeing it (using FF 8 beta). Maybe trying clearing your cache?
  6. Just to make sure I understood everything completely, basically what you want to do is fully transfer your second domain & website to MDDHosting (nameservers and email settings) before you begin transferring your primary one. First off, if you don't change anything related to your primary domain, nothing should get "jacked" Second, make sure the nameservers you are using (I assume MDD's nameservers) have an MX record to indicate where the mail server for that domain is. In your case, for your second domain, assuming you changed the nameservers to ns[x].mddservices.com already, in cPanel>Advanced DNS Zone Editor there should be an MX record that points to yourdomain.com. Here's what mine looks like using CloudFlare (it'll look similar-ish in cPanel): http://i.imgur.com/rE8DX.png Also, in terms of your last issue of mail not being sent, make sure when you send the email, you can start to figure out where the bug is if you use an IP address for the mail server instead of just yourdomain.com. Second, make sure you are using an SMTP server to send the emails, aka using an IP address again and make sure you authenticate because I believe most shared hosting smtp servers require authentication. I have a feeling that once the MX record in the nameserver propogates through the internetz, the problem might fix itself. Hope this helps!
  7. In cPanel, right after you login, check out the column of stats on the left hand side of the page. One of those items is labeled "Server Name" and whatever is listed there is the name of which server you are on. One of those names will match up with one listed on MDDHosting's server status page. Hope this helps!
  8. Research Update After reflecting upon Apache + PHP fcgi, I have come to some conclusions and extra information. If you are not using mod_php, it would be an extreme n00b mistake to install prefork for Apche's MPM. Best option would be to use either worker or event (which I believe is the method Nginx employs but is currently experimental in Apache). @Adam: Do you know if Cherokee is also event based?Since mod_php is not guaranteed to be thread friendly (due to all the libraries), I am ultimately forced to use some sort of cgi processing for PHP.PHP FPM I feel is currently the best route. This is because you get the benefits of fastcgi (process continues to live after being used, eliminates startup times, etc.) and will allow me to have a separate server solely to execute PHP scripts (need be). This has one big benefit: If the server is receiving enormous amounts of traffic, I can order up another node and have it up and running with PHP FPM. Just a quick fyi: PHP FPM can listen on either a TCP/IP port or utilize a socket connection. At this point, I can have, say, 2 of my sites switched over to use the new node's PHP FPM which will reduce load on the first node. While this route is definitely trickier, I think it's worth it to have a server(s) that functions as efficiently as possible. And, to be honest, I think this whole PHP FPM thing is overkill because I will be using XCache so the whole separate node to process PHP thing is pretty much never going to happen. I guess that's pretty much it. The big thing was really just getting rid of the ancient, disgusting monster that is Apache prefork.
  9. Haha, thanks! Yes, my recent threads in this forums have been similar I would like to use Cherokee if only it were compatible with mod_rewite (then, I would be willing to learn all the ins and outs of it) but I figured Nginx and XCache will at least get me close to Cherokee speeds. Do you have anything set up (available to the public) on your server to see performance? Also, just curious, but why did you choose Debian over Ubuntu server? Oh, and another question: is Percona administered in a similar manner to MySQL? E.g I can use phpMyAdmin and such?
  10. Alright, so, if you've read the previous two threads in this forum, you'll know that I'm planning on setting up a web server from scratch on a VPS. In this post, I'm going to detail the process I plan to use and possibly some tips/tricks that will help others along the way. Now, onto the good stuff After much research and option weighing, I have come to the conclusion that I will be using Apache + PHP fgci behind Nginx. Now, before everyone gets into an uproar as to why I just didn't opt all for Nginx, I'll explain why: Running Apache behind Nginx will allow me to retain mod_rewrite capabilities, so that I don't have to deal with rewriting the rules specifically for Nginx.Using Apache + PHP fcgi over mod_php was decided because of the lower memory footprint which is vital is pretty much any server environment. Using fcgi does have its downsides though; I will be unable to set PHP directives from the htaccess file as I have grown used to over the years. This means that I will have to come up with a PHP configuration that kicks butt and works well for my combination of mostly WordPress and Drupal powered sites.Much faster page load times; duh!Applications will see that they are being run from Apache, which is good because some web apps might disable certain functions if they detect they are being run on different server software.All in all, I think I've come up with a winning combination; I've added awesome page load times but really only lost functionality that was negligible to begin with (setting PHP directives from .htaccess). I felt that if I went all Nginx, I would be adding complexities that, quite frankly, I didn't know/want to deal with with the only benefit of *maybe* getting slightly better load times and less memory usage. Another high performance web server that I looked at was Cherokee. Cherokee is probably just as fast and lightweight as Nginx (don't quote me on that ) and also includes an awesome web interface to configure the server. Unfortunately, like Nginx, Cherokee does not have mod_rewrite compatibility and again, I'm not going to run mission critical web server software that I don't know how to fully work in case something were to go wrong. All of the above also applies to lighttpd. Now, onto the database layer in that juicy web stack. I will being running Percona just because I have yet to see an argument yet about why I shouldn't run it. In the WHT forums, a guy said that I probably will not notice the difference between Percona and MySQL for the size of my server. Keeping in mind that memory is king, I wanted something like Nginx that could handle connections consistently even when put under a lot of stress. It is possible to optimize MySQL to use less memory by more or less following the "my-small" config to reduce the memory footprint and such. However, this does not address the issue that the InnoDB storage engine simply cannot handle as many transactions as the XtraDB engine can. OK, so the big stuff is out of the way now but there are still more things I can do to optimize my setup. First thing is some sort of caching mechanism. While I haven't looked into caching and Nginx I do have experience with Apache, PHP, and XCache and let me tell you, XCache is truly amazing. For those of you who don't know, XCache is a PHP opcode cacher made by the same folks who make lighttpd. I never really thought much of of XCache until I installed it on my buddy's server and let me just share some of the statistics: 480.07Kb file reduced to 69.63Kb30.70Kb file reduced to 3.03Kb5.35Kb file reduced to 637.00b (that's bytes folks)On average, with the current configuration, XCache has approximately 120 files cached at any one time. But I must warn you: XCache was not easy to configure. Not the syntax, but the "best" settings. It took me a while to figure out the settings which worked best and it's going to be different for each server. For example, in the beginning my OOMs (out of object memory) were going through the roof and I just had to play with the setting to keep the number as low as I could. Another issue I ran into was the memory filling up right away which is also no bueno. For those of you really curious, I've uploaded a screenshot of the XCache overview page to see my config and the general "stats". To those of you now wanting to use XCache: I strongly urge you to build it yourself as I couldn't find any up to date repos and building it was super simple; just follow the instructions. The second step you can take to speed up your server is CloudFlare which you can easily opt into here at MDDHosting through your CPanel (w00t!). Not only does it do an awesome job at caching files but it also functions as your DNS server which is just another load off of your machine. There's not much to say about CloudFlare except to just use it! Sorry about the writing slowly turning to crap from top to bottom (quite tired as I write this) but hopefully, you get my general gist. Hopefully, I'll get this thing running on a sandbox server in the next few days and present even more findings! Also, I'll be running Ubuntu server 11.10 (the latest) with dropbear for the SSH server as it uses less memory than OpenSSH. Yay less memory usage!
  11. It should be completely possible to accomplish what you need to do on your website by deleting everything except your forum folder. In cPanel's file manager, you can probably click select all to select all files (obviously ) and then ctrl (or apple key)+click on the forum folder so you don't delete that. As for folders that are outside of the public_html folder, you don't really want to touch those. They contain database files, emails, and pretty much everything else related to your account.
  12. Thanks for you suggestions on the software stacks. I'm just still leery on running only Nginx and PHP fast cgi or whatever because I'll lose the ability to change PHP settings via htaccess and the mod_rewrite rules are different for Nginx. Do you know if I have Apache behind Nginx, will the mod_rewrite rules in htaccess files still work? As for the Google Apps, I think I'll look into that if I'm too lazy to setup my own mail server. And, I'll take a looksie at the script to reduce mem usage. See what all it does, etc. I am also leery of automated scripts in Linux (or any OS for that matter) if I didn't write them myself or look over them. Thanks for you all you suggestions!
  13. Seeing as I am leaving the comfy shared hosting world soon for a new home in an unmanaged vps, I am in need of as much advice, information, and practice as I can get. I've been reading up a lot on performance of web servers, http accelerators, reverse proxy caches and the like and already, I feel a little overwhelmed. As I understand it, Apache by itself is a poor choice for wanting to serve up websites with a low memory footprint due to the fact that: A) each new process that Apache spawns, it uses up more memory and each connection spawns a new process and due in part to this, Apache is easily the least efficient static file server. And a sidenote on MySQL: Percona seems to be the best choice in terms of a drop-in replacement for MySQL. This is due in part to Percona's database storage engine called XtraDB whose performance far outperforms InnoDB and also scales much more efficiently. Also, the Percona server with the XtraDB engine uses less memory than MySQL. I will soon be practicing configuring a mock server I've set up at home and I have a few questions for anyone who is willing to help out (I would greatly appreciate it): If I run Apache + mod_php behind Nginx, will .htaccess files be handled as they would be if Apache were the only web server running? If so, can PHP directives be set from the htaccess file then as well as mod_rewrite rules?Logs. How should I deal with them? I feel like if I ignore them, they'll grow to ridiculous sizes and slow down the server dues to the the fact that it's harder to deal with text files in the tens of hundreds of mb area.Has anyone had any experience with the Percona server/XtraDB storage engine? Issues with it? Any reason why I should opt for MySQL over Percona?DNS servers. Should I get a third party to deal with nameserver/dns stuff or should I just bite the bullet and run my own (I have literally no experience with DNS servers)? I know BIND is the most popular followed by (if I'm not mistaken) PowerDNS. Does anyone have an opinion about which one I should be running?Email servers. I haven't looked into a comparison of email servers as much as the web servers, but I would like to know if anyone has preferences on mail servers.Operating system? I will be using Debian as I have the most experience on that unless someone is willing to make a case for another OS I should use.That should be about it. Again, I would greatly appreciate any help given here. Thank you so much!
  14. Can you tell us what the potential risk was? (after you fix it, of course
  15. Haha, yep, np Drupal 7 fixed this issue but at least you'll know about this little quirk in D6!
×
×
  • Create New...