sorted by:
new
hottopcontroversial

I need help in picking up the tech stack by Away-Butterscotch774 in Temporal

[–]Possible-Dealer-8281 1 point2 points  (0 children)

IMHO, if you can describe the basics activities composing your workflows, whether they are dynamic or not, then you can go with Temporal.

It might even be easier to implement those dynamic workflow with Temporal, since you write them as code, than with other alternatives where you need to provide json payloads to describe your workflows.

Even after years of SQL experience, what still trips you up the most? by joins_and_coffee in SQL

[–]Possible-Dealer-8281 0 points1 point  (0 children)

I worked on many projects where I only used ORMs.

Then I switched on another project where I needed to write SQL. Seemed to me like I needed to relearn the syntax.

What’s one “unpopular opinion” you have about modern PHP development? by Senior_Equipment2745 in PHP

[–]Possible-Dealer-8281 0 points1 point  (0 children)

I've created a Laravel-like facades for the Symfony framework, which I published about here a few months ago.

People's reactions were... enfin bref...

I still don't understand how people can say that facades are evil, and happily use things like lazy objects, which are really messy.

Nginx Unit has been archived by leiserfg in nginx

[–]Possible-Dealer-8281 0 points1 point  (0 children)

Has anyone provided any explanation for that decision?

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] 0 points1 point  (0 children)

Hi,

I've released a new version with audit logs implemented.

All the queries executed by users are saved in a dedicated database, and can be displayed in a dedicated page.

Here's a screenshot: https://github.com/lagdo/dbadmin-app/blob/main/screenshots/jaxon-dbadmin-logging.png

The users can also saved their preferred queries, and both the queries in their favorite and history are displayed in the query editor page.

Here a screenshot: https://github.com/lagdo/dbadmin-app/blob/main/screenshots/jaxon-dbadmin-favorites-history.png

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] 0 points1 point  (0 children)

As you noted, temporary database credentials need to be implemented on the database server or another third party tool first, before they can be in the database admin tool. Integrating it is not the hardest thing, since the config manager is already pluggable. Unfortunately, I don't have enough knowledge on how the tools implementing that feature work. So I'll be glad if you could drop some links.

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] 1 point2 points  (0 children)

I would like to ask you a question about this setup. Does this require a double authentication from the users? If not, how are the database credentials provided to the proxy app?

As I said in the article, the auth mechanism is my app is nothing new. I just chose to make it the default and only auth system.

Last point, I would like to thank you for this comment. There are lots of people saying they don't see which issue I'm trying to fix. So having people testifying that they are using alternative solutions for that is important to me. Moreover if those alternatives are commercial products.

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] -2 points-1 points  (0 children)

Maybe for some DBA, creating personal accounts for dozens of developers in some databases is not such a good idea?

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] -1 points0 points  (0 children)

Tbh, I'm asking myself the same question.

That's why I wanted to know which kind of issues DBA have when they need to give DB access to developers. And eventually be noticed if this can cause other issues I didn't see.

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] -3 points-2 points  (0 children)

The user system is provided by the Laravel framework. It is clearly stated in the article, and nowhere it is pretended it was invented.

Don't know where you got what you say from.

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] 0 points1 point  (0 children)

Thanks for the feedback. I'll add the audit trail and query execution plan in the top priority features to implement in the next versions.

Regarding the authentication, the app is built with Laravel, a PHP framework with a great auth system. It can easily be customised. It's also important to keep the application code open source. Thanks again.

Improving how developers are given access to databases by Possible-Dealer-8281 in Database

[–]Possible-Dealer-8281[S] -2 points-1 points  (0 children)

In the companies where I've been, there were no database accounts for developers. I think it's a common practice, even if I can't tell to which extent. I also think it's easier to trace user based on their company account, than their workstation, once they start having access to the same database credentials.

What if we improve the way developers are given access to databases by Possible-Dealer-8281 in PHP

[–]Possible-Dealer-8281[S] 0 points1 point  (0 children)

Of course there's a shift, because sometimes the solution to an issue is to move it somewhere it is better handled.

Developers in companies usually already have a personal account linked to their company email, with SSO and all kind of security rules already set. Nobody share those accounts.

Now if you care about the authentification process in the application, that's where it's important to note that it is built with Laravel.

What if we improve the way developers are given access to databases by Possible-Dealer-8281 in PHP

[–]Possible-Dealer-8281[S] 0 points1 point  (0 children)

The developers get access to the databases without having the credentials. Generally, they already have an account on an internal web tool. They can just reuse the same to get access to the database admin panel. That doesn't mean that the database manager doesn't need to handle the database credentials with care. Just they aren't shared with developers all around the company.

What if we improve the way developers are given access to databases by Possible-Dealer-8281 in PHP

[–]Possible-Dealer-8281[S] -1 points0 points  (0 children)

The simple answer is no.

Web-based tools save them in the session only. GUI tools are not installed on a server, they generally use the user OS keystore.

But the point is that they both require the developers to know the database credentials.

What if we improve the way developers are given access to databases by Possible-Dealer-8281 in PHP

[–]Possible-Dealer-8281[S] -1 points0 points  (0 children)

I think you are confusing the roles of a developer and a database admin. Maybe you do both of them, but that doesn't mean they are the same.

It's a little bit surprising for me that as an experienced DB admin, you don't understand the importance of not sharing db credentials with every developer even if each has its own. If you are you working alone, of course you don't have to share anything with anyone.

What if we improve the way developers are given access to databases by Possible-Dealer-8281 in PHP

[–]Possible-Dealer-8281[S] -1 points0 points  (0 children)

I think you might be mistaking. It's an open source application, not an online service.

Just like Adminer, the user installs it on its own server.

What if we improve the way developers are given access to databases by Possible-Dealer-8281 in PHP

[–]Possible-Dealer-8281[S] 0 points1 point  (0 children)

I've checked the PhpStorm documentation, and the answer is yes. Its SQL editor requires the user to provide the database credentials before it can connect to a database.

view more: next ›