Re: [fossil-users] Problem with Fossil compilation on Windows

2017-01-23 Thread Richie Adler 
Jan Nijtmans decía, en el mensaje "Re: [fossil-users] Problem with Fossil
compilation on Windows" del 23/1/2017 08:02:41:

> Did you do a full clean before re-building? If not, the earlier built
> libz.a will not be built again.

I had, but just in case I did it again just now. Same errors.



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Using Fossil SCM with Master Repositories held on a Flash Drive ?

2017-01-23 Thread Warren Young 
On Jan 23, 2017, at 8:35 AM, Richard Hipp  wrote:
> 
> On 1/23/17, Warren Young  wrote:
>> 
>> Digital Ocean has a $5/month option that should be ridiculously overkill
>> (512 MB of RAM, 20 GB SSD) and since they do hourly pricing and have a
>> remote API, you could bring it up and down at need.  If you just schedule it
>> 8 hours a day 5 days a week, it would come to about $1.25 a month.
> 
> I don't know about Digital Ocean, but other ISPs charge you by the
> amount of time that your disk image exists, not the amount of time
> your VM is actually running.

True, but the Digital Ocean remote API lets you create and destroy whole VMs 
remotely.  With a scripting system like Vagrant[*] you could bring the VM up in 
the time it takes to get coffee going in the morning, and destroy it in the 
evening before the occupancy sensors in the office start turning lights off.

Or, just create a snapshot, download it, destroy the VM, recreate a fresh VM, 
upload last night’s snapshot, and revert to the snapshot.

[*] 
https://www.digitalocean.com/community/tutorials/how-to-use-digitalocean-as-your-provider-in-vagrant-on-an-ubuntu-12-10-vps

> price of 3 or 4 USB sticks, you could buy a Raspberry PI (or
> equivalent), stick it on your local network, and run a Fossil server
> on that!

The advantage of the public VPS is that you don’t create a potential 
island-hopping situation.

I’m totally happy to pay someone else to weather the script kiddie pounding.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Using Fossil SCM with Master Repositories held on a Flash Drive ?

2017-01-23 Thread Richard Hipp 
On 1/23/17, Warren Young  wrote:
>
> Digital Ocean has a $5/month option that should be ridiculously overkill
> (512 MB of RAM, 20 GB SSD) and since they do hourly pricing and have a
> remote API, you could bring it up and down at need.  If you just schedule it
> 8 hours a day 5 days a week, it would come to about $1.25 a month.

I don't know about Digital Ocean, but other ISPs charge you by the
amount of time that your disk image exists, not the amount of time
your VM is actually running.  So I'm not sure about the $1.25/month
option.  I suspect you'd need to pay the full $5/month.

>
> That’s around the cost of the USB sticks you’re going to wear through with
> the other plan.
>

Good point about comparing the cost to that of a USB stick.  For the
price of 3 or 4 USB sticks, you could buy a Raspberry PI (or
equivalent), stick it on your local network, and run a Fossil server
on that!

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Using Fossil SCM with Master Repositories held on a Flash Drive ?

2017-01-23 Thread Warren Young 
On Jan 20, 2017, at 8:01 AM, Richard Hipp  wrote:
> 
> On 1/20/17, Javier Guerra Giraldez  wrote:
>> 
>> chiselapp.com offers private repositories.
> 
> Or you can get a $10/month Linode (https://www.linode.com/pricing) and
> set it up as your private server.

Digital Ocean has a $5/month option that should be ridiculously overkill (512 
MB of RAM, 20 GB SSD) and since they do hourly pricing and have a remote API, 
you could bring it up and down at need.  If you just schedule it 8 hours a day 
5 days a week, it would come to about $1.25 a month.

That’s around the cost of the USB sticks you’re going to wear through with the 
other plan.

Put it behind TLS,[*] and it’s as secure as it probably needs to be.


[*] https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22907.html
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Problem with Fossil compilation on Windows

2017-01-23 Thread Jan Nijtmans 
2017-01-21 17:29 GMT+01:00 Richie Adler:
>>  Jan Nijtmans Thu, 19 Jan 2017 01:57:05 -0800
>> Try:
>> C:\Prog\MinGW\msys\1.0\bin\make.exe -e -f win\Makefile.mingw X64=1
>> FOSSIL_ENABLE_JSON=1
>
> Sadly, that didn't solve the issue. Same errors.
>

Did you do a full clean before re-building? If not, the earlier built
libz.a will not be
built again.

Regards,
   Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users