| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> |
| Cc: | Henrik Uggla <Henrik(dot)Uggla(at)kristianstad(dot)se>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgAdmin in Docker: independent users storage |
| Date: | 2018-09-18 08:15:35 |
| Message-ID: | CA+OCxoyWkD4DfAU6E8mmwGj04jZR8iiTjPovHm2LC=jR_KoCzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi
On Mon, Sep 17, 2018 at 11:55 PM, Vladimir Ryabtsev <greatvovan(at)gmail(dot)com>
wrote:
> I see, so instead of pointing on some host/network directory (as I do in
> Henrik's image) I can just map this directory and override it inside the
> container.
> I think we need to mention this on the image's page
> https://hub.docker.com/r/dpage/pgadmin4/, I believe this is extremely
> useful, and even must be recommended for Docker deployment. Storing data
> inside a container is a way to instantly lose all data with every
> redeployment/image upgrade. One may also want to map
> directory /var/log/pgadmin to access logs in a convenient place.
>
It is mentioned there. The second example specifically says it uses a
shared config/storage directory.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2018-09-18 08:18:04 | Re: Re: how to be related with the schedule and step |
| Previous Message | jimmy | 2018-09-18 00:59:04 | Re:Re: how to be related with the schedule and step |