TODO

---

• coupe with the stuffs for on-perm
• update the documentation

---

As building the image-server testing docker image plotly/testbed is similar to the on-perm. I am thinking about:

• integrate all processes into buildly

the advantage is that, all docker images building processes will be on buildly, since some ugly workaround, I may need the presence of streambed code repo.

The procedure of building testbed docker image:

1. create a baseimage

• xvfb

  • remove /tmp/.X99-lock before xvfb restart (xvfb exceptionally failure left the file, need to be removed for next start)

• Rsyslog

  • https://blog.logentries.com/2013/12/how-to-configure-rsyslog-with-any-log-file-agents-bad-no-agents-good/
  • http://nginx.org/en/docs/syslog.html (default local7)
  • https://techpunch.co.uk/development/how-to-ship-logs-with-rsyslog-and-logstash

• pylint and astroid issue

  pylint-dev/pylint#720

ImageServer:

• PLOTLY_IMAGE_SERVER_3D_DISABLED in image_server templates/nw-wrapper.sh

http://mirror.its.dal.ca/apache/tomcat/tomcat-7/v7.0.65/bin/apache-tomcat-7.0.65.tar.gz

Django cache

https://docs.djangoproject.com/en/1.7/ref/contrib/staticfiles/#manifeststaticfilesstorage

http://www.server-world.info/en/note?os=CentOS_7&p=haproxy

https://github.com/FloeDesignTechnologies/ansible-haproxy/blob/master/tasks/configure.yml

J:

• https://www.linkedin.com/comm/jobs2/view/92500900?refId=4a1e74e0-0f75-4370-8f0d-835514ff2248&trk=eml-jymbii-organic-job-card&midToken=AQECR5tODXMRGw&trkEmail=eml-jobs_jymbii_digest-null-27-null-null-hblah~iiqbn4vf~rz