ReleaseEngineering/Applications/Mapper: Difference between revisions
(added links to docs from vcs-sync) |
|||
Line 7: | Line 7: | ||
= Deployment = | = Deployment = | ||
mapper only requires bottle to run. It's recommended to run inside a virtual environment | mapper only requires bottle to run. It's recommended to run inside a virtual environment | ||
Our current production deployment of mapper lives on cruncher under /home/buildduty/mapper. It listens locally on port 8888 (specified in mapper/app.py). The apache instance on cruncher is configured to forward requests to http://cruncher/mapper/* to http://locahost:8888/* (configured in /etc/httpd/conf/httpd.conf) | |||
The mapper process is managed by supervisord which will ensure it is started up if the machine is ever rebooted, or if the process crashes. (configured in /etc/supervisord.conf) | |||
= Mapper Data Source = | = Mapper Data Source = |
Revision as of 12:06, 22 February 2013
What is it?
mapper is a web application that converts hg revisions to a git revision using the hggit map files created as part of the repository conversion.
Source
mapper's source is currently hosted at https://github.com/catlee/mapper
Deployment
mapper only requires bottle to run. It's recommended to run inside a virtual environment
Our current production deployment of mapper lives on cruncher under /home/buildduty/mapper. It listens locally on port 8888 (specified in mapper/app.py). The apache instance on cruncher is configured to forward requests to http://cruncher/mapper/* to http://locahost:8888/* (configured in /etc/httpd/conf/httpd.conf)
The mapper process is managed by supervisord which will ensure it is started up if the machine is ever rebooted, or if the process crashes. (configured in /etc/supervisord.conf)
Mapper Data Source
This section describes (roughly) how vcs-sync provides the map files served by mapper.
The map files are generated and combined on the vcs-sync machines, then pulled onto cruncher and used by `mapper`. See the source and docs for vcs-sync for more details. (Especially the mapper support section.)
Note that the above docs will be integrated into the wiki after vcs-sync development stabilizes.