On Tue, Apr 5, 2016 at 11:08 AM, Scott Doctor <sc...@scottdoctor.com> wrote:
> I am starting yet another project, well an offshoot of a current one (like > I don't have too many already). This one I need to put some stuff on a > password protected page (usually using .htaccess) on my website so that > others on the project can have access to the files. So I am going to give > fossil a shot at being the content manager for this one. It looks like the > sqlite and fossil website are using fossil for doing such. I would like to > know how much modification and special code you use in addition to the > built-in fossil stuff. (referring mostly to the wiki and download pages) > The Fossil website is hosted by Fossil itself, using Fossil's configuration settings. As I recall, the "Downloads" paged is generated by a separate script, but you don't have to do that. Fossil's time line view can do something similar by displaying just commits with a particular tag, like, for example "Release". > > I have a GoDaddy shared server website account. Still trying to figure out > what I ftp to the page and what to configure to get a clean install of > fossil working on it. My website server account uses linux and has php 5.5. > I usually just make my web pages offline with a web page creator program in > html then upload them to whatever directory. But this one is more > complicated. was looking at using Drupal, but I think fossil might be a > better fit, if I can get it working on my website. > Fossil itself is just a single executable file. If your hosting service will let you run executables you upload to it, you can make Fossil work. Your hosting provider will have to tell you how to do that. Once you can run Fossil, it just needs a copy of the .fossil file containing the database that holds your pages and other files. There is a Fossil-based repository hosting site, chiselapp.org It has a frontend webserver with scripts that provide means to register new accounts and create or upload .fossil files. Otherwise, the webserver just passes through requests to a Fossil server for handling.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
