Thank you! I can't believe how hard it is to figure out testing in Laravel.

For unit/integration tests I'm very happy with Codeception.

However there are a number of things that screw up using codeception:

Without the Laravel5 module, you cannot use namespaced classes/facades in your application code

If you use the Laravel5 module you cannot use it with the acceptance testing suite, even if you use that little snippet in the Laravel5 module docs.

As far as I can tell with the Laravel5 module, you cannot authenticate as a user.

In theory you should be able to use the PHP league faker library, but in fact you can't because it's facade based and codeception doesn't play well with that. Even the documentation on using the faker library admits this.

Using Laravel's built in testing suite is relies on the phpunit.xml file for configs not an easy yml loading a .env.testing

Laravel's testing documentation is not nearly as good as codeceptions. I wish I could just use codeception and be able to test all aspects.

Using AWS as my host, occasionally the production server is unable to write logs to the storage/logs/* and causes my application to white-screen. I don't sudo when git pull'ing and my storage owner/group/permissions are as follows:

drwxrwxr-x 6 apache apache

There doesn't seem to be any sort of pattern as to when the white-screen'ing happens. It's without any sort of admin pulling or messing with files, it happens "naturally". Is there a small daemon or something that could be changing permissions?

I'm looking to dive into a Flux like implementation to help with React complexity. I'm curious if anyone else in the Laravel world is doing something similar, especially since I rely on Elixir to compile all of my React.

A few questions:

Can I use native gulp in the same gulpfile that Exilir uses without conflict?

Is there any Flux like implementations that work "out of the box" with Exilir's browserify workflow?

After doing Laravel for awhile it's really fun to move into the frontend, but geeze there are so many options and opinions! Too bad there's not a resource like laracasts for react like implementations.

All of the other Facade mocks work great, but this Config one in particular is acting as if it's not in test mode. I'll show you what I mean:
class Stub
{
public function someAction()
{
return $someConfig = config('appName.some.configuration');
// works great, I can set and get all kinds of configurations from /config/app/appName.php
}
}
However when I try to test my fancy Stub class:
class StubTest extends \Codeception\TestCase\Test
{
protected function _before()
{
$this->stub = new Stub();
}

}
You would expect this to be a passing test. However when the Config is being mocked, it begins to ask for other configuration variables that this test shouldn't care about:
[Mockery\Exception\NoMatchingExpectationException]
No matching handler found for Mockery_2_Illuminate_Config_Repository::offsetGet("database.default"). Either the method was unexpected or its arguments matched no expected argument list for this method
If you start to mock the configuration for database.default, it'll move onto your cache configuration. On top of that it asks for real values. It's a waste of time and not sustainable.
Has anyone else run into this issue when mocking the Config facade?

I'd much rather use the Blade Form, because it's so much cleaner of an implementation. However if I can't use the default value, I'm kind of screwed because a user has no sectionPrototypes when they first create an account.

It recommends a few tools for automating deployment like ansible and fabric. Do any of you use tools like these? I kind of understand the value. You can deploy new code with schema changes and whatnot without having to break your team's instances.

I can't believe I've been using AJAX for all this time and not set up caching on the backend. This would make time sensitive calls extremely fast, like chat for example.

I too am trying to transition one of our UX heavy pages into an Angular app. It just makes sense to have 1 API that iOS/Android/Frontend uses. Also Angular is amazing when it comes to frontend manipulation.

I'm still curious on how you are leveraging the Cache facade though. Do you have some kind of Chain of Responsibility method that figures out if the result is in cache already, if not then query the db?

Yup Laravel 5 is definitely still unstable. But I'm excited for the new Symfony-ish Form Requests.

One of the differences I'm aware of is the removal of the modals directory. To prepare, I suggest learning about PSR-4 autoloading and moving your model logic into a separate src or in Laravel 5 terms, a app folder.

I'm excited because my application is getting to a point where I can charge customers ( awesome) and this means I get to implement a payment service.

I've already installed Stripe and Cashier as my payment and payment processing services. However I have some subscription rules that are somewhat complex. Here's just a small sample of the rules:

A basic plan has 1 Artist and 10 Shows.
After 10 Shows a $Y amount is charged per Show.

A premium plan has up to 5 Artists and 50 Shows.
After 50 Shows a $Y amount it charged per Show.

I will soon have to apply different rules to different user account types.
What are some methods that you all use to verify that a User can perform certain actions? I'm thinking that this calls for a separate service altogether that's called on certain routes and before actions are performed:

SubscriptionChecker::check($action, $user);

Will be responsible for simply checking if the user's account is able to perform the action.

I did some more searching around, this trick is to leverage polymorphic relationships to "compose" your super class. I love it, very easy to make models superclasses later without a bunch of migrations

I have an application that's getting pretty large. I've noticed that one of our tables "locations" is doing the job of several tables. There are many sub-locations that inherit the same properties, but are different enough that they justify their own table (because of additional fields).
I've also noticed I need to apply this pattern to another part of my application so it's definitely a pattern worth learning how to do and implementing.
Problem is I don't see any documentation on this type of Eloquent feature. Is single and multiple class inheritance out of scope of the Eloquent ORM? I'm working on implementing the repository pattern, so I could possibly switch out to doctrine which I know supports this. I'd just rather stick with Eloquent because it's so easy to use. Has anyone else encountered this problem?

Exactly what I was asking. I'm not a frontend minded person, but I can see that normal Blade + jQuery is functional but it's just not as scalable as I thought. I'm definitely going to build a RESTful API that both the web and mobile sides of the application.

So many advantages:

1) complete separation of view from the application

2) Don't have to duplicate code for mobile or web, the API expects JSON endpoints as GETers and POSTers.

3) Use a tool that has a separate goal than that of Laravel, but you can still leverage it for your application.

@bashy that's definitely helpful. There are 3 main use cases that I run into over and over:

1) A form as a type of field that can be added 0, 1, or many times (your typical 'add expense' or 'add contact' field)
2) A field that shows/hides based on certain conditions (like a checkbox causing another part of the form to show)
3) A search bar in the form that makes an AJAX call to a local API endpoint that provides results to the form for a user to selection. That selection is used on the form.

To add to the complexity, many of these forms are on modals. Modals are also a great UX tool, but if you iterate over a collection in your view then you have to generate a corresponding modal with each instance.

Blade is great. It makes reading and writing static forms a cinch. However when it comes to dynamic forms there's not a clear answer. I've been using jQuery functions to add/delete/modify fields based on user events. However this is resulting in a lot of copy pasta which is not yummy and I feel like this is a common enough problem there is a JS library out there specifically for forms.

Is this out of scope for Blade? Is this what frontend JS frameworks attempt to answer?