| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Célestin Matte <celestin(dot)matte(at)cmatte(dot)me> |
| Cc: | PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] pgweb: Add ARCHIVES_FRONT_ADDRESS to allow configuration of archives |
| Date: | 2021-10-27 09:21:37 |
| Message-ID: | CABUevEwD_qbzgJdZCrFvrfLDM+QVwKW+1RWSkB-xh97Oi+UZ7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, Oct 26, 2021 at 4:34 PM Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
wrote:
> Hello,
>
> Domain of messages in pgweb's search is currently hardcoded as
> postgresql.org
> in templates/search/listsearch.html. This patch allows to use another
> domain
> for links to messages in archives in the search function.
> Since pgarchives' domain can differ from pgweb's one, a new variable is
> defined
> for that purpose instead of using SITE_ROOT.
>
This patch adds a new parameter ARCHIVES_FRONT_ADDRESS, which is then never
used. Instead it passes in ARCHIVES_SEARCH_SERVER into the templates.
I'm pretty sure that's not intentional? They should both b
ARCHIVES_FRONT_ADDRESS?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Célestin Matte | 2021-10-27 09:45:04 | Re: [PATCH] pgweb: Add ARCHIVES_FRONT_ADDRESS to allow configuration of archives |
| Previous Message | Magnus Hagander | 2021-10-27 09:19:46 | Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null |