typo3.org issueshttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues2021-08-19T13:24:05Zhttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/500Check infrastructure2021-08-19T13:24:05ZStefan BusemannCheck infrastructure* Check php-slow.log on extensions.typo3.org and on typo3.org
* Integrate Varnish for both sites* Check php-slow.log on extensions.typo3.org and on typo3.org
* Integrate Varnish for both sites_Ready for sprinthttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/378inconsistent browser caching2019-03-29T07:12:23ZHannes Strangmeierinconsistent browser cachingcheers folks,
i recently wondered why i didn't see new content on typo3.org (a colleague told me about something i couldnt find).
end of story was: i had an old version in my browser cache, so i had a look on why that was the case (sin...cheers folks,
i recently wondered why i didn't see new content on typo3.org (a colleague told me about something i couldnt find).
end of story was: i had an old version in my browser cache, so i had a look on why that was the case (since i didnt visit typo3.org for like a week).
in my point of view the max-age for the cache-control is too high (31 days for html):
cache-control: max-age=2678400, private
The exipres-date looks way better (1 day):
expires: Thu, 17 Jan 2019 07:27:54 GMT
That being said, IF a cache-control header with max-age or smax-age directive is send in the response, the expires date will be ignored:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires
So i would say setting max-age to 86400 would be the best way to go to make the settings consistent (and prevent people from missing out on new stuff on typo3.org :) )
greetings,
HannesSprint 3 (2019)Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/359General work on infrastructure2020-06-23T10:05:55ZThomas LöfflerGeneral work on infrastructureThese tasks shall be done on every project website:
**composer**
* Project extensions
* Move project extensions into separate folder :heavy\_check\_mark:
* Add composer.json files :heavy\_check\_mark:
* Symlink them into `typo3...These tasks shall be done on every project website:
**composer**
* Project extensions
* Move project extensions into separate folder :heavy\_check\_mark:
* Add composer.json files :heavy\_check\_mark:
* Symlink them into `typo3conf/ext/` with composer :heavy\_check\_mark:
* Secure Web package
* Install `helhum/typo3-secure-web` :heavy\_check\_mark:
* Rename `html` folder to `public` (Change Link to DocRoot on servers!) :heavy\_check\_mark:
**server**
* Use PHP 7.2 :heavy\_check\_mark:
* Update Solr to use up-to-date configuration files
* Support for using Secure Web package :heavy\_check\_mark:
**performance**
* Check php-slow.log on extensions.typo3.org and on typo3.org
* Integrate Varnish for both sites
* Make sure that all CEs on public websites are cached (no `*_INT` objects) :heavy\_check\_mark:
* 404 page is called with `?no_cache=1` :heavy\_check\_mark:
* 404 page is not giving header status 404 => status 404 is given on typo3.org, so :heavy\_check\_mark:
**new projects**
* Create project template in GitLab to easily create new t3o websitesSprint 1 (2020)Thomas LöfflerThomas Löffler2018-12-31https://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/146activate cron job / scheduler tasks2018-03-02T14:50:59ZStefan Busemannactivate cron job / scheduler tasks* [x] Random banner cron job
* [x] member import
* [x] SOLR
* [x] maintenance* [x] Random banner cron job
* [x] member import
* [x] SOLR
* [x] maintenanceRelease new.typo3.orgThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/76Integrate discourse into news2017-11-25T09:41:10ZThomas LöfflerIntegrate discourse into newsSprint 2017-11https://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/57Fix tests on stage.typo3.org2017-07-05T10:07:11ZThomas LöfflerFix tests on stage.typo3.orgFollowing tests are not running
- [x] Mail sending
- [x] Combining images
- [x] GDLibFollowing tests are not running
- [x] Mail sending
- [x] Combining images
- [x] GDLib5. Sprint (virtual)https://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/28Mails are not going out on proserver2017-05-30T08:10:49ZThomas LöfflerMails are not going out on proserverWhen testing mail forms and using the test mail sending in Install Tool, no mail is arriving.When testing mail forms and using the test mail sending in Install Tool, no mail is arriving.Sprint 2017-05 preparationThomas LöfflerThomas Löffler