Hi, is the Sessions component still working, now with 5.4 version?

I tried to install it, but they never got stored on the right folder. I'm using all components on 5.4.

You can see the current list in the README but I'm encapsulating this here for the purpose of asking for help.

Here's what it takes to "move a component over":

0. Find the correct Issue (see those linked in the comments below) for the given component. Leave a comment in that issue showing you'll be pulling this task.
1. Grab the code for that component from the older branch and put it into the appropriate folder in the newer branch. Or, more likely, it's sitting in the newer branch, just still with the old code and Composer dependencies. Just update it in place.
2. Update the composer.json references to Laravel "~5.5.0"
3. Try to composer install; see if anything breaks and whether you also need to update the versions of any other dependencies, or add or remove any others
4. Once composer install works, spin up the PHP server (php -S localhost:8080) and then visit each route that's defined in that component's index.php (e.g. http://localhost:8080/ for the root of the component you're testing) and test whether everything works as expected
5. If it all works, PR it! If you get stuck, PR where you are with notes about what got stuck.

Need to move from the Laravel 5.1 branch:

• [x] Container
• [x] Database
• [x] Pagination
• [x] Middleware

Need to be finished moving from the Laravel 4.2 branch (imported but needs to be tested and tweaked):

• [ ] Mail
• [x] Queue

Opening this early for discussion/question asking. Trying to work on the artisan component, the main issue at the moment is that composer require illuminate/foundation fails, and the main thing we need is the foundation app.

You can get around this by rewriting chunk of artisan, but I feel like that's against the "spirit" of what this project is trying to accomplish.

Based off your queue branch, but with a few changes. Open to feedback on improving the submission.

Changes:

• I removed the use of configs as I felt that hid the setup of the Queue component rather than showing how to interact with it.
• I had issues getting Beanstalkd to work properly, so I went with Redis.

The workers were a bit challenging. It requires an ExceptionHandler, so I created one as an anonymous class. If there's an easier/better way to create one, let me know.

When running as a daemon, it is expecting an Application as it makes a call to isDownForMaintenance. To solve this I created an "App" and added the method. The daemon also ran fine, but then locked up.

Thank you for Torch! It's been a nice reference. Glad I can contribute in some small way.

Fixed #83

@mattstauffer Hey. Given the routing index.php example in the master branch. I do something like this

 $configPath = __DIR__ . '/../config/';
    
    $array = [
        'site' => require $configPath . 'site.php',
        'db' => require $configPath . 'database.php'
    ];
    
    $config = new Config($array);

    // Create a service container
    $container = new Container;

    $request = Request::capture();
    
    $container->instance('Illuminate\Http\Request', $request);
    $container->instance('config', $config);

After which, routes.php is required into the app.

<?php
    use Illuminate\Routing\Router;

    $router->get('/', function () {
        return $config->get('site.setup');
    });

How could I access the config in here?

Hello. I am running components/view as it is mentioned here https://github.com/mattstauffer/Torch/tree/master/components/view#usage, but when I try adding anonymous component, I get an error.

Updated templates/page.blade.php:

@extends('layout')

@section('content')

    <h1>{{ $title }}</h1>
    <p>{{ $text }}</p>

    <x-alert type="success" message="Good luck!" />

@endsection

The templates/components/alert.blade.php:

@props([
    'type' => 'info',
    'message'
])

<div {{ $attributes->merge(['class' => 'alert alert-' . $type]) }}>
    {{ $message }}
</div>

The error:

Illuminate\Contracts\Container\BindingResolutionException thrown with message 
"Target [Illuminate\Contracts\View\Factory] is not instantiable."

Stacktrace:
#33 Illuminate\Contracts\Container\BindingResolutionException in 
C:\OpenServer\domains\view\vendor\illuminate\container\Container.php:1017
#32 Illuminate\Container\Container:notInstantiable in 
C:\OpenServer\domains\view\vendor\illuminate\container\Container.php:818
#31 Illuminate\Container\Container:build in C:\OpenServer\domains\view\vendor\illuminate\container\Container.php:691
#30 Illuminate\Container\Container:resolve in C:\OpenServer\domains\view\vendor\illuminate\container\Container.php:637
#29 Illuminate\Container\Container:make in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\ComponentTagCompiler.php:221
#28 Illuminate\View\Compilers\ComponentTagCompiler:componentClass in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\ComponentTagCompiler.php:185
#27 Illuminate\View\Compilers\ComponentTagCompiler:componentString in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\ComponentTagCompiler.php:170
#26 Illuminate\View\Compilers\ComponentTagCompiler:Illuminate\View\Compilers\{closure} in [internal]:0
#25 preg_replace_callback in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\ComponentTagCompiler.php:165
#24 Illuminate\View\Compilers\ComponentTagCompiler:compileSelfClosingTags in             
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\ComponentTagCompiler.php:79
#23 Illuminate\View\Compilers\ComponentTagCompiler:compileTags in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\ComponentTagCompiler.php:66
#22 Illuminate\View\Compilers\ComponentTagCompiler:compile in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\BladeCompiler.php:322
#21 Illuminate\View\Compilers\BladeCompiler:compileComponentTags in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\BladeCompiler.php:222
#20 Illuminate\View\Compilers\BladeCompiler:compileString in 
C:\OpenServer\domains\view\vendor\illuminate\view\Compilers\BladeCompiler.php:143
#19 Illuminate\View\Compilers\BladeCompiler:compile in 
C:\OpenServer\domains\view\vendor\illuminate\view\Engines\CompilerEngine.php:51
#18 Illuminate\View\Engines\CompilerEngine:get in C:\OpenServer\domains\view\vendor\illuminate\view\View.php:139
#17 Illuminate\View\View:getContents in C:\OpenServer\domains\view\vendor\illuminate\view\View.php:122
#16 Illuminate\View\View:renderContents in C:\OpenServer\domains\view\vendor\illuminate\view\View.php:91
#15 Illuminate\View\View:render in C:\OpenServer\domains\view\index.php:57
#14 Closure:{closure} in C:\OpenServer\domains\view\vendor\slim\slim\Slim\Handlers\Strategies\RequestResponse.php:40
#13 call_user_func in C:\OpenServer\domains\view\vendor\slim\slim\Slim\Handlers\Strategies\RequestResponse.php:40
#12 Slim\Handlers\Strategies\RequestResponse:__invoke in 
C:\OpenServer\domains\view\vendor\slim\slim\Slim\Route.php:281
#11 Slim\Route:__invoke in C:\OpenServer\domains\view\vendor\slim\slim\Slim\MiddlewareAwareTrait.php:117
#10 Slim\Route:callMiddlewareStack in C:\OpenServer\domains\view\vendor\slim\slim\Slim\Route.php:268
#9 Slim\Route:run in C:\OpenServer\domains\view\vendor\slim\slim\Slim\App.php:503
#8 Slim\App:__invoke in C:\OpenServer\domains\view\vendor\zeuxisoo\slim- 
whoops\src\Zeuxisoo\Whoops\Provider\Slim\WhoopsMiddleware.php:31
#7 Zeuxisoo\Whoops\Provider\Slim\WhoopsMiddleware:__invoke in 
C:\OpenServer\domains\view\vendor\slim\slim\Slim\DeferredCallable.php:57
#6 call_user_func_array in C:\OpenServer\domains\view\vendor\slim\slim\Slim\DeferredCallable.php:57
#5 Slim\DeferredCallable:__invoke in C:\OpenServer\domains\view\vendor\slim\slim\Slim\MiddlewareAwareTrait.php:70
#4 call_user_func in C:\OpenServer\domains\view\vendor\slim\slim\Slim\MiddlewareAwareTrait.php:70
#3 Slim\App:Slim\{closure} in C:\OpenServer\domains\view\vendor\slim\slim\Slim\MiddlewareAwareTrait.php:117
#2 Slim\App:callMiddlewareStack in C:\OpenServer\domains\view\vendor\slim\slim\Slim\App.php:392
#1 Slim\App:process in C:\OpenServer\domains\view\vendor\slim\slim\Slim\App.php:297
#0 Slim\App:run in C:\OpenServer\domains\view\index.php:60

Please help.

Note: this branch is rebased on PR #66 so there's some duplication. Can adjust if needed.

• Routing component bumped to Laravel 5.6. No additional changes were required.
• Middleware examples were merged into Routing component, and are no longer separated. All code is up-to-date for 5.6.

Started porting components to 5.5. Already ported the following components:

• Logs
• Config
• Encryption

Working on more components in the following days.

In the documentation http://laravel.com/docs/5.1/queries#selects, there is a section Raw Expressions which is an example of code to use raw expressions

$users = DB::table('users')
                     ->select(DB::raw('count(*) as user_count, status'))
                     ->where('status', '<>', 1)
                     ->groupBy('status')
                     ->get();

And how it can be used without a framework?

Hi,

first of all let me congratulate your for your amazing work. I'm currently experimenting things, and I'm focusing essentially on the Routing component. I currently have a micro app with the router implemented with some Controllers.

My question is, is it complicated to implement middlewares? What should I do to make this possible? Could you point me in the right direction please?

Thanks :+1:

Adding the cache component. @mattstauffer do you want another driver done? Something like redis or memcache would require those services to be running locally if you wanted to test them in the browser.

Signed-off-by: Hunter Skrasek [email protected]

Hi dear I create app and route helper method same laravel helper methods and my code this is: function app($abstract = null, array $parameters = []) { if (is_null($abstract)) { return Container::getInstance(); }

`return Container::getInstance()->make($abstract, $parameters);`

} function route($name, $parameters = [], $absolute = true) { return app('url')->route($name, $parameters, $absolute); } but when call route and send route name for example route('profile') i have this error:

Fatal error: Uncaught ReflectionException: Class url does not exist in vendor\illuminate\container\Container.php:877 I think laravel use RoutingServiceProvider and I need provider please help thanks

Hey @mattstauffer,

Big fan of the work you have done on using illuminate components outside of Laravel and recently had to upgrade a project from using illuminate/mail 4.2 to 7 so thought I would contribute a PR.

Implementing queue support is a little more complex but let me know if you want me to include that as well.

Hopefully the style and approach is inline with other component examples and please let me know if you would prefer any refactors :-)

Cheers!

Hey @mattstauffer ,

This might supersede #192 idea and prior PR. Here is an example of how to get Cache, Config, and Env.

Some notes:

1. Not sure one would want to, but Illuminate\Support\Arr is needed to parse output of Cache::get(...) as it doesn't handle dot notation.
2. I can't beat Laravel's logic for handling cache/env for different environments. Not sure how that would be demonstrated other than copy/pasting from their source code.

Works-for-me example code:

<?PHP

/*
  Note, these variables aren't directly accessible. Use globals
  EG: Illuminate\Support\Facades\Config::get("app.cnx")
 */

use Illuminate\Container\Container;
use Illuminate\Support\Arr;
use Illuminate\Config\Repository;
use Illuminate\Support\Facades\Facade;
use Illuminate\Filesystem\Filesystem;
use Illuminate\Cache\CacheManager;
use Dotenv\Dotenv;
use Illuminate\Support\Facades\Config;
use Illuminate\Support\Facades\Cache;
use Illuminate\Support\Env;

defined("FILE_ROOT") ? true : define("FILE_ROOT", realpath(".."));

// create dummy app
$app = new Container();


// would want to refactor to make sure cache is used in production
try {
    // check if file exists. if not, presume production enviroment
    $dotenv = Dotenv::createImmutable(FILE_ROOT);
    $dotenv->load();
} catch (Exception $e) {
    // presume production
    error_log($e->getMessage());
}

// config setup
$config = new Repository(require(FILE_ROOT . "/backend/config/app.php"));

// bind $config to $app
$app->instance(
    'config',
    $config
);

// cache stuff
$cacheC = new Container();
$cacheC['config'] = $config->get('app.cache');
$cacheC["files"] = new Filesystem();
$cacheManager = new CacheManager($cacheC);
$cache = $cacheManager->store();

// bind $cache to $app
$app->instance(
    'cache',
    $cache
);

$cache->put('test', 'This is loaded from Redis cache.', 500);
$cache->put('app', $config->get('app'));

$config->set('test', 'rofl');

Facade::setFacadeApplication($app);

s(Config::get('test'));
s(Config::get('app.cnx'));

s(Cache::get('test'));
s(Arr::get(Cache::get('app'), 'cnx'));

s(Env::get('RUN_MODE'));

Output:

After much tinkering, I've come up with a way to access config data via Illuminate\Support\Facades\Config

This uses some code from the existing Config example and uses a container (using kint just for dumping):

<?PHP
use Illuminate\Support\Facades\Config;
use Illuminate\Container\Container;
use Illuminate\Config\Repository;

$config = new Repository(require(FILE_ROOT . "/config/app.php"));
$app = new Container();

$app->instance(
    'config',
    $config
);

Illuminate\Support\Facades\Facade::setFacadeApplication($app);
s($app->get('config')->get("app"));
s(Config::get('app'));

Output:

Current example uses a slim app, so is incompatible with the above. Would it make sense to add a separate file like "components/config/example2.php" (for instance)?

EDIT: This may tie in some how to PR #191 ... but maybe not.

Hey

I've provided an example of how to use the env() helper in conjunction with direct leverage of the Dotenv\Dotenv library. Unfortunately, the values aren't accessible with Illuminate\Support\Env; not sure what the missing bit is.

That said, maybe it's not important. IIRC, laravel folks say to only rely on app environment variables in the config files.

Thoughts?