On my desktop PC I’m running both Windows and Ubuntu. For myself and my family I’ve a 1Password Families account. While the macOS and (the just refreshed) Windows app are working like a charm, Linux is left behind with an old guide explaining how to run the (outdated) Windows client in Wine. Besides the use of old software, that client doesn’t support Teams or Families. Luckily for the Linux users, the Teams/Family plans have a nice webinterface that works pretty well, the only thing I really miss are the browser extensions.
The API we are building consists of many different, and mostly independent (decoupled), layers (at least 7 before reaching the database). One of the only things that is required by all the layers is the data that is being retrieved or sent to the app. Note: this article was originally published on the Exonet Techblog and is written from that perspective. That data comes in as a JSON object (which will be converted to a PHP array), is parsed and written to the SQL database.
To update XDebug to 2.3.2 (tested) on a Homestead 0.2.5 (tested) Vagrant box, you can use the following commands: cd ~ wget http://xdebug.org/files/xdebug-2.3.2.tgz tar -xvzf xdebug-2.3.2.tgz cd xdebug-2.3.2 phpize ./configure make cp modules/xdebug.so /usr/lib/php5/20131226 sudo cp modules/xdebug.so /usr/lib/php5/20131226 sudo nano /etc/php5/cli/php.ini cd /etc/php5/fpm/conf.d/ sudo nano 20-xdebug.ini sudo service php5-fpm restart Probably this will also work with different versions of XDebug and/or Homestead. Just replace the version number of XDebug to the one you want to use.
On the internet there is a lot of discussion about testing your code for a reasonable 100%. There are some who says that it is a waste of your time, others say that every single line should be tested. Personally I believe that aiming for a 100% coverage is a good goal to achieve. In my job we’ve decided for our project to go for a 100% coverage with unit tests.