example-app | Karafka WaterDrop and Sidekiq backend example application | Pub Sub library

First of all you should create a folder called projects inside your home directory, then, go into that folder and execute sudo curl -s https://laravel.build/example-app | bash

You could also do sudo su and then curl -s https://laravel.build/example-app | bash

you need to pass route name to route method

Your error message seems to be an error generated Composer. The documentation for composer seems to imply that any version >= 5.3.2 is sufficient src. However, with PHP 8.1 not even being in Alpha until June, I should imagine it's safe to say there will not be official support for this for some time.

I did do a quick search for your error and got this article which states that one of the breaking changes that 8.1 introduces is passing null to a function that is not nullable. Official PHP Docs for strpos() indicate that none of the 3 arguments in strpos() are nullable, and thus what was 'allowed' in previous versions due to scalar types is no longer allowed for internal functions in 8.1, so you'll likely need to wait for Composer to officially support 8.1.

Even if you do fix Composer you're still using an unsupported version of PHP for Laravel. From their git the composer.json file specifies

This is not a cmake-related error, it's just how the library was implemented. I do not know why, but it appears that the specialization of T* at::Tensor::data const with T = long long was forgotten/omitted.

If you want to get your signed 64-bits pointer, you can still get it with int64_t:

What Im suspecting is that the puma gem version ( probably > 5.0+) that you are using doesnt support --daemon option.

This was highlighted in the capistrano-puma documentation. The puma cli command line parser will throw error as --daemon wasn't one of the supported option. You can check your Gemfile.lock for your puma version to verify this.

In fact, the capistrano-puma doesn not stop you from using puma with version higher than 5.0. However, the gem user is responsible for the plugin compatibility requirement.

First of all, repository is just a thin layer on top of EM (an extension point if you want), that bares the entity name so you don't have to pass it to the first parameter of EM method (e.g. em.find(Ent, ...) vs repo.find(...).

Then the contexts - you need a dedicated context for each request, so it has its own identity map. If you use RequestContext helper, the context is created and saved via domain API. Thanks to this, all the methods that are executed inside the domain handler will use the right instance automatically - this happens in the em.getContext() method, that first checks the RequestContext helper.

https://mikro-orm.io/docs/identity-map/#requestcontext-helper-for-di-containers

Check the tests for better understanding of how it works:

https://github.com/mikro-orm/mikro-orm/blob/master/tests/RequestContext.test.ts

So if you use repositories, with RequestContext helper it will work just fine as the singleton repository instance will use the singleton EM instance that will then use the right request based instance via em.getContext() where approapriate.

But if you use manual forking instead, you are responsible use the right repository instance - each EM fork will have its own one. So in this case you can't use a singleton, you need to do forkedEm.getRepository(Ent).

Btw alternatively you can also use AsyncLocalStorage which is faster (and not deprecated), if you are on node 12+. The RequestContext helper implementation will use ALS in v5, as node 12+ will be requried.

https://mikro-orm.io/docs/async-local-storage

Another thing you could do is to use the RequestContext helper manually instead of via middlewares - something like the following:

@sheydan you should install docker before launch command-line. If you don't know how to use DOCKER. Refer to documentation of Laravel https://laravel.com/docs/8.x there is lot of method instead of docker.

I don't think my solution is complete or correct, but I figured I'd post it in case it inspires any ideas, I'm stumped. I have run into the exact dilemma, almost seems like a design flaw..

I followed this MongoDB full example and named it main.py

At this point my app does not work. The server starts up but result results in the aforementioned "attached to a different loop" whenever trying to query the DB.

Looking for guidance, I stumbled upon the same "real world" example

In main.py added the startup and shudown event handlers

When you modify a .env file, you need to restart the React environment.

1. Stop the React server.

2. Add the following line to your .env file :

   REACT_APP_BASE_URL="https://example-app-name.com"

3. Be sure to import dotenv where you use the REACT_APP_BASE_URL variable: require('dotenv').config()

4. npm start OR yarn start