Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• composer.json (composer)
• package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this Configure Renovate PR is merged
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• Upgrade to unstable versions only if the existing version is unstable
• Raise PRs immediately (after branch is created)
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, vendor and various test/tests directories
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 7 Pull Requests:

:children_crossing: Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot. View repository job log here.

Moved the clear-compiled to after the update is complete. Allows for deletion of vendor folder and update (clean update). Really deps should never have to be bundled

Great job on this app, I have thought about making something similar in Laravel before but haven't had the time. I like the similarities with Trello.

After install, I noticed the font wasn't loading correctly, I had to change the class in app.css from: body { font-family: "Open Sans"; } to: body { font-family: "Open Sans", sans-serif; }

Thanks!

by issuing laravel commands prior to composer running removing the vendor folder stops composer from being able to call update...

specifically php artisan clear-compiled should be moved into post-update-cmd

Lay bhai ayashi kar.. Jaldi jaldi main kiya h isliye jesa b h dekh ly..

Or email k liye .env.example ko copy kar k .env bana laien.. Kuch configuration dali h is main main ny. Email ka password ghalt h main slack pe batata hn..

Note

Remember to update these settings in .env

MAIL_DRIVER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=465
[email protected]
MAIL_PASSWORD=your_password
MAIL_ENCRYPTION=ssl

Replace [email protected] and your_password with your email and password.

Also remember to disable 2 way authentication for your email. Otherwise it will not work.

Hello Zeeshan, brilliant project mate, congrats I created this issue just to contact you anyway, I clone your repository and updated the whole system to the latest version of Laravel by setting the entire authentication system to Laravel 6 defaults.

I also updated the controllers, but did not have the opportunity to update the bootstrap to the latest version, I saw that you still use many classes from the old version on the blades. if you want i can send you the updated version.

Regards