Admin/System Tools/Regenerate Views - Revision history

Drn@ecs.soton.ac.uk at 21:11, 4 March 2022

2022-03-04T21:11:29Z

← Older revision		Revision as of 21:11, 4 March 2022
Line 2:		Line 2:
	This page pertains to the '''Regenerate Views''' button in the '''[[Admin/System Tools\|System Tools]]''' tab of the '''[[Admin]]''' web page for your repository web interface.		This page pertains to the '''Regenerate Views''' button in the '''[[Admin/System Tools\|System Tools]]''' tab of the '''[[Admin]]''' web page for your repository web interface.

	The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested~~, if~~ the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.		The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested. If the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.

	If you actually want to regenerate browse view (menu and/or listing) pages use the '''[[API:bin/generate_views\|bin/generate_views]]''' script.		If you actually want to regenerate browse view (menu and/or listing) pages use the '''[[API:bin/generate_views\|bin/generate_views]]''' script.

Drn@ecs.soton.ac.uk at 21:08, 4 March 2022

2022-03-04T21:08:17Z

← Older revision		Revision as of 21:08, 4 March 2022
Line 4:		Line 4:
	The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested, if the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.		The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested, if the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.

	If you actually want to regenerate browse view (menu and/or listing) pages use the ''[[API:bin/generate_views\|bin/generate_views]]''' script.		If you actually want to regenerate browse view (menu and/or listing) pages use the '''[[API:bin/generate_views\|bin/generate_views]]''' script.

Drn@ecs.soton.ac.uk at 21:08, 4 March 2022

2022-03-04T21:08:08Z

← Older revision		Revision as of 21:08, 4 March 2022
Line 4:		Line 4:
	The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested, if the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.		The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested, if the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.

	If you actually want to regenerate browse view (menu and/or listing) pages use the [[API:bin/generate_views]] script.		If you actually want to regenerate browse view (menu and/or listing) pages use the ''[[API:bin/generate_views\|bin/generate_views]]''' script.

Drn@ecs.soton.ac.uk: Added page about Regenerate Views page

2022-03-04T21:06:40Z

Added page about Regenerate Views page

New page

{{system_tools}}
This page pertains to the '''Regenerate Views''' button in the '''[[Admin/System Tools|System Tools]]''' tab of the '''[[Admin]]''' web page for your repository web interface.

The '''Regenerate Views''' button updates the timestamp in the archive's <tt>var/views.timestamp</tt> file to the current time. This file is used whenever a browse view (menu or listing) page is requested, if the current (server-side) cache for this browse view page is older that the timestamp in this file, then the browse view page is regenerated. This is better than regenerating all browse view pages immediately. As a repository gets larger the time to regenerate all browse view (menu and listing) pages gets longer and can put a high load on the server. Also, by default the individual caches for browse view pages are set to 24 hours, so if the view pages were actually generated, there is a good chance many of their caches would expire before they were ever accessed.

If you actually want to regenerate browse view (menu and/or listing) pages use the [[API:bin/generate_views]] script.