Add a memcached docker container to the test staging environment
Staging is using memcached as cache. Simulate the same behavior in the local testing environment.
Merge request reports
Activity
Jenkins job DGQL/gitlab-builds #190 succeeded .
See Console Output and Coverage Report for more details.No, this is for
make run-wsgi-docker
to run without any other local setup (like installing memcached).This make target will still require access to SWH internal services to access storage though. This behavior is same as that in staging and prod, where hosted services are accessed over the VPN and the memcached is a dedicated one.
Edited by Jayeshoh, now I get your question. Thanks :). I never tested this actually, this was created as a dummy placeolder for vincent to create a staging config. Now it will work perfectly. Or I did test this with another target
run-wsgi
where it is connecting to localhost.Edited by JayeshThere is an issue now,
run-wsgi
will fail. Let me see what I can do with that.Edited by Jayesh
You should also update the
swh-graphql
service in the global docker environment (https://gitlab.softwareheritage.org/swh/devel/swh-environment/-/blob/master/docker/docker-compose.graphql.yml). There is already amemcache
service used by the webapp, you can target it too for graphql.
added 1 commit
- 8c2f5207 - Add a memcached docker container to the test staging environment
Jenkins job DGQL/gitlab-builds #191 succeeded .
See Console Output and Coverage Report for more details.