2) 专栏中的专栏：
眼下只有“诗苑”里有进一步的分类 --“儿童”、“抒情”、“哲理”、“其它”。
接下来所有专栏都要进一步分类，比如“散文天地”里要分“游记”、“杂文”、
“随想”等，“文史哲”内要分“历史”、“哲学”、“文学评论”等。

[[i] Last edited by 伊甸园丁 on 2006-4-25 at 15:29 [/i]]

3) 空置文集、博客的处理意见：
文友的文集、博客建立后，30天内如果里面还没有任何内容，我们将考虑将其删除。
这样做是为了减少其它网友进入此文集、博客后什么都看不到的麻烦。所以，希望
文友在建立了自己的文集和博客后，在里面至少先放一篇文章。当然，某个空置文
集、博客被删除后，文友任何时候都可以再重建。

[[i] Last edited by 伊甸园丁 on 2006-4-25 at 15:29 [/i]]

4) MP3音乐库:
我们计划逐步建立一个MP3音乐库，供网友相互交流。当然首先我们需要搞清楚MP3文
件上传下载涉及的法律问题。违法的事情我们不做。

[[i] Last edited by 伊甸园丁 on 2006-4-25 at 15:30 [/i]]

海雨，你好：

谢谢你的新建议。你总是这样慷慨热情，让我们心怀感激。有关这个问题，我会问
问兰先生有没有简单的解决办法。

你知道我们几个都是业余写手，建立这个论坛是想让它帮助促进大家的写作。我一
直做UNIX系统管理员工作(thesunlover is actually the Sun Microsystems lover,
but unfortunately my lover is not blooming anymore, if not dying, haha)，
几乎没有编程经验(You don't think shell programming is programming, do you:))，
虽然对编程也有浓厚兴趣，问题是时间实在有限。他们几个距IT更远。所以在可以预
见的将来，我们可能都没有多余的时间和精力来学习如何customize论坛界面和功能。
兰先生将是我们值得信赖的outsouce，and I am the daily housekeeper。

作为系统管理员，我更关心的是网站的安全和持久稳定。随着用户的不断增加和文
件的膨胀，接下来需要做的工作是local backup。我们不能只依赖HOST的备份系统，
一是他们的backup policy不一定符合我们的具体需要，二是万一他们的系统出了事
故，我们不想为他们陪葬。这就是需要建立local backup系统的主要原因。

具体建立local backup系统，我初步决定选用VERITAS NetBackup(software)+Tape
Drive(hardware)+RedHat Linux(OS)。这方面你有什么具体意见和建议吗？

再谢！:)

thesunlover

> searain wrote:

"show or not show in 文苑首页"

I don't know DISCUZ. If DISCUZ has a way to let people to post to the article
collection or blog ONLY without post to the forum, then all your problems
solved. I think thesunlover already discussed this with Mr. Lan before. If
DISCUZ doesn't have the way to do so, every post posted to the articles
collection and blog has to be posted to the forum. Then you will have to
modify the DISCUZ.

There will be several options:

1) First, check the discuz site to see if there are any other people have
the same issues and they already have the free solutions you can use. But
you and Mr. Lan already did a lot custom changes of this system, other people'
s solutions may not be able to apply directly.

2) Otherwise, you may have to write your own codes to handle this issue.
The solution is add a boolean field to the table which DISCUZ uses to hold
the every post. If people select not to post to the forum, the new boolean
field will be set as "false". Then for every forum related pages, you will
modify the codes to check if the new boolean fields set as false, the post
will not be shown. - this will be too much and also it will make your system
not be able to be updated directly from future DISCUZ new version.

3) still use the boolean fields as 2), but that boolean fields doesn't control
any other forum pages. that boolean field only control if the post will
be shown in 文苑首页. Which means you may only have two places to modify.
First, when people post, you will have one more selection for them, "show
or not show in 文苑首页", then when the post added, and when the post is
added to the database, the "show or not show in 文苑首页" will be represented
by true or false of the new boolean field you added. Second, in the codes
to get the posts for "文苑首页", in the sql statement, you will add one
more condition, the new boolean fields has to be true.

海雨？是华夏的海雨吗？这里老朋友真多。

爱太阳，还是头一回听你说网名的来历。我不打叉了，你们接着讨论。

You are on a shared server, right? Or you are on a dedicated server?

As a matter of fact, I am a web programmer. Manage the Server and the back up is the "sideline". And manage the server or its back up usually will be through the shell command or shell programming (my headache and your area).

First of all, if you are on a shared server, what kind back up you can use may depends on what the ISP allows you or the ISP offers you. Check to see what is their back up policy.

Your site web pages not change very frequently anyway. I don't know very well about the DISCUZ. I think your site changes daily is only the MySQL database, and the files (image doucments) uploaded. And this site, I think the files uploaded is not very crucial, so the only crucial part is the MySQL database.

The ISP may already offers you a way (just a click somewhere in your account log in pages) to download your backup of the database.

If the ISP doesn't offer the back up tool.

[url] http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html [/url]

mysqldump is the command to backup the database. You either have to have the shell access to run the mysqldump. Or write a php statement to call mysqldump if you don't have the shell access.

[url] http://www.phpmyadmin.net/home_page/index.php [/url]

phpmyadmin is a web access database management tool for mysql. the ISP may preinstall it already or you can install it yourself. But since your site's database should be managed through the DISCUZ admin pages. phpmyadmin is not very useful for you.

phpmyadmin has the database backup tools. but some people warned that phpmyadmin database backup tool may not be very reliable.

Originally posted by [i]风信子[/i] at 2006-4-25 07:41 PM:
海雨？是华夏的海雨吗？这里老朋友真多。

爱太阳，还是头一回听你说网名的来历。我不打叉了，你们接着讨论。

Yeah, it is me. They found me from a thread about building a web site in HXWZ.

So how was your exam?

Ha! now I knew where thesunlover came from. And the web server boxes I used before, I bought from you guys. And you guys took my money and run. 🙂

[url] http://www.sun.com/hardware/serverappliances/raq550/ [/url]

The web servers I bought are cobalt raq 550. Sun bought the Cobalt. And just few months after I bought the sever from Sun, Sun dropped the whole coblat product lines. And then pretty soon, no updates, no supports and the web server Cobalt Raq 550 went out of date very soon. I only used the two servers for 1.5 years and then they became garbage. Now I rent a Unix box from ISP instead of colocation using my own server (100 dollars more every month, rent machine vs. use my own machine).

To make things worse, Cobalt used to be one of the popular web servers on the Market, and it supports a database called InterBase. Now due to Sun drop Cobalt dead, it is hard to find web hosting companies support InterBase. And I have a few projects written on InterBase, now it is hard to find a big hosting company to support the InterBase to host them.

All these are because of SUN MICORSYSTEM.

园丁大人，
现在，虽说能上歌了，但不是上传功能。
自己手里的歌还是无法搬上来。

海雨，是你就好。:-)

我考得还行吧，和自己的期望值差不多。不过还是等分数出来了才能最后确定。这两天先放松放松再说。:-)

海雨，

伊甸现在是一个web host的普通客户，我们没有租用server。目前这个host的服务
和费用等都还令人满意。

如果伊甸膨胀较快，我们又能筹集到足够的资金，我计划建立一套mirror系统，用
自己的server，参照模仿host的环境LAMP。平常时mirror系统的主要目的不是供客
户使用从而为主系统分流，而是为了修改测试界面及功能(as a testing system)、
备份(as a backup system)和预防万一(as a redundancy system)，比如说如果
host down了，mirror系统就可以用上，以保证网站的稳定持续。

当时你为什么用Sun体系，而不用Linux体系？Sun体系不大适合小business。$75/hour
for upgrading Solaris is very expensive. What other services did you get?

老实说，我这几年越做，手就把得越严，采用的方案就越CHEAP，不一定适合你们。

1）首先，关于BACK UP和REDUNDANCY SYSTEM。看看你的HOSTING有什么样的BACK UP SERVICE，还有，有的HOSTING SERVER本身就是用2个DISK，并且其中一个DISK当作redundancy system的（他们SUPPORT几百个网站，一旦垮了没法恢复，麻烦大了去了。）。加上，你可以自己经常性的DOWNLOAD MYSQL数据库，偶然再DOWNLOAD一下整个网站（主要是DOWNLOAD那些UPLOAD的文件。但是这部分文件量很大， 时间和TRAFFIC都不容许你经常这么做。经常在家里这么做，你的HOME INTERNET SERVICEG公司会找你麻烦的。）现阶段应该足够了。

2）其次，RUN一个MIRROR系统对你们来说，在很长一段时间会是OVER KILL。大公司当然该用。HXWZ那么大，也可以用。还有比方说那些付费的色情网站，虽然小，他们也该有MIRROR系统，因为他们的客户是付钱的，系统DOWN了，客户是要求退钱的。而且，我的理解是MIRROR系统是和主系统都是一起运作时，主系统DOWN了，MIRROR系统还可以TAKE OVER。如果平时MIRROR系统不RUN，只有主系统RUN，主系统DOWN时，MIRROR系统也不能马上接过来。因为平时的DOMAIN NAME SERVICE都是只指向主系统（MIRROR系统没RUN）。RE－BROADCAST你的新DOMAIN IP地址，也要花些时间。这时，你的HOSTING公司可能已经修复了。因为你们是公益网站，等等也可以，别人的网站可能是和金钱利益悠关，等不及的。

Originally posted by [i]thesunlover[/i] at 2006-5-13 05:26 PM:

如果伊甸膨胀较快，我们又能筹集到足够的资金，我计划建立一套mirror系统，用
自己的server，..

关于自己做个MIRROR系统做为TEST之用，也可以兼做BACK UP之用，倒是可以马上做起来。用一台旧PC就可以，当然如果你要把将来全部的图都MIRROR到旧PC上，可能DISK SPACE不够。如果把图只COPY到TAPE上，而复制其他部分，就足够了。

自己在旧PC上装上LAMP，和YIDIAN（DISCUZ），就完全可以复制成了。然后你自己在家里做个LOCAL AREA NETWORK。可以从自己平时用的PC当做读者上你的TEST SERVER上的伊甸。

或者就在那旧PC TEST SERVER上，装上LINUX的DESKTOP应用软件。做为SERVER ADMINISTRATOR，你就直接从SHELL COMMAND接口去做，做为读者时，你就切换到LINUX的GUI DESKTOP的接口，用FIREFOX那样的BROWSER上网看TEST SERVER的运作。

我想用旧PC或者旧的UNIX BOX SET UP 一个TEST SERVER。这部分你可以马上做起来，你是系统出身，做这个是本行。TEST SERVER做好了。你就可以学习，测试，修改PHP CODE，和伊甸系统。等你熟悉了WEB SERVER，PHP和伊甸。下一步，伊甸可能也要发展到需要自己的SERVER了，到那时，你学来的正好可以用上。