This is a test mail for some new list functionality that accidentally got
broken today.
Apologies, and please ignore this mail.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
ages are required)
* pgadmin-web (the web app, depends on pgadmin-core and adds whatever other
dependencies are necessray, drops a config file for webserver etc)
or am I thinking wrong?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
andidate for
> this which is well-maintained upstream, though, because of the
> single-process requirement. There's a bunch of simple-python
> appservers, but none of them are well-packaged and maintained.
>
>
I don't know how simple you consider uwsgi, but it's cert
> The Enterprise PostgreSQL Company
>>
>> On Wed, Aug 9, 2017 at 2:39 PM, Sarah McAlear
>> wrote:
>>
>>> Hi Hackers!
>>>
>>> We noticed that as of some time today (it worked this morning) we are
>>> unable to pull git.postgresql.org/git
it for us, but we did use https instead.
>
> Thanks!
> Matt & Sarah
>
> On Wed, Aug 9, 2017 at 6:19 PM, Magnus Hagander
> wrote:
>
>> Hi!
>>
>> Did that actually fix it?
>>
>> I've noticed a couple of other jobs complaining about the git se
gone if it uses the smart http mode,
which we didn't support until a few weeks ago, but do now.
> git:// is supported, and per the thread, Magnus did fix the issue seen. Is
> there any other reason to change it?
>
>
Security? In particular, MITM:ing initial connections etc.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
Looks like a simple copy/paste bug.
//Magnus
diff --git a/pkg/docker/README b/pkg/docker/README
index ba04dfa8..7d4ea890 100644
--- a/pkg/docker/README
+++ b/pkg/docker/README
@@ -38,7 +38,7 @@ This is the password used when setting up the initial administrator account to l
PGADMIN_ENABLE_TLS
--
This option also allow us
> to focus less on browser compatibility as the main target of our
> development will become Chromium which is the base of browsers like UC
> Browser, Vivaldi, Opera, Google Chrome.
>
Please don't ever give up browser independence for the *web* version of
on systems they're
> updating and using pgAdmin on. That last bit is important; many folks will
> continue to run production servers on RHEL/CentOS 6 for years, but how many
> are using them for client-side stuff or actively updating things like
> pgAdmin on them?
>
I doubt RHEL will very much be used on desktop systems all the way until
2024. But definitely still is in my experience, but it won't be used *that*
long. I still see it, but it's starting to go away, but it's the usual case
of large enterprises shifting platform and needing to certify a gazillion
little desktop apps and hardware gizmos before they can move...
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
ho are using Windows --
mainly as a workaround for the fact that the performance experience of the
desktop app on Windows was horrible.
On Mac I don't think I've seen anybody choose the server version if it's a
primary tool for them (some still have a shared pgadmin for
On Thu, May 21, 2020 at 1:08 PM Dave Page wrote:
> We see a non-trivial amount of automated build failures caused by git
> timeouts and Varnish cache meditation. This is only likely to get worse as
> we've automated so many different build configurations, and the PostgreSQL
> sysadmin team don't
t;
> That *is* impersonating the user..
>
> Kerberized services really should *not* be accepting a cleartext
> password to use to authenticate as the user against another service,
> which is why I'd strongly recommend against releasing with just
> 'phase 1' done
ng
to be the majority of the time. Or possibly even more efficiently,
create a custom etag and use If-None-Matches. If you make that etag be
say the version that the client has, it becomes very cheap to check
and you don't need to track any extra data.
--
Magnus Hagander
Me: https://www.ha
t;> in relatively short order, no? At least, I'd think it would make sense,
>> while people have developer environments set up and working with
>> Kerberos to go ahead and get that part done. All I'm saying is that the
>> 'phase 1' part really shouldn't be independently released, or if it is,
>> it should be *heavily* caveated that it is strongly discouraged for
>> people to run it in an environment where pgadmin and PG are in the same
>> Kerberized environment because it's not possible to set that up, with
>> just phase 1 done, in a manner which would avoid the pgadmin and PG
>> servers seeing the user's password.
>
>
> Phase 2 is scheduled to be done immediately.
\o/
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
On Tue, Jan 12, 2021 at 9:57 AM Dave Page wrote:
>
> On Mon, Jan 11, 2021 at 10:06 PM Magnus Hagander wrote:
>>
>> Hi!
>>
>> If I read the code correctly, pgadmin will (unless turned off) hit the
>> website to check the version.json file for updates *every
On Tue, Jan 12, 2021 at 5:59 AM Khushboo Vashi
wrote:
>
>
>
> On Tue, Jan 12, 2021 at 3:36 AM Magnus Hagander wrote:
>>
>> Hi!
>>
>> If I read the code correctly, pgadmin will (unless turned off) hit the
>> website to check the version.json
16 matches
Mail list logo
