When I work on my site I start jekyll using the following command line:
I like this because it shows me what I’m working on and regenerates the files as things are updated:
The downside to this is that if I’m quickly switching between proof reading a post and editing a post it gets a little slow waiting 5+ seconds for the page to regenerate (you should try it). I started looking into the documentation for
jekyll serveand there’s an option that allows you to limit how many posts it uses:
This cuts down the time required to see my changes:
That 4 seconds makes a huge difference.
I’m writing this post for two reasons:
- So others can learn from my mistakes
- So I have this documented somewhere other than my laptop
This post is almost completely a copy and paste job of the notes I created while I was building my last project using Symfony.
I do all of my primary development work on a Windows computer that runs several Vagrant VMs. The other day I needed to add an executable to my repo and have it be automatically marked as an executable file on all the servers (this project isn’t running Ansible yet so it’s not an option).
If I was running a fully Linux development environment I could just do the following:
But this doesn’t work because of the way Virtual Boxes virtual folders work. In order to do this I need to run the following in Windows:
Then I can commit the file and it will be marked as executable when it gets
git pulled to the server.
Here are this months links…
Most of my life I’ve been a Warren. When my wife and I got married we decided to take each others names and my last name became Keck-Warren. My assumption was that it would be hard to get the DMV to change my license but then I would be on my way.
But I was wrong. It turns out that it was easier to get some of my socially conservative family members to understand than it was to get some computer systems.
Why This is Stupid
People have crazy names and if you create a barrier that prevents then from signing up because their last name has a space or a hyphen they’ll go somewhere else. It also causes all kinds of information mismatches between sites and systems.
I had to visit a hospital for a couple tests right after I changed my name and their computer systems didn’t accept hyphenated last names. I was shocked that a hospital’s computer system wouldn’t allow the hyphen. We were able to move on through the process by removing the hyphen but the real problem started when they tried to bill my insurance. My insurance had a hyphen in my last name but the hospital didn’t. Because of this mismatch it caused my insurance to reject the claim.
This was strike on against this hospital and I haven’t been back.
Several times over the last couple years I’ve tried to sign up at various websites only to be told that my last name isn’t valid. My first fix is to remove the hyphen and that usually fixes the problem.
What You Can Do To Help
Test your sites signup process with common last name “oddities” things like Keck-warren, O’Connor, “van der Wall”, and McDonald. Test with non-latin names like Авандеев and قذافي. Everything you can do to make sure new users can get in because the rest of us non-alpha character last name people will thank you and you might end up with a few more customers.
As developers it’s super helpful to log information to a file so we can retrieve it later. The problem we run into is that over time those log files can take up a lot of space so it’s important to clean them up. We could do that manually by logging into the server and manually deleting them but that’s time consuming and it would be better if we could just have the server do it automatically.
The other day I tried to install the FOS User Bundle but I received the following error:
In order to solve this problem I had to setup a swap file:
If you attempt to access your application running inside a Vagrant VM using app_dev.php you’ll receive the following error:
You are not allowed to access this file. Check app_dev.php for more information.
If you look into your app_dev.php file you’ll see a line that looks like the following:
The important part is this line:
This line looks at the IP address you’re using to access the system and makes sure it’s referring to the “local” computer. There are a couple options to fix this. This first is that you can just remove this line and then delete the app_dev.php file when you deploy. This could create a potential security problem because if you forget to remove it someone could access it and use the dev tools.
The better option is to add your local computers IP address to the list. To do this we’re going to change the exit function so it outputs you’re IP address.
Now if you try to access the site you’ll get your IP address:
You are not allowed to access this file. Check app_dev.php for more information. Your IP: 192.168.56.1
Then you just need to add your IP to the list:
Aprils links just a few days late.
I was setting up a virtual server that’s using resque to perform background jobs and when I ran into the following error:
After a lot of fighting I learned that Sinatra wasn’t compatible with rack 1.6.x so the only way to fix the problem was to downgrade to a version that worked. After much testing it appears that 1.5.5 was the last version that worked.
subscribe via RSS