Re: disable create server
От | Khushboo Vashi |
---|---|
Тема | Re: disable create server |
Дата | |
Msg-id | CAFOhELeHDYxRdXsC8ysJ1xDkbwTnOvMUT60KQZ8_GncESU3E7g@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: disable create server (Pavy Manuel <Manuel.Pavy@cnes.fr>) |
Ответы |
RE: disable create server
|
Список | pgadmin-hackers |
Thank you all.
I try to deploy pgadmin4 on my company but I want to manage the connections (server in pgadmin) the users can create.
So, I've found the line 84 of pgadmin/dashboard/templates/dashboard/welcome_dashboard.html to disable the link :
<a href="#" onclick="pgAdmin.Dashboard.add_new_server()">pgAdmin saves server list per user.
You may need to keep that in mind.
Yes I’m aware of that
It seems like a reasonable request to me - for example, to stop students adding random servers to a shared instance of pgAdmin that they're only supposed to be using for coursework.
Agreed.
My need is different : I deploy pgadmin4 in an ansible role which deploy the following (inside the [ ] ) :
User ----> [ Apache ---> pgadmin ----> pgbouncer ] -----> postgresql backend
And I have a script for adding a server for a specific user which create a pool and add the server tuple in the sqlite3 db.
The benefit is :
- I can serialize the connections (some users open many, many tabs)
- users who do not close their connections are not a problem (thanks to the pgbouncer timeout)
- I can reserve some connection to the production chain
- I can monitor the pool
Since yesterday, I’ve found a (ugly) solution : in the ./pgadmin/static/js/generated/browser_nodes.js, I deactivate the Server action.
But the pretty way should be to create a dedicated profile (in addition of administrator and user).
Manuel Pavy
В списке pgadmin-hackers по дате отправления: