YATS

[license]() [GitHub issues]() [GitHub pull requests]() [GitHub contributors]() [GitHub forks]() [GitHub stars]()

DEMO

https://yats.mediafactory.de

Staff User:
Login: staff.user
Password: qwertz

Customer User:
Login: customer.user
Password: qwertz

Or use vagrant!

VAGRANT

howto:

$ cd vagrant
$ vagrant up

Wait! :-) Point your browser at: http://192.168.33.11 or for admin interface: http://192.168.33.11/admin

Staff User:
Login: admin
Password: admin

WHY JUST ANOTHER?

We used to use TRAC for a long time and were quiet happy. But every time, we wanted to customize it, it took us a long to rethink the way, trac was developed or find a plugin working with our version.
Today all our web projects are build on top of django. So it is much easier to change YATS and we are faster in adding new feateures. We think, we kept it simple in the backend, so it is still easy to modifie for people not familiar with the YATS source (as long as you know django).

KEY FEATURES

INSTALLATION

no pypi package yet!

needs: see requirements.txt AND all modules from modules folder

should need:
pyclamd (add TCPSocket 3310 and TCPAddr 127.0.0.1 to its config and restart)
memcache

There is a debian package which includes parts of all, but is very special designed for our usecase as we make no use of pip.

settings.py reads part of its config data from an inifile (see top of settings.py).

The project is splited into 2 parts:

Customization is done in the web module - e.g. add more ticket fields (models.py in web) besides the settings itself (settings.py and ini file). So far the app needs 2 folders (for logging and attachments as defined in the inifile). Make sure the webserver has write access to those folders.

ALTERNATIVE PACKAGES

https://www.djangopackages.com/grids/g/ticketing/