rhizi/res, branch demoConnective intelligencehttps://git.yuv.al/rhizi/atom/res?h=demo2015-04-26T15:06:47Zrz_config: acl__singup__email_domain2015-04-26T15:06:47ZLV-426lv-426@taproot.org.il2015-04-26T15:06:47Zurn:sha1:f7d9984a6c6497bb0af3d46f5a9f7f0fecdaa9c9UI text changes for search and merge2015-04-26T14:08:35Zgarbashdor.garbash@gmail.com2015-04-26T14:08:32Zurn:sha1:7e375071ff687300c78ab1dd91a075e906b00674docker/fedora-single: adding missing Dockerfile2015-04-26T09:52:29ZAlon Levyalon@pobox.com2015-04-26T09:52:29Zurn:sha1:c1fe4ae32e161e2b9395ccb3b71a35cdb5dbbf47wip: neo4j multiplexing: config templates2015-04-25T20:53:23ZLV-426lv-426@taproot.org.il2015-04-25T20:45:58Zurn:sha1:73cd5fe97ea740b6f7ac67ccb2dbfbef0c69eb1bdocker changes: split neo4j and rhizi2015-04-25T18:05:19ZAlon Levyalon@pobox.com2015-04-25T18:01:07Zurn:sha1:a834ad073afc12fc5f329741026f2bf20b43a2da
changes:
- rhizi and neo4j use separate containers, linked via docker link
mechanism (environment files and shared bridge)
- means debugging is faster using docker (still quicker by a little
using run-local.sh / directly running python if no change to
css/client)
- rhizi docker now doesn't run deploy, it uses a volume from the
deployment, similar to production scenario. Image still has multiple
tools needed only for development (git, strace, ant, etc)
client: convert svg icons to png2015-04-25T18:05:19ZAlon Levyalon@pobox.com2015-04-25T17:57:45Zurn:sha1:d766ecbf7a64c09e324a239493523bbda7041659
while deploying a docker container both firefox and chrome refuse to
load same path svg (reporting 'image failed to load' but showing 200 on
the client, suggesting it is a behaviour implemnted after the HTTP
interaction is completed successfully), while they accept png. This is a
workaround. We already have other icons as png's, and we do not support
change in icon size, suggesting no down side to this right now. The svg
sources are left, and are actually still deployed (minor issue).
default rhizi-server changes: no root_path, no SERVER_NAME2015-04-25T18:05:19ZAlon Levyalon@pobox.com2015-04-25T17:42:55Zurn:sha1:65d0dd5c57b1dcfa12c90dfebc6d5a157aad65b9
root_path will then default to the parent of the deployed rz_server.py,
which matches our current deployment strategy, allowing running of
rz_server.py from any current working directory (i.e. removing the need
to do an additional change dir prior).
SERVER_NAME is a layering violation wrt any frontend servers and/or
iptable rules taking effect between the client and the server. Removing
it allows the server not to care about the hostname and portname visible
to the client.
client: drop rz_server_{host,port}, use document.location2015-04-25T18:05:19ZAlon Levyalon@pobox.com2015-04-25T13:57:10Zurn:sha1:aafae6f846f533cedc4eab1857aab97395a0be31
Since the client can be hidden from the server via multiple layers, be
they load balancers, proxies or iptable rules, it is simpler to not have
the server aware of those layers and have to inform the client of them,
instead use information the client already has.
docker: move Dockerfile to res/docker, leave scripts in src/local/docker2015-04-25T18:05:19ZAlon Levyalon@pobox.com2015-04-25T13:56:34Zurn:sha1:0a20324e01210b6654c5f4415efd53d44c2c5246rhizi-server.conf.example: fix mta-port2015-04-21T21:47:02ZAlon Levyalon@pobox.com2015-04-21T21:47:02Zurn:sha1:56be3fc33c3b815f664c4a8d2affea8af7c1f327