После многих лет (буквально) мучительного выбора, где же мне публиковаться, я остановился на варианте с собственным статическим веб-сайтом, где статьи я буду писать на своём компьютере в своём текстовом редакторе, в Markdown.
Новый адрес моего блога https://hijarian.info. На блоггере я больше писать не буду.
Сайт собирается из материалов в разметке Markdown силами утилиты Hugo. Публикуется на Netlify.
Okay, today's the task: pushing all of 1892 files of Yii framework to the Git repository is a burden, and upgrading it to new version pollutes the git log with changes to files you don't care about. Let's package it into a PHAR!
Rasmus Schultz made a special script to package the Yii framework into a PHAR archive. I forked it to save for a future (at least my GitHub account will live as long as this blog).
You need just to put this script to the root of Yii codebase (cloned github repo, for example), and run it as usual:
php yii-phar.php
This will create the PHAR archive in the same directory.
Hovewer, beware the catch 1: PHP can refuse to create packed archive, emitting the following error:
PHP Fatal error: Uncaught exception 'BadMethodCallException'
with message 'unable to create temporary file'
in /path/to/your/yii/root/yii-phar.php:142
Stack trace:
#0 /path/to/your/yii/root/yii-phar.php(142): Phar->compressFiles(4096)
#1 {main}
thrown in /parh/to/your/yii/root/yii-phar.php on line 142
I decided to just remove lines 140 and 142 from the script:
echo "Compressing files ...\n\n"; $phar->compressFiles($mode);
And that's all. I can bear with 20 MB file in repo, and don't really care about compression.
To connect the resulting PHAR to your Yii application, replace your usual:
require_once('/path/to/your/yii/framework/yii.php');
With the following:
new Phar('/path/to/yii.phar');
require_once('phar://yii/yii.php');
Note that in new Phar() invocation you should use real path to your phar archive file, but second line should be written verbatim, as the PHAR which becomes created is being made with alias 'yii', using feature described in the documentation for Phar::__construct.
However, of course, there's a catch 2: Yii built-in asset manager (CAssetManager) has too specific `publish` method, unable to cope with custom PHP streams. So, we need the fixed version.
I decided to create a descendant of `CAssetManager` descriptively called `PharCompatibleAssetManager` with the following definition exactly:
/**
* Class PharCompatibleAssetManager
*
* As we use Yii packaged into .phar archive, we need to make changes into the Asset Manager,
* according to the https://code.google.com/p/yii/issues/detail?id=3104
*
* Details about packaging Yii into .phar archive can be found at
* https://gist.github.com/mindplay-dk/1607318
*/
class PharCompatibleAssetManager extends CAssetManager
{
protected $_published = array();
public function publish($path,$hashByName=false,$level=-1,$forceCopy=null)
{
if($forceCopy===null)
$forceCopy=$this->forceCopy;
if($forceCopy && $this->linkAssets)
throw new CException(Yii::t('yii','The "forceCopy" and "linkAssets" cannot be both true.'));
if(isset($this->_published[$path]))
return $this->_published[$path];
$isPhar = strncmp('phar://', $path, 7) === 0;
$src = $isPhar ? $path : realpath($path);
if ($isPhar && $this->linkAssets)
{
throw new CException(
Yii::t(
'yii',
'The asset "{asset}" cannot be published using symlink, because the file resides in a phar.',
array('{asset}' => $path)
)
);
}
if ($src !== false || $isPhar)
{
$dir=$this->generatePath($src,$hashByName);
$dstDir=$this->getBasePath().DIRECTORY_SEPARATOR.$dir;
if(is_file($src))
{
$fileName=basename($src);
$dstFile=$dstDir.DIRECTORY_SEPARATOR.$fileName;
if(!is_dir($dstDir))
{
mkdir($dstDir,$this->newDirMode,true);
@chmod($dstDir,$this->newDirMode);
}
if($this->linkAssets && !is_file($dstFile)) symlink($src,$dstFile);
elseif(@filemtime($dstFile)<@filemtime($src))
{
copy($src,$dstFile);
@chmod($dstFile,$this->newFileMode);
}
return $this->_published[$path]=$this->getBaseUrl()."/$dir/$fileName";
}
elseif(is_dir($src))
{
if($this->linkAssets && !is_dir($dstDir))
{
symlink($src,$dstDir);
}
elseif(!is_dir($dstDir) || $forceCopy)
{
CFileHelper::copyDirectory($src,$dstDir,array(
'exclude'=>$this->excludeFiles,
'level'=>$level,
'newDirMode'=>$this->newDirMode,
'newFileMode'=>$this->newFileMode,
));
}
return $this->_published[$path]=$this->getBaseUrl().'/'.$dir;
}
}
throw new CException(Yii::t('yii','The asset "{asset}" to be published does not exist.',
array('{asset}'=>$path)));
}
}
I'm really, really sorry that you had to read this traditionally horrible Yii code, but that was inevitable... :(
Main change was starting from the $isPhar = strncmp('phar://', $path, 7) === 0; part.
Now just link this asset manager instead of built-in one:
config/main.php:
'components' => array(
'assetManager' => array(
'class' => 'your.alias.path.to.PharCompatibleAssetManager',
),
)
Now your Yii web application uses phar archive instead of huge pile of separate files. They say that this increases performance, but my personal reasons was just to reduce the number of files inside the repository.
Today's guess is this: you have a test harness which utilizes the database, and it has enough test cases in it for full test run to be so slow you cringe at the very thought of launching it.
We discuss a lifehack-style solution to this problem: putting the DBMS which will be used by our test harness completely on a RAM disk, so it'll operate from much faster memory than the hard drive (even faster than from SSD).
Main issue is this: as you probably need only a test datasets at ramdisk, and only for a period of running test suite, you will need separate DBMS instances to work on ramdisk, not the ones already installed on your system.
Here we'll look at how to prepare MySQL and MongoDB instances to work on ramdisk.
In the end you'll get the special preparation script which you should launch before your tests. After this, your test suite will run with the isolated MySQL and MongoDB instances on top of ramdisk.
If your test suite has large quantities of integration tests using databases, this will greatly increase the speed of test run. It is reported in one particular case that the drop in run time was from 1:30 to 18 seconds, 5 times faster.
You should have a *nix system as a MySQL Sandbox (see below) works only there. OSX probably will do, too.
This system should have some bash-like shell (obviously) and Perl installed.
Kernel should have tmpfs support.
Your nonprivileged user should be able to mount filesystems, or you'll need to hack the script to introduce sudo at mount step (assuming your user can sudo).
For isolated MySQL instance you need the MySQL distirbutive downloaded from the website. For isolated MongoDB instance you need the MongoDB distirbutive downloaded from the website. Note, however, that the whole MongoDB server is contained in just a single binary file ~8MB in size.
Of course as we will work completely in memory you have to be sure that you have enough RAM to store your (presumably test) datasets.
Making ramdisk is very simple with latest Linux:
mount -t tmpfs $RAMDISK_NAME $RAMDISK_DIR
as root.
RAMDISK_NAME is some identifier for mountpoints table.
RAMDISK_DIR is the directory which will be turned into RAM-based filesystem.
After this mount action, anything you put into RAMDISK_DIR will be placed into memory, without interaction with the physical hard drive.
Of course, it means that after unmounting the ramdisk everything which was in it will be lost.
Just unmount the created mount point:
umount $RAMDISK_NAME
as root.
Note that you probably should stop all running services which still use the ramdisk prior to unmounting!
We'll use the MySQL Sandbox project to launch isolated MySQL instances.
For it to work you need the MySQL distirbutive downloaded from the website.
MySQL Sandbox is installed with the following command:
# cpan MySQL::Sandbox
as root, and you'll need to run it as follows:
SANDBOX_HOME="$RAMDISK_DIR" make_sandbox "$MYSQL_PACKAGE" -- \
--sandbox_port="$MYSQL_PORT_DESIRED" --sandbox_directory="$MYSQL_DIRNAME"
It's a one-liner split to two lines for readability.
Note that you need root privileges only to install the MySQL Sandbox application itself, all further communication with it will be done from unprivileged account, most possibly the same under which you launch the test suite.
We need to set the SANDBOX_HOME variable prior to launching the sandbox factory because that's how we control where it'll put the sandboxed MySQL instance. By default it'll use $HOME/sandboxes, which is probably not what you need.
Note that RAMDISK_DIR is the same directory that the one we prepared in previous step.
MYSQL_PACKAGE is a full path to the MySQL distirbutive package downloaded from website.
Please note that MySQL Sandbox will unpack it to the same directory and will essentially use this unpacked contents to launch the sandboxed MySQL.
So, probably, you'll need to move the package to ramdisk, too, to increase performance of actually launching and running the MySQL server itself, however, note that unpacked 5.6.0 contents are 1GB in size.
Remember the MYSQL_PORT_DESIRED value you use here, because you'll need to use it to configure your test suite to point at correct MySQL instance.
MYSQL_DIRNAME is of least importance here, because it's just a name of a subfolder under the SANDBOX_HOME in which this particular sandbox will be put.
After make_sandbox ended it's routine you can check that your sandbox is indeed working by running:
"$RAMDISK_DIR/$MYSQL_DIRNAME/use"
You should use the following credentials to connect to sandboxed MySQL:
* host : '127.0.0.1'
* port : $MYSQL_PORT_DESIRED
* username : 'msandbox'
* password : 'msandbox'
Please note that you must use 127.0.0.1 value for host and not a localhost as usual, because of sandbox internal security configuration.
To shutdown the sandboxed MySQL, issue the following command:
"$RAMDISK_DIR/$MYSQL_DIRNAME/stop"
or more forceful
"$RAMDISK_DIR/$MYSQL_DIRNAME/send_kill"
This commands are needed mostly to stop the working daemon; after the unmounting of ramdisk all of sandbox data will be purged out of existence.
MongoDB server is contained in just a single binary file so it'll be a lot more easier compared to MySQL.
You'll need the MongoDB distirbutive downloaded from the website, too. This time unpack it to some directory.
After that, you can launch a separate instance of MongoDB with the following command:
"$MONGODB_BIN" --dbpath="$MONGODB_DIR" \
--pidfilepath="$MONGODB_DIR/mongodb.pid \
--port $MONGODB_PORT_DESIRED \
--fork --logpath="$MONGODB_DIR/mongodb.log"
MONGODB_BIN is a /bin/mongod path preceded by the full path to the unpacked MongoDB distributive.
Here you can even use your system MongoDB package, in case you have it installed.
As a full example, MONGODB_BIN can have a value of ~/systems/mongodb-linux-x86_64-2.4.4/bin/mongod
MONGODB_DIR is a path to directory under RAMDISK_DIR to which this MongoDB instance should put it's files.
For example, it can be just a $RAMDISK_DIR/mongo.
As with MySQL, MONGODB_PORT_DESIRED is a crucial parameter to specify the correct MongoDB instance to connect to.
Remember it as you will need to set it up in your test suite.
By default MongoDB do not enforce any usernames or passwords so you need to just use the hostname and port parameters.
* host : 'localhost'
* port : $MONGODB_PORT_DESIRED
For example, for PHP Mongo extension, you get a connection to this instance as follows:
$connection = new MongoClient("mongodb://localhost:$MONGODB_PORT_DESIRED");
As you provided the --pidfilepath commandline argument when launching the MongoDB server, the following command should do the trick:
cat "$MONGODB_DIR/mongodb.pid" | xargs kill ; rm "$MONGODB_DIR/mongob.pid"
Essentially we are feeding the kill command with the contents of pidfile and removing it afterwards.
There is a GitHub repository with the example scripts nicely laid out along with the comments.
There are three scripts:
db_sandbox_properties.sh: this is the all variable parameters you need to properly setup the sandboxes.db_sandbox_start.sh: this script you run before your test suite.
It was updated with the command to copy the tables schema from source MySQL instance to sandbox MySQL instance, so, if you have an accessible up-to-date MySQL instance with the schema for your tests, this script will copy schema to sandbox so you will have a DB ready to accept test cases.
NOTE that you will need the sudo rights for your unprivileged user to successfully mount the ramdisk.
If you do not have them, you can hack the mount command in any way you see sufficient to successfully mount the ramdisk.
db_sandbox_stop.sh: this script you run when you don't need the sandbox anymore. It'll stop both MySQL and MongoDB and unmount the ramdisk (note that you'll need the sudo rights for this, too).