Welcome Guest. Please Login or Register  
Client Area  |  Softaculous Cloud  |  Calendar  |  Quick Links  |  
   


You are here: Index > Webuzo > General Support > Topic : Fossil installation type?



Threaded Mode | Print  

 Fossil installation type? (3 Replies, Read 18510 times)
optsoft
Posted on # December 30, 2013, 10:32 pm
Group: Member
Post Group: Newbie
Posts: 38
Status:
Hi,

I was pleasantly surprised to find that Fossil version control system already ships with Webuzo along with the common ones like svn, git etc.

It looks very impressive from its description and details on its website.

I want to know which one of the 4 methods is used to run the fossil that is installed via webuzo - I am asking before trying because I do not want a conflict to arise on port 80, 8080, and 443 because "fossil ui" uses those ports potentially.

Fossil standalone can only be accessed as http://127.0.0.1/... so I think that is not how it is configured, am i right?

The best way for it to be configures would be as CGI in the single user's /home/user/cgi-bin with a simple 2-line script.
See Option 3 on this page: http://www.fossil-scm.org/index.html/doc/trunk/www/server.wiki

However, as long as conflicts are managed, I have no issues with any type of fossil configuration :-)

This page is why I think fossil could be very useful :
http://www.fossil-scm.org/index.html/doc/trunk/www/selfhost.wiki

So which type of install is it, option 1,2,3 or 4?

Thanks in advance,
/optsoft
IP: --   

Fossil installation type?
valley
Posted on # December 31, 2013, 5:20 am | Post: 1
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:
Fossil is only installed with the binary located at /usr/local/apps/fossil/fossil

You can configure as per your requirements.

Edited by valley : December 31, 2013, 5:20 am

-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

Fossil installation type?
optsoft
Posted on # January 2, 2014, 2:47 am | Post: 2
Group: Member
Post Group: Newbie
Posts: 38
Status:
Quote From : valley December 31, 2013, 5:20 am
Fossil is only installed with the binary located at /usr/local/apps/fossil/fossil
You can configure as per your requirements.

Hi,
I would like to report that I successfully installed fossil and create a repo and wiki with minimal effort.
Since he single fossil binary file (no libs, no so files, nothing, beauty of fossil) is at /usr/local/apps/fossil/fossil, which is not in the standard installation db of centos,
Code
$ fossil --help
, 
Code
$ whereis fossil
and
Code
$ man fossil
produce no results.
This does not mean fossil does not work.

Simply create an alias in your ~/.bashrc to point "fossil" to "/usr/local/apps/fossil/fossil" by adding the line below at the end of the file :
Code
$ nano ~/.bashrc
...
alias fossil='/usr/local/apps/fossil/fossil'


Then, preferably make a directory outside of public_html (naturally, for security of your fossil data file) like this
Code
$ cd
$ mkdir repos
$ cd repos


Now make a test fossil repo:
Code
$ fossil init mytest

This will give you a user name and password. Note down every bit of that information

Check if the repo file is made:
Code
$ ls -hal



Then as detailed on this page - http://www.hwaci.com/cgi-bin/fossil/doc/tip/www/server.wiki#cgi -
make a plain text file named 'repo' with the following contents
Code
#!/usr/local/apps/fossil//fossil
directory: /home/username/repos
notfound: http://url-to-go-to-if-repo-not-found/


This will be your cgi script, so it must be executable:
Code
$ chmod +x repo


And it must go to the cgi-bin directory:
Code
$ mv -v repo ~/public_html/cgi-bin/


That's it.

Now check if it works:
http://domain.com/cgi-bin/repos/mytest

This should bring up a login screen.
Enter the admin user and password that was displayed when you ran the
Code
fossil init mytest
command.

It is wiser to make a habit of using https, so use https://domain.com/cgi-bin/repos/mytest instead.

Done.

Now you have a source code control system, a issue tracker, and a wiki, all in one app, running from one single binary file named fossil.
The DB file is a standard sqlite db file so your data is never lost - you could query it with any SQL query tool which supports sqlite.

Moving your repo, wiki and issue tracker to another place is as simple as copying 1 file - the mytest.fossil file.
Backup is simple - copy / download one file and you are done.

Fossil is a worth a try if nothing else. Give it a go.

/optsoft
IP: --   

Fossil installation type?
valley
Posted on # January 2, 2014, 5:30 am | Post: 3
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:

Thanks for the helpful quick tutorial.

Cheers \m/

-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is April 29, 2024, 4:03 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 10  |  Page Created In:0.025