TECHNOVERGENCE

jeudi 1 août 2013

This plugin will allow you to preview your markdown file in a browser with the alt+m command.SHIFT + COMMAND + P to show the command pallet write on it Package Control: Install Package Then look for Markdown Preview.

Install live Relaod : Look for livereload

Once installed, you markdown preview will be updated on each file save.

mercredi 7 mars 2012

In the precedent post we have seen how to install and run MySQL 5.5 on a Debian server that was already running MySQL 5.1.
In this post we will go farther and see how we make an init script to start/stop MySQL
Configuration files and scripts are available for download on our git repository at bitbucket

‣ Copy and update Debian configuration files:

Copy both debian.cnf and debian-start from your old /etc/mysql folder or download them from our repository.

‣ make symlink for binary ( to make 'kill' command working )

Update paths accordingly or use the bash script (update-mysql-init.d) containing sed commands which is available for download in the repository also.

‣ Add the debian-sys-maint user

Please, use the create_debian-sys-maint_user.sql script available on the repository to create debian-sys-maint user. Make sure to provide the script with the debian-sys-maint password as argument. The password can be found in /etc/mysql-5.5/debian.cnf

After some googling, I found an answer on
SO.
It seems that the problem was caused by some characters
like an 'emoji' character aka japanese smiley face.

There are known issues storing 4byte utf characters in some versions of MySQL that were fixed by using utf8mb4 to represent 4 byte UTF characters, as the normal utf8 character set can only represent characters up to 3 bytes in length.

This has been fixed on MySQL 5.5.3 and we will see in this post series how to run different versions of MySQL on the same Debian server.
In this first post, we will install the server, of course we will keep the old instance of MySQL running. We will make sure that the new server can be started before we will move on to the next post that describe how to make an init script to start/stop your new MySQL server with grace.

But wait, why not just upgrade to the new version with aptitude?

Because, there are other applications using the current MySQL
server that I don't want to disturb.If you don't have this constraint or if you are starting from scratch, I recommend installing the latest version of MySQL using aptitude with dotdeb.org because in Debian Squeeze, the current version of MySQL is (and it remains forever) the 5.1.x

Installing a fresh MySQL 5.5 server:

‣ make sure you have a full safe backup of all of your data and configuration files.

‣ Get your my.cnf configuration file

You can checkout my configuration file which contains some optimization, especially if you don't use MyIsam engine (I'm using Innodb engine exclusively) so I deleted some useless options like: key_buffer that was defined by the debian version of my.cnf

The
datadir
option which is where MySQL store data, was set to a directory located
on a partition with enough space to hold your data

datadir = /usr/local/appservers/mysql-5.5/data

For performance issue, query logging was disabled:

general_log and general_log_file

Finally, I included some additional configuration files
(lower_case_table_names.cnf, mysqld_safe_syslog.cnf)

‣ Stop the server

mysqladmin --defaults-file=/etc/mysql-5.5/my.cnf shutdown

Success, we have been able to install a new version of MySQL server on a machine that was running an old instance of MySQL.
Now, jump to the next post to see how to use /etc/init.d/mysql-5.5 start|stop command and how to make your new server start at system boot.

The short story is that the console.log was inside a database callback function that was called while I was moving to another page.

The long story is :

- The user open the extension popup, and try to log in.
- If login was successful we store in the database his login and status and move the user to the protected content, in our case it is the sms sending page.