Managed by the Infrastructure Team and Dogfood Team, this is to have a daily test upgrade of most of our *.tiki.org sites. So anyone can check anytime how stable trunk (the next version) is with real world data. The name relates to our eat our own dogfood policy.
During the duration of the transition SVN to GIT we have a mechanism to synchronise our git repo (master) with our SVN repo (trunk). Here is how to check if SVN is up to date: https://dev.tiki.org/Git-and-SVN-combined-workflow#Status
http://next.tiki.org/ This is for tiki.org The cron job for next.tw.o is executed at noon and midnight my time (-6h to get NY time and -9h to get SF time). next.tiki.org is synchronised from Git
As of 2022-11-02, no extra password. But if one is added, it will be:
u: next
p: next
If branding is running on Tiki21 LTS, nextbranding.tiki.org should be Tiki24 LTS, as it's the next likely upgrade
http://nextbranding.tiki.org/ (Full upgrade from live site daily, code update without full rebuild of index every 30 min.) (Powered by Tiki Manager)
u: next
p: next
http://nextprofiles.tiki.org/ (Full upgrade from live site daily, code update without full rebuild of index every 30 min.) (Powered by Tiki Manager) As of 2022-03-03, we decommissioned, and will restore in 2-3 months on another server. This site is not so useful because next upgrade will be in 2024.
u: next
Which is why we have set up a continuous Pre-Dogfood Server. Yesterday's data with tomorrow's code (code in trunk). Ideally, this would be part of TRIM so everyone in the community could easily set this up for themselves, but it's not at this stage.
1- Run a new site ex.: nextdev.tiki.org
2- Daily update of code (from trunk)
3- Daily refresh of data (from live site)
The future-proof solution is Clone and Upgrade in Tiki Manager
Alternatively, some other code is here: https://sourceforge.net/p/tikiwiki/code/HEAD/tree/trunk/doc/devtools/update.dogfoodserver.sh
Use the following as per System Configuration. See also Divergent Preferences in Staging Development Production
; To avoid bots indexing the site and losing SEO over duplicate content preference.metatag_robots = "noindex, nofollow" ; Testing changes shouldn't spam people preference.feature_user_watches = n ; Make it obvious to everyone that this is not real data site preference.sitesubtitle = "Pre-dogfood test upgrade server. Data refreshed daily." ; Set error reporting to all (useful for debugging) preference.error_reporting_level = -1 ; Make error reporting available to all users, not just admins preference.error_reporting_adminonly = n ; Here are some less commonly used options. Just uncomment the prefs to be like above by removing the ; ; If you are using memcache in production, you probably want to deactivate for the pre-dogfood server, or at least change the memcache_prefix so the production and pre-dogfood server don't collide ; preference.memcache_enabled = n ; If you are using a Content Delivery Network (CDN), you want to make sure values are not the same in production vs pre-dogfood server ; tiki_cdn = "" ; tiki_cdn_ssl = "" ; If you want to prevent user registrations, uncomment below ; preference.allowRegister = n ; To close the site. Only users with tiki_p_admin permissions can log in. ; preference.site_closed = y ; Closed site message ; preference.site_closed_msg = "This is a development site, not open to the public"
Is enough metatag_robots enough? Or is modifying https://next.tiki.org/robots.txt also necessary ?
1) |
19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
2) |
Tiki birthday |
3) |
17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
4) |
21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
5) |
19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting |