If you are developing some application that writes a lot of logs use
logrotate to keep them short and don’t allow them to reach gigabytes.
I’m developing in Symfony framework on daily basis. And on the development environment, it creates lots of logs. Every request is logged, every command is logged, every event subscriber is logged. And if you’re using some older version deprecations are also logged. On my computer, every refresh in browser creates over 1 MB of logs! My friend gets almost 10 MB…
My new addition is the Casey Neistat vlog on youtube. He is so damn positive person and his videos are so cool I literally spend hours watching them. And it’s no waste of time (well it’s way better than watching tv for sure 😉).
Check it out yourself 👉 https://www.youtube.com/user/caseyneistat
From some time on I was thinking about some completely different format of posts, the short one. I even had a name for it –
shorties. I have pretty many thoughts on my mind that I’d like to share with you, but they’re too short to make it a proper post. So the idea died.
I changed the application from one class to three with separated responsibilities, wrote some tests and use Travis-CI for continuous integration. Version 0.2.1 is available here.
Since the last post, the application changed a lot. When I had a little time I sat down and just coded. Changes are too small to wrote about separately, but now there are enough of them to do some summary 🙂
I like Fallout video games series. Well, the old ones – the last one I played was Fallout Tactics. But let’s focus on Fallout 2.
The game starts in a temple, and you are the Chosen One. Well, maybe. You have several challenges to overcome: giant ants, scorpions and, of course, the final guardian. If you fail, you will die.
But it’s a video game, of course, you survive and you defeat the guard. Then you will get harder and harder works to do, with the ultimate goal – finding GECK, Garden of Eden Creation Kit, a very powerful device capable of repairing the earth after a nuclear holocaust.