Posts about technology and arts.
This week I had to write my first custom command for Laravel 4. In Nestor-QA, Peter and I thought it would be useful to have the database schema being automatically generated with SchemaSpy in our Jenkins box.
Thanks to Artisan this task is much simpler than I thought.
The following command creates the
php artisan command:make SchemaSpyCommand --command=schemaspy
This will create the file
app/commands/SchemaSpyCommand.php. And all I had to do was
just fill in the options and write the exec command as the Laravel 4 docs explain.
$this->info('Creating SchemaSpy'); $jar = $this->option("jar"); $dbtype = $this->option("dbtype"); $output = $this->option("output"); $commandLine = sprintf("java -jar %s -u none -t %s -o %s", $jar, $dbtype, $output); $this->info(sprintf("Command line: [%s]", $commandLine)); exec($commandLine);
That’s how my final command looks. Now the final step is integrate it into the application by adding the line below to
And that’s it, running
php artisan schemaspy --jar=/opt/schemaspy/schemaSpy_5.0.0.jar
creates the database schema docs in the
Check this gist for the final code.
I recently installed TestLink 1.9.8 and noticed that the menus and some other parts
of the UI we missing. Looking at
/var/log/testlink/userlog1.log (the location
may change depending on your settings) I realized that there was something wrong
with my PHP installation. There were log messages like the below.
include_once(ADORecordSet_ext_empty.class.php): failed to open stream: No such file or directory - in /home/kinow/php/workspace/testlink-1.9.8/lib/functions/common.php - Line 92 [13/Sep/18 12:51:09][WARNING][2o0h173pdgg5fjqh1pukr83og2][GUI] E_WARNING include_once(): Failed opening 'ADORecordSet_ext_empty.class.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear:.:/home/kinow/php/workspace/testlink-1.9.8/lib/functions/:/home/kinow/php/workspace/testlink-1.9.8/lib/issuet ...
I found a post in a forum (but unfortunately I forgot to save the link) that suggested
these ADORecordSet were being caused by the module php5-adodb. Removing the module, and
cleaning the templates cache directory (
fixed the issue for me.
Hope that helps. Happy testing!
The Apache Way is the philosophy behind Apache Software Foundation and is shared by all of its projects. It is composed by a set of principles:
I have been part of Apache Commons for a while, and haven’t really contributed much yet. Maybe because I had lots of projects related to TupiLabs as well as my own wedding this year. But I can assure that respectful, honest, technical-based interaction is quite right (not to discredit the other items, of course).
Even though there are critics of the Apache Way (1, 2, 3), it still stands as an important pillar for the Apache Software Foundation, and its principles help to create stable and production ready software, such as Apache Hadoop, Apache Httpd, Apache Commons Lang, among others.
I have just returned from honey moon, ready to start writing code again, but first I had to read all the unread messages in my inbox. Some were e-mails from Apache mailing lists. One of these e-mails had Phil Steitz comments on a post by Daniel Wu.
Instead of publishing his performance benchmark results of Apache Commons Pool, Daniel posted his code to the commons-dev mailing list. Phil Steitz, one of Apache Commons Pool committers replied with questions and a few points that Daniel could use to enrich his benchmark tests.
This kind of behavior happens a lot within Apache (at least in the mailing lists that I follow), and it produces a lot of benefits for different parts.
I keep loving the Apache Way and the resulting community and code around it. There are always lots of things to learn, the Open Source projects communities are healthy and you will always find people willing to share their experience and time teaching you.
♥ Open Source
Actually, in the dashboard, the graph was missing, being displayed as a gray box. Enabling the web inspector in Google Chrome I got the graph URL. Opening the link in a new tab gave me the exception message: too many SQL variables (1).
After some research, I found out this was a bug in SQLite. After trying to hack the code, and being concerned about using a patched version of Graphite and having to update it later, I decided to switch database.
But to avoid losing the graphs, users and other settings, including the events, I migrated the SQLite database to a MySQL server. This MySQL server was already installed in the server machine, since this machine hosted a Zabbix server too.
Here are the steps required to migrate your database from SQLite to MySQL (2).
|sqlite3 graphite.db .dump||sqlite3-to-mysql.py||mysql -uroot -pyourpass graphite|
After tail’ing the Graphite webapp log file,
tail f- storage/log/webapp/error.log
I noticed the Python MySQLdb wasn’t installed.
ImproperlyConfigured: Error loading MySQLdb module: No module named MySQLdb
My server was an Ubuntu 13.04, so I installed the module simply with the following command.
apt-get install python-mysqldb
Hope that helps!
1 You may have to enable *DEBUG* in your Django settings for seeing the exception in your browser
2 Zabbix needed some minor tweaks in order to use [MariaDB](https://mariadb.org/), but probably you can give it a try too
I had previously installed another test box, so I decided to take a deeper look at the settings, write a puppet manifest and prepare this new box to become a production server. However, after browsing the webapp, all graphs were broken.
After googling a while, reading forums and bugs, I decided to open the $GRAPHITE_HOME/webapp/graphite/render/views.py, adding log.rendering(...) statements (not the most elegant solution, I know).
By following the program workflow I found out it was entering a block after checking if it should remotely render the image. This feature is turned on/off by REMOTE_RENDERING = True/False, in local_settings.py.
After setting this to False the problem was solved.