Ziggy | Python application logging and collection framework | Networking library

Replace with your auth token

If you are not using Blade, or would prefer not to use the @routes directive, Ziggy provides an artisan command to output its config and routes to a file: php artisan ziggy:generate

The primary difference between htop and ps aux is that htop shows each individual thread belonging to a process rather than the process only - this is similar to ps auxm. Using the htop interactive command H, you can hide threads to get to a list that more closely corresponds to ps aux.

In terms of memory usage, those additional entries representing individual threads do not affect the actual memory usage total because threads share the address space of the associated process.

RSS (resident set size) in general is problematic because it does not adequately represent shared pages (due to shared memory or copy-on-write) for your purpose - the sum can be higher than expected in those cases. You can use smem -t to get a better picture with the PSS (proportional set size) column. Based on the facts you provided, that is not your issue, though.

In your case, it might make sense to dig deeper via smem -tw to get a memory usage breakdown that includes (non-cache) kernel resources. /proc/meminfo provides further details.

I'm calling this solved for now because my site started working.

it was extremely difficult to navigate since I had 6 months of work on a dev branch, and it worked via npm run watch. When I merged into master, npm run production loaded incorrectly--the styles were half there and half missing.

The solution was to downgrade from tailwindcss@1.9 to tailwindcss@1.4.

Along my way, I read something about postcss or something not working with the --no-progress flag which is on npm run production.

A person could try removing that flag, but I already downgraded tailwind so I didn't try that.

When you're in REPL, you need two consecutive blank lines to finish the statement. However writing code in REPL is quite cumbersome, as you can't easily edit/fix previously written code, so I'd suggest you to save anything you do into .py file, where you can edit the code more easily and then run the code via python ./myfile.py.

Why it should not be mixing?

You define Route::get('/{category}' and Route::get('/{tag}'. So if you open /1 in your browser it will always run the first route it is able to find that matches the pattern. So it is always running CategoryController@index yes?

Your routes should be:

You are using laravel 7, I think this package is not support in laravel 7, it will support in laravel 6

Is this:

The problem was the import in app.js