Operation log
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 30 2015
Would be nice to split them between dev and prod pool too.
This become annoying enough to raise priority.
Live at http://status.nasqueron.org/.
D96 takes care of the issue on nasqueron/phabricator, so we can decrease the priority.
Relevant log part of the docker build test run is available at P136.
I raise the priority, as APCu beta offers a PHP 7 version, so new build of rDPHAB isn't currently possible.
A lot of PHP applications nowadays use APCu to explicitely cache user-level objects.
In a nutshell the objective is to represent a CSV dataset in JSON, with the assertion the first line gives us properties names.
Note: I'm only going to speak about the front-end, as the fact we code the back-end in Node.js or in Python doesn't matter a lot to this question.
I think that the objective are to vague for making something concrete.
About the browser stack, two questions (more or less related)
- Does a framework bring a lot comparing to vanilla javascript for the use ?
- Which browser we intend to support. A good target would be in my opinion Grade A support by mediawiki
We also should follow http://www.sontek.net/blog/2011/05/07/turning_vim_into_a_modern_python_ide.html so we can offer a starting point to Tasacora contributors.
When Django were considered, I've noted http://www.jeffknupp.com/blog/2013/12/18/starting-a-django-16-project-the-right-way/ as relevant notes.
PhabricatorBotFeedNotificationHandler is broken in upstream since spring 2015.
Added to nginx main http configuration: large_client_header_buffers 8 1024k
By the way, the cause of this specific error instance is our nginx server returns a 414 URI too large error code. This issue is filled separately as T602.
Cleaned ommits selection
More precise comment
Nov 29 2015
Configuration superseded by T553: Docker now directly manages this disk.
Part 1 - Reclaim /dev/sdb1