[Gambas-user] "New" gambas-basic.org website

[Christof Thalhofer]

Am 12.02.2018 um 01:47 schrieb Adrien Prokopowicz:

>> If we generate real load, I think we could pay it then. The only thing
>> that creates much traffic IMO are the downloads and they are on Gitlab.
> 
> Would there be any limit on the bandwidth for these servers ?

Yes, sure. There is alway "any limit" and if it is the limit of the
cable. HS donates the Space used and the bandwidth to the Gambas
community. So there is nothing to worry about. They would tell us, if
they would not be able to donate it any more.

Are you able to tell the traffic of gambaswiki.org?

> I'm not concerned at all about CPU or disk load. If your servers have 
> more than 500KiB of RAM, then all of it would be in filesystem cache, so 
> it should be loaded and sent over preeeeetty fast. ;-)

The server has 4 CPU and 10 GB Ram:

top - 08:12:35 up 36 days, 10:12,  4 users,  load average: 0,18, 0,10, 0,07
Tasks: 332 total,   1 running, 284 sleeping,   0 stopped,   1 zombie
%Cpu(s):  0,7 us,  0,2 sy,  0,0 ni, 97,2 id,  1,5 wa,  0,0 hi,  0,1 si,
0,2 st
KiB Mem:  10236388 total,  9498088 used,   738300 free,      216 buffers
KiB Swap:  4190204 total,      768 used,  4189436 free.  6246236 cached Mem

>> So: Do only rewrite history that you have not committed. Never rewrite
>> history that is public! And do not store passwords or private keys in
>> the repo.
>>
>> You can fuckup a lot of other's work by changing history that others
>> depend on ... !
>>
>> This is different from SVN!
> 
> So it wasn't really a joke then. ;-)

Ok. I give up ;-)

> Of course, rewriting the history is basically breaking the commit chain, 
> and these things tend to not go smoothly for other collaborators. :-)

So it simply should not be done.

>> Are you the one who is responsible for the current website of Gambas?
>> Then please send me a private mail with a public ssh key.
> 
> I am not. Benoît is pretty much in charge of everything, I am just 
> helping out now and then. ;-)

Ok. So it he wants to, he can write me a mail then I can create the user
for a website. I got his key already.

>>> The only problem for now is that the HTTPS site doesn't really work,
>>> since the inner frame loads gambaswiki.org in plaintext, and browsers
>>> (rightfully) block mixed-content requests. Fixing it requires deploying
>>> HTTPS on gambaswiki.org, which we should do at some point, but it's not
>>> too much of a deal for now.
>>
>> This is a very ugly construction and can eventually lead to downranking
>> in search engines.
> 
> I am pretty sure it already affects ranking, but yeah it is something 
> that should get fixed soon, especially considering wiki/bugtracker 
> passwords are being sent in plaintext over the wire …
> 
> (Firefox is actually shouting at me for this every time I log in the 
> bugtracker or wiki).

Chrome will deny access to http per default in the future. They will
handle it the same as self signed certs ...

>> At HS we install free https certificates automatically from
>> https://letsencrypt.org/.
> 
> Let's encrypt is the best. I set it up on pretty much every single 
> project of mine (including the Gambas Playground), and it's quite 
> awesome! :-)

It becomes ultra mightiy then ... I am not really sure if I like that at
all ...


Alles Gute

Christof Thalhofer

-- 
Dies ist keine Signatur

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20180212/84bb0452/attachment.sig>