vps

I'm trying to setup Wordpress to be able to install plugins via SFTP (SSH) on a Centos 6 VPS. I've been able to modify wp-config so it uses the right credentials with user as my SFTP user. Now I have a permission related problem, as if I do a chmod 777 on my wp-content folder I'm able to install, but with the normal permissions it can't create folders. I'm using Nginx and all my wp-content files and folders are owned by user and I've tried setting the group to nginx but it doesn't work. I also tried setting the user as nginx but still no luck. UPDATE : I found out wordpress was using apache as

The market is flooded with VPS (virtual private server) hosting options. It seems everyone and their mother has a overloaded server in his/her closet. Enterprise options always seem priced insanely high, which make the ones that are cheap and claim enterprise level seem shaky. What do you look for in a quality VPS provider (language support, 24/hr tech, etc), and how if at all do you check their credibility? whoisjake Most virtual hosting platforms will have a trial period in which you can test out their reliability. They will also give you a list of their high profile sites on their systems.

How can I deploy a Rails app to a VPS (virtual private server) or a dedicated server? It would be nice to have an easy to follow guide. I know about scripts to automate the process, but I think it's better to have everything under control, in order to understand better the process. I have successfully deployed a heavy Rails application to Linode or Digital Ocean, using these technologies: rbenv for Ruby installation nginx + Passenger for the application server PostgreSQL for the database server Capistrano to automate deploys (configure this first on your dev machine with your server IP and

Whenever I run something with Ruby on my server, I get the following error: /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/yaml.rb:56:in `<top (required)>': It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. I installed Ruby using RVM onto my VPS. I’ve tried installing the package libyaml as per instructed in other issues on Stack Overflow, to no avail. I’m not sure what type of system my VPS is running, but it doesn’t have the apt-get command. It does have yum … I had this problem and installing

小内存的VPS（尤其是Centos）在进行类似于Yum操作的时候会耗费大量的内存（相对于VPS的128MB或者更小的内存来说），所以就要禁用一些不必要的服务或者yum的插件。建议128MB内存的VPS用户最好用Deiban系统。 1 禁用Yum fastestmirror插件 Yum的fastestmirror插件能够帮助VPS找到最快的源，提高yum下载速度，不过占用内存也很夸张，据说能有100MB+！已经的命令能禁用fastestmirror插件： sed -i -e 's/enabled=1/enabled=0/' /etc/yum/pluginconf.d/fastestmirror.conf 2 禁用yum的filesystem 对VPS而言，filesystem是母机的事情，所以禁用yum检查filesystem也能节省一部分内存: echo "exclude=filesystem" >> /etc/yum.conf 3 禁用不常用的服务启动 类似于windows的开机启动，很多Linux服务也会开机启动，在小内存的VPS上可以把不是必须的服务禁用，能节省下很大部分内存： chkconfig --list| awk '{system("chkconfig "$1" off")}' chkconfig --list| awk '{if($1=="crond" || $1=

There are a bunch of managed cloud based hosting services for nodejs out there which seem relatively new and some still in Beta. Yet another path to host a nodejs app is setting up a stack on a VPS like Linode. I'm wondering what's the basic difference here between these two kinds of deployment. Which factors should one consider in choosing one over another? Which one is more suitable for production considering how young these services are. To be clear I'm not asking on choosing a provider but to decide whether to host on a managed nodejs specific hosting or on an old fashioned self setup VPS.

I am working on my first Drupal project on XAMPP in my MacBook. It's a prototype and receives positive feedback from my client. I am going to deploy the project on a Linux VPS two weeks later. Is there a better way than 're-do'ing everything on the server from scratch? install Drupal download modules (CCK, Views, Date, Calendar) create the Contents ... Thanks A couple of tips: Use source control, NOT FTP/etc., for the files. It doesn't matter what you use; we tend to spin up an Unfuddle.com subversion account for each client so they have a place to log bugs as well, but the critical first step