RateLimiting | Simple Python module providing rate limiting

Laravel runs Providers before the command on artisan commands, so its trying to $settings = Themes::get(); on RouteServiceProvider and failing, thus the error. For a temporary fix remove that code and then run the migrate command.

For a more permanent fix, you can check if the model/table exists before running the query:

The issue was because of a mounted disk which I had deleted and, upon doing so, learned that I setup the fstab wrong for that disk. This made the OS unbootable.

Solution was to delete the instance (but not the boot disk), create a temporary instance with the boot disk attached, fix the fstab, delete temporary instance, then create a new instance again but with the now-fixed disk as the boot disk.

Ok, shortly after posting we figured it out. Seems like a mount point has changed (I expect due to a linux kernel update) and we have not used the nofail option in /etc/fstab as described in the aws knowledge center, this caused the server to hang at boot.

Going forward we will also ensure we use UUID mounting so we are independent on the device naming in /dev/.

you don't define theme_settings variable in boot function do it like this:

Kong GUI (Manager) is part of the kong enterprise edition. If you are using kong community edition, Have a look at https://pantsel.github.io/konga/ and there are few others developed by community for long UI

Let's say we can create a new App\Http\Middleware\ThrottleRequests class which will extend original \Illuminate\Routing\Middleware\ThrottleRequests. And override the method getHeaders to your own that will return empty array.

You need to create a new StringContent per request. PostAsync will dispose the content.

When a request completes, HttpClient disposes the request content so the user doesn't have to. This also ensures that a HttpContent object is only sent once using HttpClient (similar to HttpRequestMessages that can also be sent only once).

Why do HttpClient.PostAsync and PutAsync dispose the content?

Figured I could post a snippet for reference of how this would look like in practice, using go-grpc-middleware WithUnaryServerChain and a unary interceptor.

The idea is to add a grpc.UnaryInterceptor to the server, which will be invoked with an instance of *grpc.UnaryServerInfo. This object exports the field FullMethod, which holds the qualified name of the RPC method being called.

In the interceptor you can then implement arbitrary code before actually calling the RPC handler, including RPC-specific rate limiting logic.

Socket.io attaches itself to your http server by inserting itself as the first listener to the request event (socket.io code reference here) which means it totally bypasses any Express middleware.

If you're trying to rate limit requests to /socket.io/socket.io.js (the client-side socket.io code), then you could create your own route for that file in Express using your own custom router with a different path and have your client just use the Express version of the path and you could then disable serving that file through socket.io (there's an option to disable it).

If you're trying to rate limit incoming socket.io connections, then you may have to modify your rate limiter so it can participate in the socket.io connect event.

Now that I think of it, you could hack the request event listener list just like socket.io does (you can see the above referenced code link for how it does it) and you could insert your own rate limiting before it gets to see the request. What socket.io is doing is implementing a poor man's middleware and cutting to the front of the line so that they can get first crack at any incoming http request and hide it from others if they have handled it. You could do the same with your rate limiter. Then, you'd be in an "arm's race" to see who gets first crack. Personally, I'd probably just hook the connect event and kill the connection there if rate limiting rules are being violated. But, you could hack away and get in front of the socket.io code.