Moving the Vim Homepage on 26.09.2023

[Christian Brabandt]

Dear all,
as you all know, we have had quite a few issues with our current hosting
provider for the vim.org homepage. Therefore, I'd like to announce,
that we'll be moving to a new hoster on tuesday, September 26th, 2023.

I will set the database on the current OSDN instance at 20:00 CEST
(14:00 EST) o'clock to readonly mode and so should be the old homepage.
I'll also add a banner that this is the old homepage. Hopefully the
switch will be done fast enough, that nobody notices it and we can
finally continue to use the new homepage with proper database
connections and ssl certificates.

However, the code is at the same time switched from the current php 5
version to a new php 8 installation, which required a rewrite of some of
the php pages and sql queries. Hopefully everything will still work as
expected. The new IP address should then be 31.172.117.18

In case of any questions, please redirect them to the vim_dev mailing
list.

Finally, I'd like to thank a few people involved:

- First of all, I'd like to thank Marc Schöchlin, who offered to take
care of the new Vim.org homepage hosting and at the same time, spend
some considerable amount of time to rewrite the homepage to php8.

- I'd also like to thank Shuji Sado who supported us with the old
OSDN.net hosting.

- I'd also like to thank Jeff Chousterman and wavestack cloud for
offering the infrastructure of the vim.org homepage. This should give
us a modern and reliable base for the future.

- And last but not least, thanks to Stefan Zehl for maintaining the DNS
for such a long time.


With all of your support this wouldn't be so easily possible!

Thanks,
Christian

[Christian Brabandt]

Dear all,
the homepage has been moved to our new provider wavestack. It should be
much more stable and performant again.

There may still be some problems with the old php code, so if you notice
anything, please let me know and I'll fix it.

Best,
Christian
--
The fancy is indeed no other than a mode of memory emancipated from the order
of space and time. -- Samuel Taylor Coleridge

[Tony Mechelynck]

This is Tony Mechelynck and I'm using the mail interface because the
Google Groups interface lets me neither paste from the clipboard nor
attach a text file.

Indeed, when I browse to https://www.vim.org/ the ShowIP extension to
SeaMonkey tells me that I am at 31.172.117.18 which is the correct new
IP. The Vim Tips wiki, at vim.fandom.org, is also (as expected) still
accessible. However when I follow a link to a script, for instance
https://www.vim.org/scripts/script.php?script_id=2822 (a link found at
https://vim.fandom.com/wiki/Showing_the_ASCII_value_of_the_current_character)
which is supposed to be the page for the unicode.vim plugin, all I get
is a blank page (NOT Error 404) which (again according to ShowIP) is
supposed to come from 31.172.117.18. I have tried other script IDs, as
well as searched for scripts directly from the vim.org homepage,
always with the same (lack of) result.

Has the scripts database all gone to never-never land ? Or else, what
did I do wrong ?

FWIW, I am using a fiber connection in Brussels, Belgium, and at the moment,
* "systemctl status wicked" tells me
● wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled;
preset: disabled)
Active: active (exited) since Wed 2023-09-27 00:00:12 CEST; 1h 54min ago
Process: 1267 ExecStart=/usr/sbin/wicked --systemd ifup all
(code=exited, status=0/SUCCESS)
Main PID: 1267 (code=exited, status=0/SUCCESS)
CPU: 70ms

Sep 26 23:59:47 linux-tuxedo systemd[1]: Starting wicked managed
network interfaces...
Sep 27 00:00:12 linux-tuxedo wicked[1267]: lo up
Sep 27 00:00:12 linux-tuxedo wicked[1267]: eth0 up
Sep 27 00:00:12 linux-tuxedo systemd[1]: Finished wicked managed
network interfaces.
* "ifstatus eth0" tells me the following, which I don't understand
(except the first line saying that it is up):
eth0 up
link: #2, state up, mtu 1500
type: ethernet, hwaddr f0:2f:74:1d:e9:8a
config: compat:suse:/etc/sysconfig/network/ifcfg-eth0
leases: ipv4 dhcp granted
leases: ipv6 dhcp granted, ipv6 auto granted
addr: ipv6 2a02:a03f:64bb:3801:cfd8:dc79:7fe0:4d62/64 [auto]
addr: ipv6 2a02:a03f:64bb:3801:f22f:74ff:fe1d:e98a/64 [auto]
addr: ipv4 192.168.129.0/23 [dhcp]
route: ipv4 default via 192.168.128.1 [dhcp]
route: ipv6 default via fe80::6e3:1aff:febf:d672 metric 1024 proto ra
* If the above is only between my fibre modem and my computer, then I
have no access to the internal configuration of the modem.

Best regards,
Tony.