Page MenuHomePhabricator

Work out a local development environment for Heritage API
Closed, ResolvedPublic


Right now, and besides what can be covered by PHPunit tests, we do not have much choice to test changes than merging, deploying and see things break… :-(

It’s been several instances where the lack of development environment led us to deploy incorrect code.

We would need a development environment.

Event Timeline

I have started something using docker-compose.

Change 291198 had a related patch set uploaded (by Jean-Frédéric):
Add local dev environment with docker-compose

I file T134565 as a blocker, because local dev cannot access Intuition as a NFS mount ; using it as a library would solve the issue.

Change 291198 merged by jenkins-bot:
Add local dev environment with docker-compose

Lokal_Profil closed this task as Resolved.EditedJun 23 2016, 4:45 PM
Lokal_Profil added a subscriber: Lokal_Profil.


Things to be broken out as bugs

  • statistics and statisticsct are not included in the dump so we cannot mount these (T138517)
  • Add a symlink to the toolbox (T138519)
  • cldr should be included (T138515)

Mentioned in SAL [2016-06-30T18:43:04Z] <JeanFred> Deployed latest from Git: 795a396 (T136351), 4c8d9e3, e09e3d7 (T138519), 7840307, 4bdddd0 (T138606)