Code Files location

[jamessmith]

VICIBOX 4.0.0 ISO | ASTERISK: 1.4.44-vici | VERSION: 2.6-375a | BUILD: 120831-1523 | CPU: i7-3770 | No Timing Hardware or Extra software | Hosted Server with core i7-3770 on ASUS P8H77-M PRO with 32GB RAM

We want to change some vicidial code to optimize it according to our needs. So I want to know all the locations of the code files. I think that all the code is under the following directories, but if I am missing any, please let me know
PHP files: /srv/www/htdocs
Perl files: /usr/share/astguiclient

Also if there is any github project, that I can fork, please let me know.

[williamconley]

code is downloadable via svn (better than github: you don't have to be open source to use the full version for free on your own server! No fee! LOL) check the vicidial wiki for svn code download usage.

there are also script files in /var/lib/asterisk/agi-bin
and /etc/asterisk
and a configuration file in /etc/astguiclient.conf

but it would be easier to use /usr/src/astguiclient/VERSION to find the install.pl file which is the script that "puts" all the files where they belong (that will definitely let you know you have all of them, as it is the master control of where they go)

ALL files are contained in /usr/src/astguiclient/VERSION before install.pl "distributes" them to their various locations.

handy:

Code: Select all

cd /usr/src/astguiclient/trunk
svn info

also be aware that there are documents in /usr/src/astguiclient/VERSION/docs and timed processes running in crontab -e for root and the Vicidial service which starts several applications (not the least of which being several screens that are required to be running their scripts for the system to function!).

Happy Hunting

Thanks, by the way, for posting your specs!

[jamessmith]

thanks william, I will check the install script. Regarding SVN, I am not sure if SVN allows forking. I think using SVN we can create branches, perform the change in code under the branch and later merge the branch back into the trunk. So basically the SVN branches are used to test new functionality and once satisfied we can merge the changes back to the main trunk and so the purpose of the branch finishes here. For another new functionality, we will create a separate new branch and so on.

on the other hand in GIT we can fork any repository and the fork can become independent. we will also be able to get changes from parent and merge them in the fork and vise versa. So forks can live and grow separately and can even become a different product.

Most of the changes we want are related to DB, while rest are regarding UI.

[williamconley]

Sounds good, we use git and SVN both. But SVN for all project storage and collaboration whereas we use git on an individual user basis (which is free) but not as a server (which is only free if all information is public). We don't support git as a server-based application because it is encumbered (not GPL, like Vicidial) when you want to use it as a Server. Does work great as a client or desktop application, though. Can't be beat.

https://github.com/plans

[jamessmith]

is it possible that I download the latest code from SVN repo to my server, and also setup SVN-server on my server on the code directory, and create a local branches. Perform all the required changes locally in different branches and then merge the branches in the local repo. Later when vicidial team release a new revision, I can merge my local-repo with the new revision?

[williamconley]

svn merging is possible, but complex. however if you are experienced with it ... of course you can. it's already on your server and unless The Vicidial Group stops publishing with SVN it will continue to be available via svn for later merging.

although you may want to find out which versioning software best handles "merge" and consider pushing the SVN into that software before you attempt the merge. and let us know how it goes.