Refactor with system-level installation and users repositories

[botherder]

Instead of a self-contained folder, I've been considering restructuring Viper so that it can be provided with an installation script (probably Python setuptools), so that the main executable scripts are dropped in /usr/bin/ and the rest is stored for example in /usr/share/viper/ while the binaries and projects are instead stored for example in $HOME/.viper/.

I would like some feedback before proceeding with such a radical change.

[jaegeral]

So storing binaries and projects in home dir is good also for backup purposes.

I wonder how users then can use their own scripts (e.g. new/custom modules)

It would also be very nice to include and consider to provide a service for api.py and web.py (if that is a seperate point we can make it an issue as well).

In the end every decrease of barrier to get hands on viper is worth to spend time.

Maybe for 2.0?

[kevthehermit]

I like the idea. While refactoring it might be worth looking at providing
full SQL Support. Projects is the major hurdle here.

[botherder]

Can you elaborate on what you mean with "full SQL support"?

[kevthehermit]

Allow for MySQL or PostgreSQL. I manually change the connection string on my instance but it doesn't support projects.

Need a switch DB or use a project prefix in the table structure