eclipxe13

[eclipxe13]

Still true? How true?

[eclipxe13]

Using answers from SO is not always the best to do

[eclipxe13]

It’s going into production tomorrow

[eclipxe13]

Can’t take anything seriously on this day

[eclipxe13]

“Oh, it’ll be done in about a sprint”

[eclipxe13]

Moments after cloning someone’s github/gitlab repo for the first time…

[eclipxe13]

Linux sysadmin and devops engineer investigate your Linux system and containers including K8s cluster for security and other issues :P

[eclipxe13]

Life of the open source maintainer https://www.tiktok.com/@shmemmmy/video/6888823361405799686

[eclipxe13]

Al fin, hice my GitHub Profile Readme! https://github.com/eclipxe13

[eclipxe13]

Desmitificando el testeo (PHP)

En el canal de Discord de PHPeros hice una plática donde toco algunos mitos y mentiras del testing... además de proponer una definición por demás burda y reductiva de lo que es “testear”, con el fin de aclarar que testear es para todos y no solo para los especialistas ni expertos...

[eclipxe13]

Buen dia, buscando como validar un XML ante el SAT di con tu apartado y librerias, tengo que realizar uas validaciones de facturas que recibo, ante u PAC, pero supe como usarla, me pudieras apoyar en guiarme? ... tienes skype, telegram? ... mi nombre es Ramiro Flores de Monterrey

Hola Ramiro, lo lamento, no había visto tu pregunta.

Si quieres me puedes contactar en eclipxe13@gmail.com o bien en el canal de Discord de la comunidad de PhpCfdi: https://discord.gg/aFGYXvX

[eclipxe13]

Building PHP-7.2.0alpha1

I’m following this instructions to build #php version #php-7.2.0alpha1 from the greatest SaraMG... any comments are appreciated on twitter

# get and run a debian:unstable instance docker pull debian:unstable docker run -ti debian:unstable /bin/bash

# install packages (not sure if all dependences are required, I just take it from debian/control) apt update apt install wget apache2-dev autoconf automake libtool default-libmysqlclient-dev firebird-dev freetds-dev libapparmor-dev libapr1-dev libbz2-dev libc-client-dev libcurl4-openssl-dev libdb-dev libedit-dev libenchant-dev libevent-dev libexpat1-dev libfreetype6-dev libgcrypt11-dev libgd2-dev libglib2.0-dev libgmp3-dev libicu-dev libjpeg-dev libkrb5-dev libldap2-dev libmagic-dev libmcrypt-dev libmhash-dev libonig-dev libpam0g-dev libpcre3-dev libpng-dev libpq-dev libpspell-dev libqdbm-dev librecode-dev libsasl2-dev libsnmp-dev libsqlite3-dev libssl-dev libtidy-dev libwebp-dev libwrap0-dev libxml2-dev libxmlrpc-epi-dev libxmltok1-dev libxslt1-dev libzip-dev unixodbc-dev zlib1g-dev apt clean

# saramg source code wget https://downloads.php.net/~pollita/php-7.2.0alpha1.tar.bz2 tar -jxf php-7.2.0alpha1.tar.bz2 cd php-7.2.0alpha1

# do this or configure will fail with curl ln -s /usr/include/x86_64-linux-gnu/curl/ /usr/include/

# taken from https://devzone.zend.com/downloads/buildphp.sh without # --enable-gd-native-ttf --with-mcrypt --with-pdo-sqlite3 ./configure --enable-bcmath --enable-calendar --enable-cli --enable-exif --enable-ftp --enable-gd-jis-conv --enable-intl --enable-mbstring --enable-pcntl --enable-shmop --enable-soap --enable-sigchild --enable-sockets --enable-sysvmsg --enable-sysvsem --enable-sysvshm --enable-wddx --enable-zip --with-bz2 --with-curl --with-gd --with-kerberos --with-libedit --with-libxml-dir --with-mhash --with-mysqli --with-openssl --with-pcre-regex --with-pdo-mysql --with-readline --with-system-ciphers --with-xmlrpc --with-xsl --with-zlib

# build make

# make test make test

# Do not forget to share your test results!

[eclipxe13]

Scrutinizer-CI for PHP

I just did not understand why use Travis-CI + Scrutinizer-CI + Coveralls + SensioLabs Insight. I had some PHP Libraries as free software and I had been using these tools from the first time I start with continuous integration, but why?

I just repeat what others did.

Let’s see how this tools are used in common PHP Libraries:

Travis CI: Build process (runs PHP Code tools like parallel-lint, php-cs-fixer, phpcs, phpunit, phpcpd) If one of this tools report an error then the build process fail. As Travis CI perform the phpunit tests, it can be used to generate the code coverage and it can be posted to other tools like Scrutinizer and Coveralls

Scrutinizer CI: Perform code analysis, it can see more than you can see with normal tools used before or your IDE. It receives the code coverage created before.

Coveralls: Also takes the code coverage and show it. It is an specialized tool but is not very nice, maybe Codecov can make it better.

SensioLabs Insight: Code analysis tool, it does only this job but it does it very well. It does not perform other tasks like the build process.

Why all these tools? Scrutinizer can perform all of it.

Build: You can build the application and run all the tools needed. You can have mongodb, elasticsearch, mysql, postgress and a vary of other tools preinstalled.

Tests: The buid process can make the coverage and you can also include other tools like phpcs, but not too many as it understand its own build output.

Coverage: The code coverage is on the same tool. It also has a chrome plugin to see the code coverage inside github.

Code analysis: Well, maybe its not as good as SensioLabs Insight bit it perform a superb job.

Why you should not use only Scrutinizer CI: Travis CI can build your project in several PHP versions including HHVM, I have not found any way to make this on Scrutinizer CI. So, if the compatibility against several versions of PHP is an issue then Scrutinizer CI is not the right answer.

My advice: Try Scrutinizer-CI as a all-in-one solution, if your project need more utilities then include one by one as growing.

[eclipxe13]

The inspiration for iA Writer.

[eclipxe13]

no more code for today, it's a night of silence

Sometimes I live in denial, and this is what happend to me with Mootools. I didn't want to know that was already dead. It has been dead for a long time, is not flash news, but I did not want to know about it. It is (as long as exists at github) a great javascript framework. Mootools gives javascript a lot of structure and made things so much better than jQuery. Everything a real developer (not a designer) would expect from a framework (http://www.jqueryvsmootools.com/). But now is gone. When Developers Lose Interest The Story Of Mootools https://medium.com/the-javascript-collection/7bccfb4f1a39 I'm so sad about recognize that Mootools is dead that I will keep a night of silence (a minute is not enough), and won't say another word about it.

[eclipxe13]

Actualizándome

Pues resulta que cansado de reinventar la rueda me he decidido en mejorar mi desarrollo web. En particular:

Bootstrap 3: Excelente conjunto de CSS + jQuery para implementar interfaces de usuario

jQuery: bueno, en particular lo que me gusta es mootools, pero no tiene la aceptación que tiene jQuery, no ha sido sencillo tratar de ocupar tal pieza de código (échale un ojo a jqueryvsmootools.com) pero me las estoy arreglando

Formularios tradicionales + Ajax: con los plugins de jQuery validator y ajaxForm poder enviar un formulario. si la petición viene por Ajax entonces actulizar sólo la parte de código correspondiente, si no se ejecutó y se envió en forma tradicional entonces mostrar toda la página con la misma información (tal como se vería con Ajax)

PHP Namespaces: Por fin estoy poniendo mi framework en namespaces en lugar de clases globales, le estoy dando por nombre EngineWorks y por el momento no estoy del todo convencido del rendimiento pero la estructura se ve bastante bien

Implementando mod_rewrite y el patrón de Controlador + Acción (no, no es MVC, es simplemente una buena agrupación de la ejecución

Modelado de datos: Clases para hacer CRUD

Y bueno, todo esto lo estoy experimentando con un proyecto nuevo llamado BuzonCFDI con licencia GPL, LGPL o MIT (por definir) para poder recibir comprobantes fiscales digitales por internet para una empresa o un grupo de empresas.

Ya les contaré de cómo va todo!