Coder Social home page Coder Social logo

platform's Introduction

Orchestra Platform 4

Orchestra Platform is an admin panel that handles Laravel extensions and user management. Our curation of Laravel extensions provide the boilerplate for any web application development to ensure a speedy deployment using the best tools available on Laravel.

Build Status Latest Stable Version Total Downloads Latest Unstable Version License

Table of Content

Version Compatibility

Laravel Platform
5.5.x 3.5.x
5.6.x 3.6.x
5.7.x 3.7.x
5.8.x 3.8.x
6.x 4.x

Quick Installation

composer create-project orchestra/platform your-project-name --prefer-dist

Resources

Contributing to the Orchestra Platform

Contributions can be made to the Orchestra Platform's respective component repositories:

We also have some independence packages that would work well with Orchestra Platform, including:

Contributions for the website and documentation can be made here:

Security Vulnerabilities

If you discover a security vulnerability within Orchestra Platform, please send an e-mail to [email protected]. All security vulnerabilities will be promptly addressed.

License

  • The Laravel PHP Framework is open-sourced software licensed under the MIT license by Taylor Otwell.
  • The Orchestra Platform is open-sourced software licensed under the MIT license.

platform's People

Contributors

ahmadshah avatar arcanedev-maroc avatar crynobone avatar dakira avatar ghostprofile avatar gitter-badger avatar grahamcampbell avatar greabock avatar halaei avatar hikouki avatar irazasyed avatar jerguslejko avatar josephsilber avatar jspringe avatar kevinsimard avatar lsinger avatar luqmanrom avatar martinbean avatar martinssipenko avatar michaeldyrynda avatar mzaalan avatar pedes42 avatar philbates35 avatar pulkitjalan avatar rndb8418 avatar taylorotwell avatar themsaid avatar tomcastleman avatar vinicius73 avatar vinkla avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

platform's Issues

FatalErrorException Thrown from clean Orchestra installation

I just installed a fresh Orchestra Platform project, using the create-project composer command:

composer create-project orchestra/platform website 2.1.x --prefer-dist

I navigated to /admin, which as expected showed the installation page. I installed Orchestra without any issues.
After logging in and navigating to settings, to make some changes, I received the following:

image

Worked fine yesterday. Has there been a change to perhaps the Laravel Repo, or do I have something wrong in my environment?

Publishing Migrate files from other packages.

In the Packages such as https://github.com/rtconner/laravel-tagging , the migration files are moved to base_path/database/ according to laravel 5 folder structure. Where as in Orchestra's folder structure it needed to be moved to the path base_path/resources/database/
Boot for the above package.

public function boot() {
$this->publishes([
__DIR__.'/../../../config/tagging.php' => config_path('tagging.php'),
__DIR__.'/../../../migrations/2014_01_07_073615_create_tagged_table.php' => base_path('database/migrations/2014_01_07_073615_create_tagged_table.php'),
__DIR__.'/../../../migrations/2014_01_07_073615_create_tags_table.php' => base_path('database/migrations/2014_01_07_073615_create_tags_table.php'),
]);
}

I have to manually move the files from /database to /resources/database in order for migration to work after publishing the package. Is there any work around for this issue.

Orchestra Platform 2.1

Platform

  • Add a quick installation guide on Github.
  • Improve Orchestra Platform performance.
  • Include orchestra/control by default. #17
  • Include orchestra/story by default. #18
  • Send email as text/html and text/plain. #25
  • Change minimum stability to stable.

Laravel Changes

  • Add remote support.
  • Support for Illuminate\Routing refactors.
  • Update default view for slider pagination to Bootstrap 3.
  • Setup live debugger in app.
  • Update controller alias.
  • Added repository to Composer file.
  • Include upgrading guide.

Components

Asset

  • Add Orchestra\Asset\Container::show() method to compile both styles and scripts. orchestral/asset#3

Auth

Debug

Extension

Facile

  • Check request header to detect allowed content-type. orchestral/facile#3
  • Refactor private API to reduce redundant responsibility.

Foundation

Html

  • Predefined package path to avoid additional overhead to guest package path. orchestral/html#11
  • Add support for button from Form Builder.
  • Add Orchestra\Html\Form\Grid::setup() and Orchestra\Html\Form\Grid::resource() helper.

Memory

Optimize

  • Update list of compiled classes for Orchestra Platform 2.1.
  • Replace default composer.json post commands.
  • Add orchestra/warden. orchestral/optimize#2

Resources

Support

  • Add Orchestra\Support\Relic.
  • Add Orchestra\Support\Str::replace().
  • Add Orchestra\Support\Facades\Warden for orchestra/warden integration.

Translation

  • Deprecated since illuminate/translation already offer the same functionality.

Testbench

  • Update support for Laravel 4.1.

View

Warden

Widget

  • Predefined package path to avoid additional overhead to guest package path. orchestral/widget#6

Website

  • Redevelop the website using Orchestra Platform.

[Insight] Logical operators should be avoided

in server.php, line 14

The and operator does not have the same precedence as &&. This could lead to unexpected behavior, use && instead.

$requested = $paths['public'].$uri;

// This file allows us to emulate Apache's "mod_rewrite" functionality from the
// built-in PHP web server. This provides a convenient way to test a Laravel
// application without having installed a "real" web server software here.
if ($uri !== '/' and file_exists($requested))
{
    return false;
}

require_once $paths['public'].'/index.php';

Posted from SensioLabsInsight

hooking into config gives no error

When trying to create/update config via hooking into the extension/config page, and saving it, you have to be DEAD on how you are doing it, there is no feed back if the data has not been saved.

Orchestra Platform 2.0

Orchestra Platform 2 would utilize on Laravel 4 PHP Framework, the overall public API would still remain unchanged while the internal architecture would be completed improved via Facades and ServiceProvider.

Docs

Documentation would have it's own repository and should cover usage as a complete package or as individual components.

  • Use Jekyll to manage website as well as documentation.
  • Change-log on every individual component.

Components

With the introduction of composer, we are now free to organize the code into smaller component where there would be use-case where you can use one or two Orchestra Platform components without everything else. At this moment we have organize the code into following components:

  • Experimental component.

Asset Components

  • Migrate from Laravel 3.
  • Unit tests.
  • Documentation.

Auth Components

  • Migrate from v1.
  • Installation command.
  • Unit tests.
  • Documentation.

Extension Components

  • Migrate from v1.
  • Add support to register and boot service provider.
  • Command for Extension.
  • Installation command.
  • Unit tests.
  • Documentation.

Facile Components

  • Migrate from v1.
  • Unit tests.
  • Documentation.

Foundation Components

  • Migrate from v1.
  • Routing.
  • Installation process.
  • Unit tests.
  • Documentation.
  • Bootstrap 3 integration.

Html Components

  • Migrate from v1.
  • Unit tests.
  • Documentation.

Memory Components

  • Migrate from v1.
  • Installation command.
  • Unit tests.
  • Documentation.

Resources Components

  • Migrate from v1.
  • Add support for resource controller.
  • Unit tests.
  • Documentation.

Support Components

  • Migrate from v1.
  • Unit tests.
  • Documentation.

View Components

  • Migrate from v1.
  • Unit tests.
  • Documentation.

Widget Components

  • Migrate from v1.
  • Unit tests.
  • Documentation.

Release Schedule

First 2.0 beta release 2.0.0-BETA1 would come soon after Laravel 4 release (May 28th, 2013). 2.0.0 however is schedule for August 2013 to give ample time for any improvement and bugfixes. During the beta, we would focus on following areas:

  • Bugfixes
  • Documentation
  • Unit testing

Deprecated

This would be the checklist for those migration from Orchestra Platform 1.*.

  • Dependency management for Extension has been removed in favor to Composer.
  • Remove artisan orchestra::toolkit, alternative workbench solution might be introduce in the future.
  • Orchestra\Theme::map() has been deprecated and removed.

Issue when using orchestra/platform installer

When I install using orchestra/platform installer

composer create-project orchestra/platform 3.3.x --prefer-dist --stability=dev

I get

Writing lock file
Generating autoload files
> Orchestra\Foundation\ComposerScripts::postUpdate
> php artisan orchestra:assemble


  [ErrorException]
  Declaration of App\Providers\EventServiceProvider::boot() should be compatible with Illuminate\Foundation\Support\Providers\EventServiceProvider::boot()


Script php artisan orchestra:assemble handling the post-update-cmd event returned with an error


  [RuntimeException]
  Error Output:

[Bug] Ajax call on a resource route gives error

Hi,
this is the setup

// locale.js

$.ajax({
    type: 'POST',
    url: '{{resources("chattranslation/ajax-release-translation")}}',
    data: { translationId: 'some-value', translation: 'somevalue' }
});
//ChatTranslationServiceProvider

public function boot()
{
    $path = realpath(__DIR__.'/../../');
    $this->package('chattranslation', 'chattranslation', $path);
    Event::listen('orchestra.started: admin', function () {
        $chat = Resources::make('chattranslation', array(
            'name'    => 'Messages Translation',
            'uses'    => 'restful:Turistas\ChatTranslation\Controller\TransController',
            'visible' => \Auth::check(),
        ));
    });

    Acl::make('chattranslation')->attach(App::memory());
}
//TransController

public function postAjaxReleaseTranslation()
{
    $translation = $this->translation->find(Input::get('translationId'));
    if (Input::get('translation')) {
        $translation->translated_body = Input::get('translation');
    } else {
        $translation->touch();
    }
    $translation->save();
}

now this configuration gives NotFoundHttpException
but if I remove the data from the js like this

// locale.js

$.ajax({
    type: 'POST',
    url: '{{resources("chattranslation/ajax-release-translation")}}'
});

the NotFoundHttpException error vanishes instead it gives me the obvious error on $translation = $this->translation->find(Input::get('translationId')); this, however, tells us that it reached the right method.

The only way that works with sending data is to add a return statement inside the controller method like

//TransController

public function postAjaxReleaseTranslation()
{
    $translation = $this->translation->find(Input::get('translationId'));
    if (Input::get('translation')) {
        $translation->translated_body = Input::get('translation');
    } else {
        $translation->touch();
    }
    $translation->save();
    return true;
}

with this small addition everything works as intended but only because I don't care about data sent back to the client in this case.

Hope to have explained the problem throughly

Orchestra Platform 3.0

Platform

  • Support for Laravel 5.0
  • Add App\Providers\ExtensionServiceProvider #43
  • Add App\Providers\DebugServiceProvider d8b66d5
  • Include orchestra/testbench as default TestCase.
  • Improves default page.

Components

Auth

  • Rename Orchestra\Auth\Acl\Container to Orchestra\Auth\Acl\Acl.
  • Add auth contracts.

Extension

  • Allow support for "base"'s orchestra.json and orchestra folder to base_path().'/orchestra.
  • Remove Orchestra\Extension\PublisherServiceProvider.
  • Allow to register deferred services. orchestral/extension@cb110a7
  • Add extension contracts.
  • Safe mode should persist between request. orchestral/extension#52

Facile

  • Rename Orchestra\Facile\Container and Orchestra\Facile\Facile.
  • Rename template classes.

Foundation

  • Include base_path().'/database/orchestra/installer.php for installation. orchestral/foundation#161
  • Update Form and HTML facades location.
  • Should be able to set configuration to allow caching of UserMetaRepository. orchestral/foundation#162
  • Add Orchestra\Foundation\Providers\ExtensionServiceProvider. orchestral/foundation#163
  • Implement filters and middleware for routing.
  • Fixes routing test suite.
  • Make installation routes optional.
  • Make orchestra/debug optional.
  • Make orchestra/resources optional.
  • Make orchestra/facile optional.
  • Use Orchestra\Foundation\Middleware\UseBackendTheme middleware. orchestral/foundation#169
  • Separate Routing and Processor test case. orchestral/foundation#168

HTML

  • Explicitly require illuminate/html. orchestral/html#25
  • Allow Orchestra\Html\Form\Factory to handle all request to Illuminate\Html\FormBuilder.
  • Add Orchestra\Html\Table\Grid::searchable() and Orchestra\Html\Table\Grid::sortable() to facilitate searching and sorting.
  • Allow to retrieve instance of Illuminate\Http\Request and Illuminate\Translation\Translator from within Form and Table builder.
  • Add Orchestra\Html\Table\Grid::paginated() helper method to access pagination state for current table.
  • Allow support for checkboxes form.
  • Allow control to be accessed from Orchestra\Html\Form\Grid context via a new find() method.
  • Update Illuminate\Pagination\Paginator changes.

Memory

  • Remove Orchestra\Memory\Abstractable\Container.
  • Change the way configuration is cached when using Orchestra\Memory\Abstractable\DatabaseHandler. orchestral/memory#19

Model

Optimize

  • Update changes to Illuminate\Foundation\Console\OptimizeCommand.
  • Update compiled list.

Publisher

  • Config publishing command.
  • Migration publishing command.

Resources

  • Use orchestra/routing.
  • Rename Orchestra\Resources\Container and Orchestra\Resources\Router.
  • Add get(), set() and forget() helper method on Orchestra\Resources\Router to allow direct manipulation to it's attributes value.

Testbench

  • Update application bootstrap action to match Laravel 5.0
  • Update config templates to match Laravel 5.0

Support

  • Add Orchestra\Support\Facades\HTML facade.
  • Remove Orchestra\Support\Relic.
  • Remove Orchestra\Support\Messages.
  • Remove Orchestra\Support\MessagesServiceProvider.

View

  • Include app_path().'/Http/Views for default view path.
  • Allow cascading theme views replacement if available from resources/themes/* directory.
  • Elixir helper for theme. orchestral/view#16

Extensions

Control

Story CMS

Integrations

  • Properly handle Illuminate\Http\Request not available from within console environment.
  • Properly handle public path when using php artisan serve.

php internal server: 404

i just installed platform via composer, and use php internal server to see installation page

php -S localhost:8000 server.php

but the server.php router seems not working or something. because php can not find public packages:

[Tue Feb  4 16:37:43 2014] ::1:45026 [404]: /packages/orchestra/foundation/vendor/select2/select2.css - No such file or directory
[Tue Feb  4 16:37:43 2014] ::1:45027 [404]: /packages/orchestra/foundation/vendor/delta/theme/jquery-ui.css - No such file or directory
[Tue Feb  4 16:37:43 2014] ::1:45028 [404]: /packages/orchestra/foundation/vendor/bootstrap/css/bootstrap.min.css - No such file or director
...

did i missed something? i use

PHP 5.5.8-3 (cli) (built: Jan 24 2014 09:12:11) 
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2013 Zend Technologies
    with Zend OPcache v7.0.3-dev, Copyright (c) 1999-2013, by Zend Technologies

Orchestra Platform 1.2

Task

  • Merge Orchestra Platform
  • Update Laravel 3.2.*

Release Schedule

To be released on June 20th, 2013.

[WIP] Orchestra Platform v3.2.0

We would love to get your feedback and ideas for Orchestra Platform 3.2. Just post them here.

The following lists are a short roundup of all feature requests below (hope I did not miss one) and what our thoughts are about them. I will update the list if new ideas are posted.

Platform

  • Bump minimum requirement to PHP 5.6.0.

Components

Extension

Facile

  • Allow to get proper response based on Accept header (via content-negotiation). orchestral/facile#10

Foundation

Imagine

Kernel

Support

  • Orchestra\Support\Expression should implements Illuminate\Contracts\Support\Htmlable. orchestral/support#39

Testbench

today installation not working as expected

Hi,
As I read you've did a very nice stuff and I've started today to look at it.

Installed. Logged in.
First:
Profile and Password can't be submitted. Issue in AccountController of foundation, maybe a should fill it there, lines 61 and 131.
(the explanation: I don't think that the equality ==! will be ever true as the user id is int and the input id is string. '=!' I think is the stuff or you have to cast.)

Second:
None of the Components are displayed in Extensions menu, neither the Control so present in your demos.

Env:
Win7 x64, NginX 1.2.1, PHP 5.4.3, MariaDB 5.5.24

Thank you very much,
Paul

Orchestra Platform 2.2

  • Increase minimum PHP version to 5.4*
  • Add support to Laravel Forge and Homestead. #38
  • Add SoftDeletingTrait to the default User class.

Components

Asset

  • Add support for Orchestra\Asset\Container::prefix() to support external URL. orchestral/asset#7

Auth

  • Add support for new remember_token.
  • Add Orchestra\Auth\Acl\AuthorizationTrait.

Extension

  • Convert php artisan extension:detect to use Symfony's table.

Facile

  • Allow output as CSV.

Foundation

Notifier

Support

  • Add Orchestra\Support\Traits\ObservableTrait.
  • Add Orchestra\Support\Traits\QueryFilterTrait.
  • Add Orchestra\Support\Traits\UploadableTrait.
  • Add Orchestra\Support\Traits\ValidationTrait.

View

  • Command for managing theme options.

* We however will not accept massive array() to [] Pull Request until 2.1 reach End of Life (EOL) by January 15th, 2016.

errors installing orchestral/platform

First of all: I am amazed by this system/framework! I was going to write an almost identical system during the next weeks, but stumbled upon this by sheer luck hanging around in the laravel IRC channel!

However, I got some errors in the console when I wanted to install the lastest version: http://hastebin.com/bodaverusa.txt

I just wanted to report this, in case some things might got broken when those files could not be found ...

Error on SessionHandler::read(): when loading the Orchestra Platform

I am using orchestra for one of my current project and fetched the code using composer. When I issued the php artisan serve command and visit the url for installation, I am greeted with the following error:-

SessionHandler::read(): The session id is too long or contains illegal characters, valid characters are a-z, A-Z, 0-9 and '-,'

I had ran the composer update several times to make sure all the components are updated. Older projects done in orchestra are working fine but unable to fetch a clean one from composer. Any idea why this occurs?

Something seems wrong

So after a fresh install, the only button I see is a Home button on the admin section... and the text on that home page ONLY says this:

Welcome to your new Orchestra Platform site!

If you need help getting started, check out our documentation on First Steps with Orchestra Platform. If you’d rather dive right in, here are a few things most people do first when they set up a new Orchestra Platform site.

--- nothing below at all. Is this what to expect, or am i obviously missing something?

Orchestra Platform 2.0.* update based on Laravel 4.0.8

Scheduled release alongside Laravel Framework v4.0.8 release.

Components

The following components has updated that need to be released:

  • Orchestra\Auth
  • Orchestra\Facile
  • Orchestra\Foundation
  • Orchestra\HTML
  • Orchestra\Support
  • Orchestra\View
  • Orchestra\Testbench

LDAP Support

I am sorry in advance if this is the wrong place to ask a question.
Is LDAP/AD support on the roadmap?

Thank you.

Welcome text missing something

Assalamuʻalaikum,

Upon installation, I'm presented with the following screen:

screencapture-localhost-orchestra-website-public-admin-1450535331872

It says "...here are a few things most people do first when they set up a new Orchestra Platform site." However, I don't see anything. Is it missing something or is something wrong with my browser?

Thanks for your time.

[WIP] Orchestra Platform 3.1

  • Standardise path for generated compiled.php, services.json, routes.php and config.php.

Foundation

  • Use @inject blade helper.
  • Convert Publisher (using FTP) to external project/repository.
  • Convert Filters to Middleware. orchestral/foundation#181
  • Add Orchestra\Foundation\PipelineServiceProvider.

Kernel

Optimize

  • Update compiles list.

Support

  • Remove FTP namespace.
  • Add Orchestra\Support\Providers\PipelineServiceProvider.
  • Add Orchestra\Support\Providers\Traits\FiltersProviderTrait and Orchestra\Support\Providers\Traits\MiddlewareProviderTrait.

Translation

  • Update Laravel folder setup.

Optional Components

Tenanti

  • Convert Orchestra\Tenanti\Migrators\Queue to Orchestra\Tenanti\Jobs namespace and separate each to it's own class.

@title() is not registered as blade helper

@title() helper to generate <title> is not rendering in app.blade.php

Rendered HTML template


<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    @title()

    <!-- Bootstrap -->
    <link href="/css/app.css" rel="stylesheet">

    <!-- Fonts -->
    <link href='//fonts.googleapis.com/css?family=Roboto:400,300' rel='stylesheet' type='text/css'>

    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
    <!--[if lt IE 9]>
        <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
        <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
</head>

fresh install + navigate to the /admin... CRASH.

Class Orchestra\Model\User contains 3 abstract methods and must therefore be declared abstract or implement the remaining methods (Illuminate\Auth\UserInterface::getRememberToken, Illuminate\Auth\UserInterface::setRememberToken, Illuminate\Auth\UserInterface::getRememberTokenName)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.