Disqus - Friends of ericbarnes

Re: Running out of Post IDs

fideloper — Fri, 01 Apr 2011 12:04:34 -0000

First thought: Will never work in IE
Second thought: April fools.

Re: hybrid grid

fideloper — Wed, 18 Apr 2012 12:07:33 -0000

Everyone forgets poor French Fries.

Re: Episode 3: The EE revolt of 2012 and why you should unit-test your shit - PHP Town Hall

fideloper — Thu, 27 Dec 2012 11:20:54 -0000

I complete agree with Chris - Composer + Packagist is a turning point in PHP.

Re: Ubuntu: Install LAMP with PHP 5.4

fideloper — Sun, 06 Jan 2013 10:08:44 -0000

What version of Ubuntu are you using? That's looking for Quantal distro, which doesn't appear to be in that repo. I have this working under precise LTS - http://ppa.launchpad.net/on...

Some googling reveals that there might be an issue with 5.4 and 12.10 Quantal, perhaps that needs some time to work itself out.

Re: Women Need to Realize Work Isn't School

fideloper — Fri, 11 Jan 2013 10:50:24 -0000

I think "disruptive" should be replaced with "assertive" - Unless speaking in terms of "disrupting the normal work flow/convention."

I can understand women needing to take special care in the presentation of themselves - Seeing how easily they can be dismissed when they approach "assertiveness". It's a sad state of affairs.

However, this article seems to be implicitly stating that women approach authority (Teachers, bosses) differently then men. Is that the intent?

Re: Testable and Maintainable code with Dependency Injection and Containers

fideloper — Sat, 26 Jan 2013 16:25:02 -0000

Thanks! Appreciate it!

I've been using Laravel a lot, and have found writing about the concepts behind it very useful to learn the framework itself.

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Tue, 29 Jan 2013 18:06:59 -0000

Thanks, appreciate it!

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Tue, 29 Jan 2013 18:08:06 -0000

:D - (Keeping you mind!)

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Tue, 29 Jan 2013 19:41:56 -0000

Oh, good call - that's an absolute path in the form code instead of a relative one. Those using a localhost to do something like http://localhost/myproject/public will need to adjust that.

Thanks

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Fri, 01 Feb 2013 15:28:35 -0000

Hello - Thanks!

I have seen this issue crop up for some in IRC chat. It could be an issue with PHP and Apache. http://stackoverflow.com/qu....

Note that the --env=local flag is specifically looking for credentials in the "local" environment. If it's not finding them in app/config/local/database.php, it'll fall back to what it finds in app/config/database.php. (I'm not sure if this issue is environment related, but I wanted to point that out).

Hope that helps!

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Mon, 04 Feb 2013 09:42:23 -0000

I'm glad it's helpful! I'm posting as I learn, to help me remember everything :D

Re: Laravel 4: A Start at a RESTful API (Updated)

fideloper — Tue, 05 Feb 2013 12:32:28 -0000

Awesome, I'll check on that.
Thanks

Re: Laravel 4: A Start at a RESTful API (Updated)

fideloper — Tue, 05 Feb 2013 14:33:50 -0000

Indeed! There are many, many aspects to consider. Most frameworks are working towards standard web-work and so API's are more of an add-on, rather than a focus.

Perhaps in the case where your API will be fairly robust, a truly smaller framework would help more than hinder (Silex comes to mind in the PHP world).

It would be great to see a framework specifically for API's. (NodeJS has a few, such as Restify)

Laravel 4 does give you more potential control, both at error handling and controller/routing logic. With its use of Composer and packages you could *conceivably* use what you want and "overwrite" what you don't like (For instance, standard controller logic to handle not-found methods).

Sidenote: Do you blog any of your RESTful API work? I'd love to read up on the detail work, such as normalizing http 1.0 vs 1.1, etc.

Re: Laravel 4: A Start at a RESTful API (Updated)

fideloper — Wed, 06 Feb 2013 09:03:09 -0000

You would likely need a browser plugin to help you do this. Keep in mind I used basic auth as an example. While some popular API's have used it, most use oAuth (Which is a better, but more complex, solution)

Re: Laravel 4: A Start at a RESTful API (Updated)

fideloper — Wed, 06 Feb 2013 09:04:28 -0000

Looks awesome!

Re: Laravel 4: A Start at a RESTful API (Updated)

fideloper — Wed, 06 Feb 2013 09:07:09 -0000

Possibly, but composer.phar can be in any location, not necessary inside the project root.

For instance, I ALWAYS put it inside of a 'bin' folder, so on my computer, I actually run:
$ php bin/composer.phar dump-autoload.

Even better, tho, I believe Laravel is making some strives towards doing this automatically, or setting up autoloading in a way that it's not necessary.

Re: Vagrant: What, Why, and How

fideloper — Sat, 09 Feb 2013 19:28:52 -0000

Hello!

I believe the real benefit is time. Similar to unit-testing, it takes some up-front work for a long-term cost savings.

For instance, your example of using "apt-get install new-server ... and then configure it" - That configuration takes a lot of time (speaking from experience).

To demonstrate: I keep a markdown file for all servers I have built for certain projects. Here's a run down of what a typical web-head takes to build (after some hours of making sure of configurations and install packages are what you wanted) - This is an incomplete example of a web server (vs a database or other service):

Basic Server Installs:
$ apt-get update
$ apt-get install -y python-software-properties
$ add-apt-repository ppa:ondrej/php5
$ apt-get update
$ apt-get install -y php5
$ apt-get install -y apache2
$ apt-get install -y libapache2-mod-php5
$ apt-get install -y mysql-server
$ apt-get install -y php5-mysql
$ pecl install mongo
$ echo "extension=mongo.so" | tee /etc/php5/conf.d/mongo.ini
$ apt-get install -y php5-gd
$ apt-get install -y curl php5-curl

Other tasks:

* Timezone and time-syncronization
* User administration (You're not allowing direct log-in into your production machine as root, right? Also: Apache has own user/group. Code deployment user and group management, etc etc)
* Apache performance tweaks and general tuning
* php error reporting and other performance tweaks (since this is a LAMP example)
* Virtual Host setup
* Logging, including logrotate and log backup. Distributed environment = log aggregation concerns (more servers!)
* Firewall setup
* Server Monitoring (New Relic, home-grown or other)

So, as you can see, even arguably simple server setups can demand complicated and thoughtful setup.

The value of chef, puppet, and ultimately vagrant is in automating tasks that take precious **time** and are prone to error.

Time saved in:
* Deployment, including adding new servers
* Development - having same/similar server to dev in as production means less nasty surprises.

* Consistency - errors due to mismatching versons goes away

I hope that helps show just how much work can go into starting up a production server and how Vagrant fits into using chef/puppet to save you time and headache.

Re: ETag’s and Conditional GET’s in Laravel 4

fideloper — Wed, 13 Feb 2013 16:57:58 -0000

I haven't yet, but it's certainly on my To Do list!

Re: Laravel 4 Error Handling

fideloper — Fri, 15 Feb 2013 11:37:53 -0000

Thanks!

Laravel actually doesn't give you a clear place to put your own library for things like business logic. Presumably you could add it all into your "Models" directory, but I don't like that approach.

I recommend having a external library for your business logic, that would be a good place to put custom Exceptions.

I typically set up my own "lib" directory for business logic type libraries. I only keep Eloquent or simliar classes in L4's "models" directory.

See this: http://fideloper.com/post/4... for an example of what I mean, and how to accomplish that.

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Tue, 05 Mar 2013 16:47:11 -0000

I see a few people up-voted this, so I'd like to response.

It's accurate and true, this article gives little explanation.

My intent was to give a working quick-start guide. I most definitely assume some knowledge, and I didn't spell that out.

My intended audience is generally one that knows the framework a bit, and one that's interesting in doing more advanced things with it. This might be more obvious with my other Laravel-related posts.

I actually use this article a lot.

For instance, when I want to start a new build up and get going quickly , I can copy and paste quite a few things here and have it work quickly.

I wasn't out to teach the basics of Laravel setup - I apologize for making that unclear.

That being said, I'm not going to write out the basics of getting started - My intended audience is for more medium to advanced users in both PHP/coding and Laravel.

Thanks for reading in any case!

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Tue, 05 Mar 2013 16:48:46 -0000

Hi! That's certainly frustrating. There quite a few thing that could go wrong, and those things can vary from your environment to updates in Laravel causing this article to not be accurate any longer (And any mistakes I've made - altho I have copied/pasted and used this process many times).

Can you let me know the original errors you were getting? Perhaps I can help.

Re: Error Handling with Content Negotiation

fideloper — Fri, 08 Mar 2013 16:27:38 -0000

Yes! That's something I've been meaning to get to - I'd like to figure out the best way to handle that gracefully.

Re: Ubuntu in Production: Install Sphinx Search, with PHP |Fideloper

fideloper — Wed, 13 Mar 2013 13:52:31 -0000

Awesome, thanks!

Are you aware of any pitfalls in installing php5-dev on an production machine?

Re: ETag’s and Conditional GET’s in Laravel 4

fideloper — Tue, 19 Mar 2013 08:46:21 -0000

Great point! Thanks, I'll update that.

Re: Laravel 4 Uber-Quick-Start (With auth!) Guide

fideloper — Tue, 19 Mar 2013 17:59:33 -0000

Ah, I've run into that issue! That's something with how Taylor @ Laravel updates - sometimes composer repos or the "skeleton" app are out of sync with each other. (While they are developing new stuff or making changes in Beta).