Just a heads up, I just signed up for a new dedicated Core 2 Duo server, which will replace the virtual machine it's currently running on. Lots more power, lots more RAM, lots more disk space -- for about 30% more money. Yay!
Sometime soon I will be moving this site over to the new server. Because the nameservers will need to be changed and the database will need to be migrated, there will be some downtime, possibly up to a day.
Haven't decided on the day yet, but I work weekend nights so it could be around Christmas. I'm coordinating with Sue, since she'll have to update nameservers.
Also just a plug: Since I wouldn't mind the server helping to pay for itself, and it has much more capacity than I personally need, I'd be interested in hosting other sites on it. If you are looking for a place to host a site, drop me a PM with what you need and I can make you an offer.
The server is a Core 2 Duo with a gig of RAM (will put in more when/if needed), plenty of space, running CentOS 5 (Linux), and I'm open to installing various things on it, so I can go beyond the standard PHP/MySQL hosting environment.
I may consider free hosting for general purpose nonprofit Christian causes.
Moving to a new server
The plan is to move it today (Wednesday). I will take it down at some point today, Sue will change the nameservers, and I will put it on the new server.
It will be down most of the evening and night. Things will work sporadically until later Thursday when the new nameservers/DNS have propagated and everyone's local DNS cache has caught up.
It will be down most of the evening and night. Things will work sporadically until later Thursday when the new nameservers/DNS have propagated and everyone's local DNS cache has caught up.
0 x
We're here, but maybe some character encoding issue. Testing special characters in new posts ....
á é à ó ú ¿ ? ¡ ñ Ñ
Edit because I can't post a new post: I fixed the clock, which is I *think* the reason why I can't post. The flood timeout is 60 seconds, and I set the clock back. Apparently a stupid flood detection algorithm that doesn't detect clock changes.
á é à ó ú ¿ ? ¡ ñ Ñ
Edit because I can't post a new post: I fixed the clock, which is I *think* the reason why I can't post. The flood timeout is 60 seconds, and I set the clock back. Apparently a stupid flood detection algorithm that doesn't detect clock changes.
Last edited by micah on Thu Dec 27, 2007 11:14 am, edited 1 time in total.
0 x
-
Mountain Man
- Pethead Fanatic
- Posts: 1387
- Joined: Fri Oct 10, 2003 9:11 pm
- #1 Album: Wake-Up Call
- Pethead since: 1983
- x 266
-
adrinux
- Pethead
- Posts: 282
- Joined: Wed Sep 29, 2004 3:13 pm
- #1 Album: Wake-up Call
- Pethead since: 1999
- Location: BRAZIL/RS
- Contact:
accented characters problem
I'm very satisfied with the new server. things go much faster now.
But I've noticed some characters problem.
At the portuguese forum, the accented characters such as: á, ó é, ã, and so on... every accented character is not working properly, it seems like they are replaced with a '?'...
can anyone fix that?
But I've noticed some characters problem.
At the portuguese forum, the accented characters such as: á, ó é, ã, and so on... every accented character is not working properly, it seems like they are replaced with a '?'...
can anyone fix that?
0 x
To learn recursivity, first, you need to learn recursivity.
Para aprender recursividade, primeiro, tem que aprender recursividade.
Para aprender recursividade, primeiro, tem que aprender recursividade.
-
adrinux
- Pethead
- Posts: 282
- Joined: Wed Sep 29, 2004 3:13 pm
- #1 Album: Wake-up Call
- Pethead since: 1999
- Location: BRAZIL/RS
- Contact:
mmmm, it's strange... they worked fine here 
either accented chars are not working only at the portuguese forum or
the problem is with the old posts which must be saved on the server, there must be a mismatch between the old and the new character encoding.
either accented chars are not working only at the portuguese forum or
the problem is with the old posts which must be saved on the server, there must be a mismatch between the old and the new character encoding.
0 x
To learn recursivity, first, you need to learn recursivity.
Para aprender recursividade, primeiro, tem que aprender recursividade.
Para aprender recursividade, primeiro, tem que aprender recursividade.
Yeah I'm not quite sure what is causing that. I've verified that the old and new servers are serving the same character encoding. I wonder if it is a PostgreSQL issue -- in the transfer process I migrated from 7.4 to 8.1 and created a new DB. I'll poke around at that, but it might be too late to save encoding of old posts. 
0 x
Who is online
Users browsing this forum: No registered users and 94 guests