Laravel Vue SPA, Bulma themed. For demo login use `[email protected]` & `password` -

  • By Laravel Enso
  • Last update: Dec 14, 2022
  • Comments: 17

Laravel Enso

StyleCI Backers on Open Collective Sponsors on Open Collective Github Issues Build Status GitHub language count GitHub GitHub tag (latest by date) GitHub Release Date GitHub commits since latest release

Hit the ground running when building your new Laravel SPA project with boilerplate and extra functionality out of the box!

 

Watch the demo

click on the photo to view a short demo in compatible browsers

Important

If you are using this project please consult the changelog on every update.

Official Documentation

The documentation is available here split into backend and frontend. Note that most sections have short demo clips.

Take It For A Spin

You may try out a live demo installation by visiting laravel-enso.com and logging in with [email protected] and password.

Installation Steps

  1. Download the project with git clone https://github.com/laravel-enso/enso.git --depth 1

  2. Within the project folder run composer install

  3. Create a database for your site (see the Laravel database documentation), copy or rename the .env.example file to .env, edit the database configuration information, and run php artisan key:generate

  4. In order to serve the back-end API, take a look at the Local Development Server section of the Laravel installation documentation and consider using Valet for a better experience

  5. Run php artisan migrate --seed

  6. Open the client folder, copy the .env.example file, save it as .env and set the URL for the back-end API (which you've configured at step 4)

  7. Run yarn && yarn build

  8. Launch the site and log into the project with user: [email protected], password: password

  9. For live reload / hot module replacement functionality run yarn serve

  10. (optional) Setup the configuration files as needed, in config/enso/*.php

Enjoy!

Support services (new)

While developing Enso, we constantly received private inquiries from devs and teams asking us about paid support. Some of these requests even lead to fruitful collaborations, so we finally decided to launch such an option.

If you're looking for premium support when building applications with Enso we can help you with that. Our support packages start at 480 Eur / month with 8 hours included. With premium support you will get:

  • a private repo on our self hosted gitlab instance where you can host your project
  • priority in addressing your issues
  • help with understanding the Enso environment
  • getting you to be proficient when developing on Enso
  • mentoring
  • code reviews
  • general advice & support on Laravel & Vue
  • assistance on Enso version upgrades
  • up to 4 hours / month of remote desktop sessions and call conferences with your team
  • direct communication via Slack during our office hours

The support services are provided by a team of 4 members.

Thanks

Built with with ❤️ , crafted on Laravel 5.6.x, Bulma 0.6.x, Vuejs 2.5.x and:

Vue Router, Vuex, Axios, Font awesome 5, Animate.css, Bulma-Extensions, Driver.js, Chart.js, Flatpickr,

Special thanks to Taylor Otwell, Jeffrey Way, Evan You and Jeremy Thomas.

Contributions

are welcome. Pull requests are great, but issues are good too.

Sponsor (new)

This project is backed by Earthlink

Contributors

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

License

This package is released under the MIT license.

Github

https://github.com/laravel-enso/enso

Comments(17)

  • 1

    White screen

    Hello!

    I have cloned this project and followed install steps but I only have a white screen. Debugbar dont throw any info.

    How I can proceed to solve it?

    My repository is here: https://github.com/jjmontalban/Enso

    Any advice will be well received

    Best regards!

  • 2

    Add replace note about date-fns & rewording for v3.0.0 changelog

    Add replace note about date-fns move (used for custom components & in "transition" state for resources/js/components/enso

    note: marking as draft pull until fully upgraded, to group all further missing changes/notes here. (almost through everything though, so I don't expect anything more significant missing from the changelog/upgrade steps)

  • 3

    Meta information missing after update to 2.3.x

    Hi, I'm facing problems with meta information after updating to 2.3.x version. In particular, meta.appName is blank and I'm getting authentication errors related to CSRF token (this is the message gotten after a successful authentication: "can't assign to property "csrfToken in enso.js line 323").

    From where can I set meta tags? Thanks

  • 4

    Icon in custom renderer

    I have a table where I use a renderer for a column. The renderer is defined as:

    customRender(row, column) {
    	            switch (column.name) {
    		            case 'document_url':
    		                return row[column.name] ? `<a href="${row[column.name]}" target="_blank" class="button is-small is-table-button is-primary"><span class="icon is-small"><fa icon="cloud-upload-alt"></fa></span>`
    		                    : ``;
    		            default:
    		                toastr.warning(`render for column ${column.name} is not defined.`);
    		                return this.__(row[column.name]);
    	            }
    	        }
    

    At the moment the icon is not displayed correctly (and in dom its still <fa icon="cloud-upload-alt"></fa> instead of svg tag.

    If I use the icon anywhere else on the same page it works (means it is imported correctly)

  • 5

    Finally got it working but I am unable to login

    I am attempting to login using the [email protected] and password credentials. I seeded my tables and I see the entry on the users table for [email protected].

    Nothing happens after I hit Login.

    My URL for testing Enzo SPA is: http://admin.digihometour.com/login

  • 6

    yarn - error

    Output: ERROR Failed to apply patch for package bulma-rtl

    This happened because the patch file patches\bulma-rtl+0.7.1.patch could not be parsed.

    If you just upgraded patch-package, you can try running:

    cd patches\bulma-rtl+0.7.1.patc
    patch -p1 -i h
    npx patch-package bulma-rtl
    cd ../..
    

    Otherwise, try manually creating the patch file again.

    If the problem persists, please submit a bug report:

    https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E
    

    error Command failed with exit code 1. child_process.js:650 throw err; ^

    Error: Command failed: yarn run postinstall

    ERROR Failed to apply patch for package bulma-rtl

    This happened because the patch file patches\bulma-rtl+0.7.1.patch could not be parsed.

    If you just upgraded patch-package, you can try running:

    cd patches\bulma-rtl+0.7.1.patc
    patch -p1 -i h
    npx patch-package bulma-rtl
    cd ../..
    

    Otherwise, try manually creating the patch file again.

    If the problem persists, please submit a bug report:

    https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E
    

    error Command failed with exit code 1.

    at checkExecSyncError (child_process.js:607:13)
    at execSync (child_process.js:647:13)
    at Object.<anonymous> (D:\paradox\Programming\OpenServer\domains\enso\CLIENT\node_modules\postinstall-postinstall\run.js:15:5)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    
  • 7

    feature request : Tailwindcss theme

    This is a feature request.

    Prerequisites

    • [X] Are you running the latest version?
    • [X] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
    • [X] Did you check the documentation?
    • [X] Did you perform a cursory search?

    Description

    tailwindcss theme output

    a clone of the current bulma theme using tailwind

    this theme is using TailwindCss V1.0.0-beta4, so it will be ready for the final verstion with this configurations, only to keep the look

    this is only a mockup using Vue and tailwindcss to divide it for each enso component, so it will be easy to add it.

    const defaultTheme = require("tailwindcss/defaultTheme");
    
    module.exports = {
      theme: {
        // Some useful comment
        extend: {
          colors: {
            white: {
              default: "#ffffff",
              smoke: "#f5f5f5"
            },
            gray: {
              ...defaultTheme.colors.gray,
              290: "#4a4a4a",
              480: "#7a7a7a",
              860: "#dbdbdb"
            },
            blue: {
              ...defaultTheme.colors.blue,
              450: "#3273dc"
            },
            green: {
              ...defaultTheme.colors.green,
              450: "#23d160"
            }
          },
          fontFamily: {
            enso: ["Montserrat", "sans-serif"]
          },
          height: {
            13: "3.25rem"
          },
          inset: {
            13: "3.25rem"
          },
          boxShadow: {
            bnavbar: "0 1px 1px rgba(10, 10, 10, 0.35)",
            bbookmarks: "0 1px 1px rgba(10, 10, 10, 0.2)",
            bsidebar: "0 2px 3px rgba(10, 10, 10, 0.35)"
          }
        }
      },
    };
    
    

    if there is an other idea for a different theme, i can change it. if its ok, i can start merging it with enso and make a PR.

    ps: there is no :bug: https://github.com/laravel-enso/Enso/issues/125#issue-348854265

  • 8

    Themes

    This is a question.

    Prerequisites

    • [x] Are you running the latest version?
    • [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
    • [x] Did you check the documentation?
    • [x] Did you perform a cursory search?

    Description

    I use an own custom theme. In general everything works like expected but I have 2 questions:

    1. How is the default theme for login choosen? I deleted/commented every occurence of light/dark theme in code but still the light theme and not my default is choosen (after deleting cache and everything). If I log in and out my custom theme is choosen for login screen. I also set the theme in index.blade.php
    2. What's the source for theme selector (...mapState('layout', ['themes']),). The light/dark selector is shown in my app (what means that more than one theme is available)
  • 9

    Faulty vendor:publish command

    This is a bug.

    Prerequisites

    • [x] Are you running the latest version?
    • [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
    • [x] Did you check the documentation?
    • [x] Did you perform a cursory search?

    Description

    image

    Steps to Reproduce

    1. Upgrade to 11.12[.2]
    2. Follow CHANGELOG.md upgrade steps (maybe related to #152? couldn't find anything to change as we didn't extend applicable packages yet; except for core usage of them)
    3. Log in, note a blank menu & above errors

    Expected behavior

    App to work

    Actual behavior

    Enso-part of app mostly non-functional (blank menu, notification menu broken, ...)

  • 10

    Errors after fontawsome icon update

    I did the icon update as described but as you can see in screenshots not all icons are working. Some are for my new menu items this is ok, I have to change them manually but some are from the default items like tachometer in dashboard.

    screenshot 2018-01-24 18 47 20 screenshot 2018-01-24 18 47 15

    Did I forgot something? Additionally the spaces between the cards are also missing. This can be a problem in combination with the missing icons?

  • 11

    Can't get yarn serve running

    This is a bug.

    Prerequisites

    • [x] Are you running the latest version?
    • [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
    • [x] Did you check the documentation?
    • [x] Did you perform a cursory search?

    Description

    I use the following config:

    • I run laravel enso in docker
    • I mapped port 8001 to 8080 in docker
    • I access laravel enso with http://localhost:8001/login
    • In my .env File in client folder I defined API_URL=http://localhost:8001/

    Expected behavior

    Browser should show login screen after calling http://localhost:8001/login

    Actual behavior

    I get the following error for: http://localhost:8001/api/meta Proxy error: Could not proxy request /api/meta from localhost:8001 to http://localhost:8080/ (ECONNRESET).

  • 12

    Bump tinymce from 5.10.3 to 5.10.7 in /client

    Bumps tinymce from 5.10.3 to 5.10.7.

    Changelog

    Sourced from tinymce's changelog.

    5.10.7 - 2022-12-06

    Fixed

    • HTML in messages for the WindowManager.alert and WindowManager.confirm APIs were not properly sanitized. #TINY-3548

    5.10.6 - 2022-10-19

    Fixed

    • The name and id attributes of some elements were incorrectly removed during serialization #TINY-8773
    • Notifications would not properly reposition when toggling fullscreen mode #TINY-8701
    • Toggling fullscreen mode with the fullscreen plugin now also fires the ResizeEditor event #TINY-8701
    • The URL detection used for autolink and smart paste didn't work if a path segment contained valid characters such as ! and : #TINY-8069

    5.10.5 - 2022-05-25

    Fixed

    • Base64 data URIs were not extracted correctly during parsing when proceeded by data: text #TINY-8646
    • Empty lines that were formatted in a ranged selection using the format_empty_lines option were not kept in the serialized content #TINY-8639
    • The s element was missing from the default schema text inline elements #TINY-8639
    • Some text inline elements specified via the schema were not removed when empty by default #TINY-8639

    5.10.4 - 2022-04-27

    Fixed

    • Inline toolbars flickered when switching between editors #TINY-8594
    • Multiple inline toolbars were shown if focused too quickly #TINY-8503
    Commits
    • a4c4e46 TINY-9402: Prepare for TinyMCE 5.10.7 release (take 3) (#8331)
    • 0fea476 TINY-9402: Prepare for TinyMCE 5.10.7 release (#8328)
    • 8bb2d26 Merge pull request from GHSA-gg8r-xjwq-4w92
    • 78fa310 TINY-8885: Update changelog for 5.10.6 release (#8198)
    • 5421ec9 TINY-9219: Fix broken tests on Firefox (#8158)
    • 70f8c28 TINY-8979: Backport URL link detection fix (#8127)
    • 4e102c0 TINY-8978: Backport fix for notifications in fullscreen (#8121)
    • a0ae700 TINY-8773: Prevent stripping of "name" and "id" attributes on iframe and img ...
    • 29e04bb TINY-8622: Updated changelog for 5.10.5 release (#7848)
    • f3ab303 TINY-8639: Retain formatted blank lines when format_empty_lines is true (ba...
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by tinymce, a new releaser for tinymce since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 13

    Bump decode-uri-component from 0.2.0 to 0.2.2 in /client

    Bumps decode-uri-component from 0.2.0 to 0.2.2.

    Release notes

    Sourced from decode-uri-component's releases.

    v0.2.2

    • Prevent overwriting previously decoded tokens 980e0bf

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

    v0.2.1

    • Switch to GitHub workflows 76abc93
    • Fix issue where decode throws - fixes #6 746ca5d
    • Update license (#1) 486d7e2
    • Tidelift tasks a650457
    • Meta tweaks 66e1c28

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 14

    Logout does not do anything if session is expired.

    This is a bug.

    Prerequisites

    • [x] Are you running the latest version?
    • [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
    • [x] Did you check the documentation?
    • [x] Did you perform a cursory search?

    Description

    • Login to https://www.laravel-enso.com/
    • Clear your cookies.
    • Logout.

    Expected result: redirect to login page. Actual result: nothing happens.

    Note: If you click on another menu, it will redirect to login.

  • 15

    Bump terser from 4.8.0 to 4.8.1 in /client

    Bumps terser from 4.8.0 to 4.8.1.

    Changelog

    Sourced from terser's changelog.

    v4.8.1 (backport)

    • Security fix for RegExps that should not be evaluated (regexp DDOS)
    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 16

    composer.json loose version match - PHP 8.1 forced upgrade.

    This is a bug.

    Hi,

    You have set a while ago a composer.json dependency for

            "symfony/http-client": "^6.0",
            "symfony/mailgun-mailer": "^6.0"
    

    Which at that time was matching with version 6.0.X which was required PHP >=8.0.

    Both http-client and mailgun-mailer have released 6.1.X which bumped PHP requirements to >=8.1

    Now, upgrading (late) to Laravel-enso 5.0.0 will force (due to these 2 dependencies) an upgrade to 8.1, or force user investigate which dependencies are asking for the upgrade, and try lowering the versions to a compatible version.

    In our case we went for

            "symfony/http-client": "6.0.*",
            "symfony/mailgun-mailer": "6.0.*"
    
  • 17

    FontAwesome 6.1.1 - upgrade.

    This is a feature request.

    Prerequisites

    • [x] Are you running the latest version?
    • [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
    • [x] Did you check the documentation?
    • [x] Did you perform a cursory search?

    Description

    Any plans on upgrading to FA6? I've updated to 6 locally, but Enso still has dependencies in some modules with 5.13...

    Thanks!