dbx12

Now you build only one block wide windows.

Cave spider: let me introduce myself

Not an answer, but you don’t need an extension to defeat right-click blocking scripts: shift-right-click usually does the trick.

Damn, bought it back when only credit card was an option and it was $12 or something like that.

Great that it worked out, did you use apt remove or apt purge?

You might want to put your code in triple back ticks so it renders as code block :) Currently isn’t visible on some clients (boost for Lemmy in my case)

Looks like your php code is wrong, try this (and just this) for index.php

<?php
phpinfo();

You also had Test Text1 inside the php block which is a syntax error. Maybe that’s the cause why you don’t get anything.

Edit corrected the filename to lowercase extension.

You’re thinking about Schroedinger. Pavlov was the guy with the dogs and bells.

Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.

Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE part of your SQL command (or analog statement of the query builder)? No fucking thanks.

Yep, it’s a repost of this one.

One could even think this OP is an alt account.

There are some good points in it but the list feels poorly written as it contains very general tips which feel like fluff to increase the article length like:

Protect the client-side against attacks.

Or just wrong stuff like:

Validate all server-side input data.

If you can trust someone, it’s the server. You should validate data coming from the client on the server side.

Some things even contradict each other like

Implement strong authentication, such as two-factor authentication (2FA).

And

Use secure authentication mechanisms such as OAuth.

Assuming your app is an OAuth client, you have no say in how the identity provider identifies the user.

Good point, but even better than

Monitor file and source code integrity.

is having the application source code read-only, ideally owned by another user to avoid the confused deputy problem.

If all of those servers are yours (which they likely are, since you get ssh access), you can use one key for all. Using different keys would make one compromised key less problematic. But if someone was able to copy one file of your system, they can copy multiple files.

That resolves keeping track of things as well 😄

Yes the package pushes the notion “final is bad”. Throw both into the trash.

Ducking Medium again. No I don’t want an account with you. The article can’t be that interesting.

Just because one person said "final is bad", the Laravel fanboy herd is flocking to solutions like this. In my opinion, the package per se is not bad, but the unreflected, absolute statement "final is bad" is the problem.

I would recommend key based authentication for SSH connections. For the normal connection, the key pair is enough, if you want admin (root) access, you would use the command sudo which in turn requires a password. For creating a default admin account: Linux does this for you, it’s called root. You should create a personal user to work with in daily business and add it to the sudoers group (permits using the sudo command)

Proton Mail sounds quite promising to me

Make them non-admins and make the “difficult dashboard” admin-only. At least that is my way of doing it.

Docs is another topic I really don’t like about Laravel. Why don’t you have a simple API doc with available functions and their parameters instead of that blog-style documentation. And no, I don’t want to watch a video about how to use X, I want to know what functions I can call. Oh and don’t get me started on all their global “helper” functions.

Hey, I’ve came over from Reddit and thought I’ll introduce myself as well. As every programmer, I’ve started way too many pet projects and almost all of them are starving. In terms of framework, I prefer Yii2 over Laravel every day. I feel like Laravel provides you a dozen different (seemingly equally good) ways of doing something. You could say it’s lacking clarity or guidance for the developer.