Tag Archives: Ubuntu

Laravel Application Logs and Logrotate

Depending on usage, errors, and what you’ve chosen to log, the Laravel application log(s) can really grow after a while.  With Laravel 3 and initially with Laravel 4, new log files were created every day by default, which kept them small and easy to search, but now Laravel 4 defaults to a single log file (which I prefer).

Continue reading

Upgrading to PHP 5.4 on Ubuntu 12.04 LTS

File this under “mostly for my own benefit”, since I often forget how I accomplished something when I need to go back and do it again.

As of March 15, 2013, PHP 5.3.x will only receive “critical fixes” and people are encouraged to upgrade to 5.4 or 5.5. And sometime in 2014, 5.3.x will not longer be supported at all. All of the Linux servers I’m working on now are running Ubuntu 12.04 LTS, which currently provides PHP 5.3.10, so I decided to look into what it takes to update to 5.4.x on these boxes.

It’s simple…
Continue reading

Thoughts on Vagrant

I’ve been making a play to get current and stay current with today’s web dev technologies, trends, etc.

It’s not easy. Things are moving fast and I was a bit behind to begin with.

Some of the tools that developers on the cutting edge are pushing appear to be a little abstract relative to what I’m actually working on right now or to my current workflow. One of these tools is Vagrant. Don’t worry, I do get it. Dev environments should match Prod and Vagrant makes it much easier to accomplish. But as a single developer who doesn’t need new environments that often, do I really want to spend time learning about Vagrant, along with Chef and/or Puppet just to prop up the occasional new environment when my current OS X/MAMP Pro dev environment really hasn’t caused me any problems to date? (actually, I did have an issue with case-sensitivity and class names, but not a big deal.)

Again, my use-case is currently limited (single developer, very few new environments, content with MAMP). And I don’t really want to take the time right now to learn Chef or Puppet. But if I can make it super simple, and considering the prospect of developing an app and packaging it up with a Vagrantfile and including it in a repo – all ready to go (I haven’t really seen this, but it sounds cool), then maybe it’s worth looking into. Plus, I’ll have that peace of mind that my Dev and Prod environments are matched.

So I borrowed some code from a couple of different Vagrant/Laravel 4 Github repos and mashed together my own Vagrantfile/boostrap.sh that is very simple and doesn’t require Puppet or Chef to get something up and running that to run a Laravel app. In addition to installing a LAMP environment, it points the default Apache site to the public folder.

Your web app will be available at http::/localhost:8888 and you can access MySQL via an SSH tunnel using the “vagrant” user.

Posted on Github: https://github.com/rufhausen/super-simple-vagrant-laravel

A Simple Git Deployment setup on Ubuntu Server

After spending a lot of time on trial & error to set up a simple Git web application deployment setup using Ubuntu server, I’m writing this down as a reference for myself and thought it might helpful to others as well. If anyone actually reads this and can comment on:

  • Things I missed
  • Things I did that were stupid
  • Things that were especially stupid

…it will be appreciated.

This is based on Ubuntu 12.04 server and deploying from OS X, though that part shouldn’t matter.

Continue reading

PowerPC, Ubuntu, Java, and Minecraft. It can work.

This post isn’t related to what this blog is supposed to be about, but apparently there are a number of people with old PowerPC Macs like myself who want to get some use out of them by running things like Minecraft servers. My two kids are addicted to playing and they love idea of having their own server.

When the old PowerMac G5 was still running Leopard, we were able to run a server without any issues except that it’s not particularly fast, and it was difficult to find a Java JRE that was current enough for Minecraft that would work on the G5, but we(I) did.

Now that the G5 is running Ubuntu Server 12.04, Java JRE/JDK packages are plentiful, but Minecraft doesn’t like them (openJDK, for instance). I’m here to say that the fix is to install the IBM PPC java packages instead. Huge difference in performance.

Eventually, it looks like PowerPC support will be removed from Minecraft altogether regardless of the java situation, but for now, the old G5 has life.