EmilMoe

Thank you @ismaile

I'm trying to upgrade to Laravel 8, but Sentry keeps bugging me. Any ideas?

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for sentry/sentry-laravel ^1.9.0 -> satisfiable by sentry/sentry-laravel[1.9.0, 1.x-dev].
    - Can only install one of: guzzlehttp/guzzle[7.0.1, 6.5.x-dev].
    - Can only install one of: guzzlehttp/guzzle[7.0.x-dev, 6.5.x-dev].
    - Can only install one of: guzzlehttp/guzzle[7.1.x-dev, 6.5.x-dev].
    - Conclusion: install guzzlehttp/guzzle 6.5.x-dev
    - Installation request for guzzlehttp/guzzle ^7.0.1 -> satisfiable by guzzlehttp/guzzle[7.0.1, 7.0.x-dev, 7.1.x-dev].

From composer.json:

"guzzlehttp/guzzle": "^7.0.1",
"sentry/sentry-laravel": "^1.9.0",

SELECT TABLE_NAME, AUTO_INCREMENT
FROM   information_schema.TABLES
WHERE  TABLE_SCHEMA = '__DATABASE__'

This gives me the max ID in each table, I can add that to the next one before import. That might work.

For small databases yes. There are more than 10.000.000 records, so I'm not sure about that.

It's an idea yes, unfortunately, there are 30 tables and this would be a slow process.

Another option would be to write a custom importer, but that's not a small task either.

Yes, they are all the exact same structures

Sorry, I mistakenly clicked 'best answer', now I cannot remove that again.

I have an application that unfortunately has been allowed to grow on 4 setups. That's too much maintenance, therefore it must be converted into 1 SaaS setup.

Any good ideas on how I can merge those 4 databases where there will be a lot of duplicated IDs?

Wouldn't it make sense to build into the core?

Anyway I changed my approach a bit from @dimsav

if (env('APP_FORCE_HTTPS', false)) {
    URL::forceScheme('https');
}

\Route::has($routeName)

Yes I guess you are right that should be the most optimal solution.

My problem is when paging my API requests it happens rather often that an object which has a reference to another is intersected.

For example I call api/books/1 on that page I already loaded api/authors. But the author associated to Book:1 isn't in on the first authors page, maybe it indexes 10 per page and this is Author:20.

Now my selects and lists cannot properly display it as they cause a mismatch where the author isn't in the list.

My question is how this is best solved? I have played with some parameters such as &include=20 to force an extra added, but I feel it's bad design and then users could index everything by running many include queries.

I have made listeners for Spatie Backup, but the listeners are triggered twice. I can't see where the problem should be coming from, any ideas?

I register them as this:

if ($this->app->runningInConsole()) {
    if (class_exists(\Spatie\Backup\Events\BackupWasSuccessful::class)) {
        Event::listen(\Spatie\Backup\Events\BackupWasSuccessful::class, BackupWasSuccessfulListener::class);
    }
}

https://github.com/spatie/laravel-backup/issues/1060

SAML requires the server to do a double handshake (ACL). Does anyone know an article or package that provide an example how I can test this on my local setup?

That was it, fantastic.

I put them in as global, but I selected protected as I thought that was something to do with secret values. Now I looked into that, and it seems to not be the case, but some kind of protected branch, which I don't think I have set up, so that might be the issue?

I have set up some variables for my CI script at https://gitlab.com///-/settings/ci_cd

And I am trying to use them in .gitlab-ci-yml but it is as they are not parsed? If I put the content from the variables directly into the script, it works, but it fails when I refer them:

 $ npm-cli-login -u ${WEBIX_USER} -p ${WEBIX_PASSWORD} -e ${WEBIX_EMAIL} -r http://npm.webix.com -s @xbs
 /usr/lib/node_modules/npm-cli-login/lib/index.js:11
             throw new Error(err);
             ^

I read somewhere that it is intended that the variable name is displayed, but it doesn't change the fact that the login fails – and only when I refer variables, not when I hardcode the values.

I got it!

2 certificate files needs to be writable – not really easy to help me here as it's a custom error.

I got it!

2 certificate files needs to be writable – not really easy to help me here as it's a custom error.

I had this same error last week, stupid as I am, I already forgot how I solved it. I hope someone here can help me point how, what is going wrong?

It happens when a new environment is setup, so it's a fresh clone of my application.

I'm running Laravel 7.

 > @php artisan package:discover --ansi
    Illuminate\Contracts\Container\BindingResolutionException 
   Target class [hash] does not exist.
   at vendor/laravel/framework/src/Illuminate/Container/Container.php:809
     805| 
     806|         try {
     807|             $reflector = new ReflectionClass($concrete);
     808|         } catch (ReflectionException $e) {
   > 809|             throw new BindingResolutionException("Target class [$concrete] does not exist.", 0, $e);
     810|         }
     811| 
     812|         // If the type is not instantiable, the developer is attempting to resolve
     813|         // an abstract type such as an Interface or Abstract Class and there is

I found the solution here: https://stackoverflow.com/a/60274512/1743169

You need to downgrade your bootstrap to 4.3.1 Steps: 1. Remove bootstrap - npm uninstall bootstrap 2. Install Bootstrap 4.3.1 - npm install [email protected]

Any updates on when I can upgrade from that version Bootstrap?

I found the solution here: https://stackoverflow.com/a/60274512/1743169

You need to downgrade your bootstrap to 4.3.1 Steps: 1. Remove bootstrap - npm uninstall bootstrap 2. Install Bootstrap 4.3.1 - npm install [email protected]

Any updates on when I can upgrade from that version Bootstrap?

It seems to be the most error prone part of my application, I fixed a similar, though not the same, issue a month ago and now facing a new problem with npm run dev:

ERROR in ./resources/sass/app.scss
Module build failed (from ./node_modules/css-loader/index.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):

            @extend %responsive-container-#{$breakpoint};
                   ^
      Complex selectors may not be extended.
   ╷
31 │             @extend %responsive-container-#{$breakpoint};
   │                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   ╵

Have anyone managed to fix this?