#server config

สำหรับคนที่เปิดเซิร์ฟเวอร์เกม The Forest ในแบบ Dedicated Server นั้น เราจะสามารถตั้งค่าต่างๆของเซิร์ฟเวอร์ได้มากกว่าการเปิดเซิร์ฟเวอร์แบบ Listen Server ซึ่งใช้ตัวเกมในการเปิด แต่ก็แน่นอนว่าวิธีการตั้งค่าก็จะซับซ้อนกว่าเช่นกัน โดยเราสามารถตั้งค่าต่างๆได้ดังนี้

สำหรับการตั้งค่านั้น เราสามารถเพิ่มเติมและแก้ไขการตั้งค่าต่างๆของเซิร์ฟเวอร์ได้จากไฟล์ที่ชื่อว่า Server.cfgซึ่งภายในจะมีคำสั่งอยู่ส่วนใหญ…

If you have the resources (CPU + RAM) available on your server then its can be a great troubleshooting tool if you enable MySQL logging which includes server messages, SQL query logs, and slow query logs. If you do not have the resources I would suggest only enable minimal logging such as only server messages and the slow query log since enabling all queries to be written to a file can become expensive rather quickly. Below I discuss enabling three different types of MySQL logging, adding a MySQL configuration file to logrotate, and configuring root to run mysqladmin commands without having to type the password out each time.

Enable MySQL Logging:

First we are going to enable the various types of MySQL logging. I would keep an eye on the query log just in case it becomes to resource intensive. Below I will display the configuration command to enable each type of logging including creating the file and directory that MySQL will log to.

Modify The my.cnf MySQL Config File:First lets add the statements to the MySQL configuration file which by default is typically /etc/my.cnf. There will probably be a minimal set of configuration items in this file if you have never modified it. Add the below lines which include comments above each one to explain what will be logged.Configure my.cnf To Log Queries, Errors, Slow Queries:

Create MySQL Log Directory: I like to try and split services up in the log directory so I can keep track of things easier so in this case we are going to do the same. In the command list below we will be creating a directory, creating blank files, and then making sure everything has the right permissions and is owned by the proper user which should be the “mysql”.Create MySQL Log Directory & Log Files:

Restart MySQL & Verify Logging:Now lets restart MySQL and verify the logging is operational. You can restart MySQL by issuing the below command.Restart MySQL:

Configure Root User MySQL Access:Now in preparation for the logrotate mysql configuration file you want to add a file to the root users home directory so that user can flush the log files without having to use a username and password every single time. If you attempt to flush the MySQL logs before you add the below configuration file you will receive an error similar to the below.Error When Running mysqladmin flush-logs Without A Password:

Add Logrotate MySQL Configuration File: Now add the below configuration contents to a new file named “mysql” in the “/etc/logrotate.d/” directory.The mysql Logrotate Configuration File Contents:

# Will log MySQL Errors Including Startup Errors log-error=/var/log/mysql/mysqld.log # Will log MySQL queries, This log will grow quickly general_log = 1 general_log_file=/var/log/mysql/mysql.log

# Will log MySQL queries that take a long time (in this case over 1 second as specified below) slow_query_log = 1 slow_query_log_file = /var/log/mysql/mysql-slow.log long_query_time = 1

The above configuration lines should go under the main section of MySQL which should be “[mysqld]” at the beginning of the file. The next section doesn’t start until “[mysqld_safe]” so as you can see there are typically two sections and they are divided by these headings.

[root@dev ~]# mkdir /var/log/mysql [root@dev ~]# touch /var/log/mysql/mysql.log [root@dev ~]# touch /var/log/mysql/mysqld.log [root@dev ~]# touch /var/log/mysql/mysql-slow.log [root@dev ~]# chown -R mysql.mysql /var/log/mysql [root@dev ~]# chmod -R 664 /var/log/mysql/

So notice that all of the new files will be owned the mysql user in the mysql group and they will allow reading from all users and writing from the mysql user and members of the mysql group.

[root@dev ~]# /etc/init.d/mysqld restart Stopping MySQL:  [  OK  ] Starting MySQL:  [  OK  ] [root@dev ~]#

If MySQL fails to restart and this is a live server quickly make a backup of my.cnf, remove the changes,and start MySQL so your downtime is minimal. If you follow the directions above you should be fine but I wanted to mention just in case there were any issues with the restart. Now visit some web pages on your site to generate some of the MySQL queries to the database and then view the log files to verify logging is functional. You can view the log files in real time by using the tail command as displayed below.

View New MySQL Log Files In Real Time With Tail:

[root@dev mysql]# tail -f mysql.log FROM wp_posts WHERE MONTH(post_date) = '12' AND YEAR(post_date) = '2009' AND post_type = 'post' AND post_status = 'publish' AND post_date < '2009-12-20 12:52:13'

[root@dev ~]# /usr/bin/mysqladmin flush-logs /usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Access denied for user 'root'@'localhost' (using password: NO)'

Use your favorite editor such as vi as the root user  to create a file by the name of .my.cnf in /root/. Add the contents below to this file but of make sure to modify the username and password in the example below to include a MySQL username and password that has access to run “mysqladmin flush-logs”.

New /root/.my.cnf File:

[mysqladmin] user               = root password        = changeme

Make sure that you set the proper permissions for the above file once you have created it so that no other users on the server can read the file contents and find out what the MySQL root password is. To set the proper permissions use the below command.

Set Permissions On /root/.my.cnf:

[root@dev ~]# chmod 600 /root/.my.cnf

Now you can run the “mysqladmin flush-logs” command as the root user without having to enter a username or password and without receiving an error.

/var/log/mysql/*.log { create 644 mysql mysql notifempty daily rotate 5 missingok nocompress sharedscripts postrotate # run if mysqld is running if test -n "`ps acx|grep mysqld`"; then /usr/bin/mysqladmin flush-logs fi endscript }

The basis of the file is that it will rotate any files in the MySQL directory that end with “.log”. Once the files are rotated the new files will be generated by the mysql user with permissions of 644. The files will not be rotated by Logrotate unless they have contents. The files will be rotated daily and five copies will be retained. Logrotate is not going to panic if there is a file missing and when all is said and done the root user will run “mysqladmin flush-logs” to flush out the log files so logs will continue to write to the proper files.

Although this is very easy process, but everyone described this process in very complex way. I have a tough time. This is my attempt to simplify all those complexities.

Just Purchase the certificate from SimpleDNS.

Submit the private key, DNSimple can do this for you. Allow them to generate private key for you. This is private.key.

After few days you will receive an email from COMODO Group. They will provide you certificate. This is server.crt. This certificate is at very end of the email. See this

Now, enable mod_ssl apache extension if it is not enabled. (Skip this step now. If at last if it doesnt work then do this)

Copy both of this files, private.key and server.crt and add it in some folder.

Now, configure the apache site specific config file. So, it will be look something like this if you're using rails

<VirtualHost *:443> ServerName test.example.com #!!! Be sure to point DocumentRoot to 'public'! RailsEnv staging DocumentRoot /home/ubuntu/staging/public <Directory /home/ubuntu/staging/public> #This relaxes Apache security settings. AllowOverride all Allow from all Require all granted #MultiViews must be turned off. Options -MultiViews </Directory> SSLEngine on SSLCertificateFile /home/ubuntu/staging/certs/server.crt SSLCertificateKeyFile /home/ubuntu/staging/certs/server.key

Add CNAME record in DNS . It will look something like this

CNAME test.example.com 3600 example.com

Wait for an hour and then restart the server. It will suppose to work. Let me know if you have some problem.

When we were building PuzzleSnap, we wanted to ensure one of the problems we addressed early on was being able to keep up with growth of the app. Since we were a very small engineering team (3 developers), and were pretty broke, we needed a cost-efficient solution that could address the following needs:

We needed something that wouldn't bankrupt us.

We were bootstrapping like crazy!. I think in total we spent only about $500 to $1000 bucks in getting Puzzlesnap off the ground, and that was just to form the LLC. 

We needed something that was relatively easy to maintain.

All of us had hectic schedules, and the last thing we needed was something that had a lot of up-keep. We wanted something that was fairly simple to setup, and maintain.

We needed something that could scale extremely fast (incase we took off).

Everyone says "explosive growth" is a good problem to have, but it still sucks when you have people wanting to play your app, and the service goes down because you can't keep up with the demand. People don't give a shit about your "backend infrastructure issues".

We needed something that was fairly dependable.

As with ANY solution, there is never a 100% up-time guarantee, however we needed a solution that could come close to it. 

We needed something that we could closely monitor from anywhere.

Since we were all living in Dallas, but didn't have a "formal" office, we needed something that could be monitored anywhere, as long as we had Wifi. After evaluating different options, we decided to finally move forward Amazon Web Services. Since we were fairly new to AWS, the whole process of getting it up and running was a huge learning experience for us. There were a variety of solutions, and learning what each of them did was a challenge in itself. Understanding the difference between EC2, S3, RDS, EBS, Cloudfront, and so on, took some getting used to.  However, part of being entrepreneurs is being able to hustle and learn things on the fly. We finally figured it all out and how the whole "cloud" AWS ecosystem worked. For those who've never used AWS, the following is a 30,000 ft overview of what some of the services are: EC2 - Virtual servers on the cloud. You could instantly deploy servers with the click of a mouse button. S3 - Virtual hard-drive with unlimited storage space. We used it to store all our images. RDS - Virtual MySQL databases on the cloud. No worry about your DB going down if your application server went down. EBS - Elastic Beanstalk - Amazon's tool to quickly deploy and manage apps in the cloud. Cloudfront - Content delivery network that made it easy to distribute content around the world. For Puzzlesnap, the following was our server config. Pardon the ghetto drawing. I was too lazy to make it on Word or Visio :) 

We'd tried to separate all the components of the app to ensure redundancy.  1) The images got saved onto an Amazon S3 bucket, which was separate from EC2 / RDS. So if one of those services went down, we still wouldn't lose our images. 2) The data got written to our master Amazon RDS MySQL database, which is separate from S3 / EC2. So if S3 or EC2 went down, we wouldn't lose our data. 3) The data got read from our slave Amazon RDS MySQL database, which automatically got all it's data from the master DB. 4) The loadbalancer would automatically share the load across 4 of our instances which was separated into two zones. Currently it's all set to micro (since we haven't formally launched yet. However a week before launch, we will change it all to medium. Luckily, changing the instance type is a piece of cake.) Amazon also makes it super easy to deploy new servers horizontally incase we need to. We keep backup private images that we use to deploy servers really quickly.   On top of all that, we're hoping to take local backups as a final means of data protection. The cool thing of this setup is that all the services are pretty independent of each other. With that being said, this is still far from the "perfect" setup. We still sort of have no idea what we're doing, and we're hoping we'll continue to play it by ear.

We're also well aware of Amazon's recent outage, which scared us a little bit. But, hey, what are you gonna do? No setup will ever be perfect, so we're hoping things will be fine when we launch. Hopefully PuzzleSnap does take off. If it does, we're ready!