The SQLite.org website, and the Fossil-SCM.org website (which is the
same server) have always run off of the "althttpd" webserver. I have
just put up documentation for this very simple but effective webserver
at
https://www.sqlite.org/docsrc/doc/trunk/misc/althttpd.md
If you prefer to run
On Feb 27, 2018, at 2:42 PM, Svyatoslav Mishyn
wrote:
>
> So, if I want at some point to replace file by a symlink,
> first need to remove that file, commit changes,
> and only then add a symlink, right?
I did just that for a file here just days ago using the 2.5
Hi,
it seems that when `allow-symlinks` option is enabled,
file which was already added cannot be overwritten by a symlink,
see a test.
mkdir test && cd test
fossil init .fossil && fossil open .fossil
fossil set allow-symlinks 0
cp ~/.ssh/default.pub . && fossil add default.pub && fossil ci -m
On Feb 27, 2018, at 10:55 AM, Agrawal, Ritika wrote:
>
> - Need to clean up the files manually as well
That’s consistent with the current default behavior of “fossil rm” as well, so
it’s correct until/unless that changes.
>- Purging happens
4caf2221c1050ab1cf07cf8616043
Both these ids are neither current checkout id nor parent id. Any ideas?
Thanks,
Ritika
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20180227/b46a39f5/att
On 2/27/18, Agrawal, Ritika wrote:
> Hi,
>
> I am trying to use the purge command available with fossil 2.5 release.
>
> Steps performed :
> 1. fossil purge files
> 2. fossil purge list
> 3. fossil purge obliterate
>
> After obliteration, the size of the repo remains
ChiselApp also uses Let's Encrypt
On Tue, 27 Feb 2018, Warren Young wrote:
On Feb 27, 2018, at 8:37 AM, Roy Keene wrote:
You don't lose support for TLS, since Apache supports TLS. It's just running
Fossil as a CGI -- this is exactly how ChiselApp works.
Compare
Hi,
I am trying to use the purge command available with fossil 2.5 release.
Steps performed :
1. fossil purge files
2. fossil purge list
3. fossil purge obliterate
After obliteration, the size of the repo remains the same. After trying to
commit the changes to the repo, I see the error :
On Feb 27, 2018, at 8:37 AM, Roy Keene wrote:
>
> You don't lose support for TLS, since Apache supports TLS. It's just running
> Fossil as a CGI -- this is exactly how ChiselApp works.
Compare Thomas’ post to the HOWTO I linked in my first post in this thread.
The largest
You don't lose support for TLS, since Apache supports TLS. It's just
running Fossil as a CGI -- this is exactly how ChiselApp works.
On Tue, 27 Feb 2018, Warren Young wrote:
On Feb 26, 2018, at 3:33 PM, Thomas Levine <_...@thomaslevine.com> wrote:
Since it seems that the only dynamic stuff
On Feb 26, 2018, at 3:33 PM, Thomas Levine <_...@thomaslevine.com> wrote:
>
> Since it seems that the only dynamic stuff is in PHP and fossil,
> I suggest using Apache mod_php and mod_cgi (contrary to Warren's
> suggestion), as I think the configuration will be easier.
Of course, but then you
11 matches
Mail list logo