ZoneMinder is a free, open source Closed-circuit television software application developed for Linux which supports IP, USB and Analog cameras.
Go to file
Andrew Bauer b918a7be10
add support for fedora 27
2017-11-16 13:42:38 -06:00
.github Initial commit of github issue template. 2016-12-31 08:50:39 -07:00
cmake Merge pull request #896 from knnniggett/pod2man 2015-07-03 11:40:24 -04:00
conf.d reorganize zm config files (#1937) 2017-07-17 09:11:36 -04:00
db Introducing Maginon Supra IPC camera Controls and script (#1947) 2017-07-13 11:10:20 -04:00
distros rpm spcfile change 2017-08-23 08:48:11 -05:00
doc-pak Migrate svn to git 2013-03-17 00:45:21 +01:00
docs Fixes #1983 (#1989) 2017-09-28 18:03:39 -04:00
misc add compressing options to the sample logrotate config 2017-06-26 12:17:49 -04:00
onvif print the line out all at once, fixing the missing comma after fps. 2017-07-13 10:27:53 -04:00
scripts fix and move pod to bottom 2017-09-11 22:19:49 -04:00
src use int instead of unsigned int. Google code style says it's right, and it gets rid of a comparison warning 2017-08-22 09:47:30 -04:00
umutils Migrate svn to git 2013-03-17 00:45:21 +01:00
utils packpack - add missing $parms var 2017-08-21 18:50:30 -05:00
web initial commit to change color of web console systemstats (#1981) 2017-10-07 18:42:39 -04:00
.dockerignore Improve Docker build; reduce image size & layer count 2016-06-02 10:51:41 +10:00
.eslintignore Add eslint configuration files extending Google's rules 2017-03-18 00:02:17 -07:00
.eslintrc.js Add eslint configuration files extending Google's rules 2017-03-18 00:02:17 -07:00
.gitignore add comment at top, suggesting how to keep sorting maintained 2016-11-17 12:05:42 -05:00
.gitmodules Use the 3.0 branch of crud, compatible with cakephp 2.x 2015-09-29 17:22:43 -06:00
.travis.yml add support for fedora 27 2017-11-16 13:42:38 -06:00
AUTHORS Updated AUTHORS to reflect recent changes to the project 2013-09-09 10:06:36 -04:00
BUGS Point to the GitHub issues page for the list of current bugs 2013-09-09 09:45:29 -04:00
CHANGELOG.md spelling fixes 2016-12-29 10:31:05 +01:00
CMakeLists.txt arm neon-check "uname -m" if CMAKE_SYSTEM_PROCESSOR is not what we expect (#1966) 2017-08-21 12:02:28 -04:00
CONTRIBUTING.md Create CONTRIBUTING.md 2015-09-21 08:52:32 -05:00
COPYING update gpl 2 statement 2016-12-26 09:08:08 -06:00
ChangeLog Pointed the ChangeLog to the commits url 2013-09-05 11:32:48 -04:00
Dockerfile Add zip package to the docker image. Fix #1974 2017-08-26 17:16:17 +02:00
INSTALL Support SSL for mysql connections (#1965) 2017-08-14 10:30:42 -04:00
LICENSE Copied COPYING to LICENSE 2013-04-12 19:11:17 -04:00
NEWS Migrate svn to git 2013-03-17 00:45:21 +01:00
README.md Include Gentoo ebuild (#1993) 2017-10-04 07:41:44 -04:00
TODO update link to README to be README.md 2013-09-06 14:35:08 -04:00
cmakecacheimport.sh Support SSL for mysql connections (#1965) 2017-08-14 10:30:42 -04:00
code_of_conduct.md set email address to send complaints to 2017-06-06 16:03:10 -04:00
description-pak Doing my best to manually remove nextime's plugin architecture while keeping his other changes. 2013-08-13 09:43:23 -04:00
version Merge branch 'master' into filter_by_runstate 2017-06-06 20:34:47 -04:00
zm.conf.in Support SSL for mysql connections (#1965) 2017-08-14 10:30:42 -04:00
zmconfgen.pl.in update gpl 2 mailing address in source files 2016-12-26 09:23:16 -06:00
zmlinkcontent.sh.in zmlinkcontent: fix syntax error 2017-02-20 11:12:15 +02:00
zoneminder-config.cmake Merge branch 'feature-h264-videostorage' 2017-05-16 13:37:24 -04:00

README.md

ZoneMinder

Build Status Bountysource

All documentation for ZoneMinder is now online at https://zoneminder.readthedocs.org

Overview

ZoneMinder is an integrated set of applications which provide a complete surveillance solution allowing capture, analysis, recording and monitoring of any CCTV or security cameras attached to a Linux based machine. It is designed to run on distributions which support the Video For Linux (V4L) interface and has been tested with video cameras attached to BTTV cards, various USB cameras and also supports most IP network cameras.

Contacting the Development Team

Before creating an issue in our github forum, please read our posting rules: https://github.com/ZoneMinder/ZoneMinder/wiki/Github-Posting-Rules

Installation Methods

Building from Source is Discouraged

Historically, installing ZoneMinder onto your system required building from source code by issuing the traditional configure, make, make install commands. To get ZoneMinder to build, all of its dependencies had to be determined and installed beforehand. Init and logrotate scripts had to be manually copied into place following the build. Optional packages such as jscalendar and Cambozola had to be manually installed. Uninstalls could leave stale files around, which could cause problems during an upgrade. Speaking of upgrades, when it comes time to upgrade all these manual steps must be repeated again.

Better methods exist today that do much of this for you. The current development team, along with other volunteers, have taken great strides in providing the resources necessary to avoid building from source.

Install from a Package Repository

This is the recommended method to install ZoneMinder onto your system. ZoneMinder packages are maintained for the following distros:

If a repository that hosts ZoneMinder packages is not available for your distro, then you are encouraged to build your own package, rather than build from source. While each distro is different in ways that set it apart from all the others, they are often similar enough to allow you to adapt another distro's package building instructions to your own.

Building a ZoneMinder Package

Building ZoneMinder into a package is not any harder than building from source. As a matter of fact, if you have successfully built ZoneMinder from source in the past, then you may find these steps to be easier.

When building a package, it is best to do this work in a separate environment, dedicated to development purposes. This could be as simple as creating a virtual machine, using Docker, or using mock. All it takes is one “Oops” to regret doing this work on your production server.

Lastly, if you desire to build a development snapshot from the master branch, it is recommended you first build your package using an official release of ZoneMinder. This will help identify whether any problems you may encounter are caused by the build process or is a new issue in the master branch.

Please visit our ReadtheDocs site for distro specific instructions.

Package Maintainers

Many of the ZoneMinder configration variable default values are not configurable at build time through autotools or cmake. A new tool called zmeditconfigdata.sh has been added to allow package maintainers to manipulate any variable stored in ConfigData.pm without patching the source.

For example, let's say I have created a new ZoneMinder package that contains the cambolzola javascript file. However, by default cambozola support is turned off. To fix that, add this to the pacakging script:

./utils/zmeditconfigdata.sh ZM_OPT_CAMBOZOLA yes

Note that zmeditconfigdata.sh is intended to be called, from the root build folder, prior to running cmake or configure.

Docker

Docker is a system to run applications inside isolated containers. ZoneMinder, and the ZM webserver, will run using the Dockerfile contained in this repository. However, there is still work needed to ensure that the main ZM features work properly and are documented.

Contribution Model and Development

Pull requests are very welcome! If you would like to contribute, please follow the following steps.

  1. Fork the repo
  2. Open an issue at our GitHub Issues Tracker. Describe the bug that you've found, or the feature which you're asking for. Jot down the issue number (e.g. 456)
  3. Create your feature branch (git checkout -b 456-my-new-feature)
  4. Commit your changes (git commit -am 'Added some feature') It is preferred that you 'commit early and often' instead of bunching all changes into a single commit.
  5. Push your branch to your fork on github (git push origin 456-my-new-feature)
  6. Create new Pull Request
  7. The team will then review, discuss and hopefully merge your changes.

Analytics