Skip to content

Install issues with Fresh Laravel 11 #117

Open

Description

@domthomas-dev

Hi, it's sure, I'm a beginner with StoryBook.
I followed the documentation of this package.

I installed a new fresh Laravel 11.

laravel new storybook
composer require area17/blast
php artisan vendor:publish --provider="A17\Blast\BlastServiceProvider" --tag="blast-config" 

I don't know how I should update the config file

If I do this :

php artisan blast:demo

The story is created

If I do :

php artisan blast:launch

or

php artisan blast:launch --install

I have this :
Screenshot 2024-03-14 at 18 49 49

and
Screenshot 2024-03-14 at 18 48 32

Activity

  1. mrtimbrook commented on Mar 14, 2024

    @mrtimbrook
    Collaborator

    It looks like Storybook Server can't access the application. If you open the network tab in your dev tools you'll see the request to your application for the component view. You can right click that and open in a new tab. That will show you the error in your application.

    The most common cause for this is that the APP_URL in your .env is incorrect.

    Blast uses env('STORYBOOK_SERVER_HOST', env('APP_URL')) . '/storybook_preview', for the URL to generate the views in storybook so you can either define the env var STORYBOOK_SERVER_HOST or use APP_URL.

  2. creed-aderse commented on May 21, 2024

    @creed-aderse

    I have the same issue. The APP_URL is correct.
    What I am seeing in the documentation here: https://dev.to/area17/getting-started-with-blast-storybook-for-laravel-blade-c5c is this section:

    Installation
    You can get started by installing Blast using:
    composer require area17/blast
    This will:
    
    Create a stories and a data directory for your story Blade files and any associated data
    Publish assets used by Blast to the application's public directory
    Create a route from which to load your component examples
    

    I don't see any routes being created.

    @domthomas-dev - were you ever able to get this to work?

  3. creed-aderse commented on May 21, 2024

    @creed-aderse

    @domthomas-dev - this worked for me when I changed my APP_URL to include the port => http://localhost:8000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions