I just started working with Laravel. I need to rewrite a whole system I made some years ago, using Laravel 4 as base framework. In my old system, I used to have a `constant.php` file with some constants declared, and a `globals.php` file which contained lots of array sets (for example, categories statuses, type of events, langs, etc.). By doing so, I could use something like

    foreach ( $langs as $code =&gt; $domain ) {
        // Some stuff
    }

anywhere in my app.

My question is, how can I store that info in the so called &quot;laravel way&quot;. I tried using some sort of object to store this info, setting this as a service and creating for it a facade:

**app/libraries/Project/Constants.php**

	namespace PJ;

	class Constants {
		
		public static $langs = [
				&#39;es&#39; =&gt; &#39;www.domain.es&#39;,
				&#39;en&#39; =&gt; &#39;www.domain.us&#39;,
				&#39;uk&#39; =&gt; &#39;www.domain.uk&#39;,
				&#39;br&#39; =&gt; &#39;www.domain.br&#39;,
				&#39;it&#39; =&gt; &#39;www.domain.it&#39;,
				&#39;de&#39; =&gt; &#39;www.domain.de&#39;,
				&#39;fr&#39; =&gt; &#39;www.domain.fr&#39;
			];
	}

**app/libraries/Project/ConstantsServiceProvider.php**

	namespace PJ;
	 
	use Illuminate\Support\ServiceProvider;
	 
	class ConstantsServiceProvider extends ServiceProvider {
	    public function register() {
	        $this-&gt;app-&gt;singleton(&#39;PJConstants&#39;, function() {
	            return new Constants;
	        });
	    }
	}

**app/libraries/Project/ConstantsFacade.php**

	namespace PJ;
	 
	use Illuminate\Support\Facades\Facade;
	 
	class ConstantsFacade extends Facade {
	    protected static function getFacadeAccessor() { 
	        return &#39;PJConstants&#39;;
	    }
	}

**composer.json**

    &quot;psr-4&quot;: {
         &quot;PJ\\&quot;: &quot;app/libraries/Project&quot;
    },

and so I access that property as `PJ\Constants::$langs`.

This works, but I doubt it is the most efficient or correct way of doing it. I mean, is it the right way to &quot;propagate&quot; a variable by creating a whole Service Provider and facades and all such stuff? Or where should I put this data?

Thanks for any advice.

**_EDIT # 01_**

Data I want to pass to all controllers and views can be directly set in script, like in the example at the beginning of my post, **but** it can also be generated dynamically, from a database for example. This data could be a list of categories. I need them in all views to generate a navigation bar, but I also need them to define some routing patterns (like `/category/subcategory/product`), and also to parse some info in several controllers (Like get info from the category that holds X product). 

My array is something  like:

    $categories = [
        1 =&gt; [&#39;name&#39; =&gt; &#39;General&#39;, &#39;parent&#39; =&gt; 0, &#39;description&#39; =&gt; &#39;Lorem ipsum...&#39;],
        2 =&gt; [&#39;name&#39; =&gt; &#39;Nature&#39;, &#39;parent&#39; =&gt; 0, &#39;description&#39; =&gt; &#39;Lorem ipsum...&#39;],
        3 =&gt; [&#39;name&#39; =&gt; &#39;World&#39;, &#39;parent&#39; =&gt; 0, &#39;description&#39; =&gt; &#39;Lorem ipsum...&#39;],
        4 =&gt; [&#39;name&#39; =&gt; &#39;Animals&#39;, &#39;parent&#39; =&gt; 2, &#39;description&#39; =&gt; &#39;Lorem ipsum...&#39;]
    ]

Just as an example. Index is the id of the category, and the Value is info associated with the category.

I need this array, also, available in all Controllers and Views. 

So, should I save it as a Config variable? How else could I store these data; what would be the best and semantically correct way?

All Global State Solutions on Gang of Coders

Total of 1 Global State Solutions

Laravel: Where to store global arrays data and constants?