Managed by the Infrastructure Team, Testing Team and Wishlist 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.
To check tomorrow's code (trunk) with yesterday's data, you can access the links below. Most of the year, these sites are running trunk, but during the release process, we run the upcoming version. Ex.: branches/9.x is used instead of trunk until dev.tiki.org moves from 8.x to 9.x
http://nextdev.tiki.org/ (updated 4 times per day)
u: next
p: next
http://nextdoc.tiki.org/ (updated 4 times per day)
u: next
p: next
http://nextinfo.tiki.org/ (updated 4 times per day)
u: next
p: next
http://nextthemes.tiki.org/ (updated 4 times per day)
u: next
p: next
http://nexttv.tiki.org/ (updated 4 times per day)
u: next
p: next
http://nextprofiles.tiki.org/ (updated 4 times per day)
u: next
p: next
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)
u: next
p: next
This one should be destroyed:
http://nextparserdev.tiki.org/ This is for the new Jison Parser (updated 4 times per day)
You need to clear all cache so the Jison Parser kicks in.
u: next
p: 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)
Use the following as per System Configuration
; 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 preference.sitesubtitle = "Pre-dogfood test upgrade server. Data refreshed daily." ; Set error report 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) |
21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
| 2) |
19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
| 3) |
Tiki birthday |
;){kind=link}
;){kind=link}