From: Shane Z. <sh...@lo...> - 2011-02-15 22:57:44
|
I believe the process was something like this: /usr/local/slash/bin/install-slashsite -u slash -H {TLD} -o shane -g nobody -R -a webmaster -e web...@lo... -p {PASSWORD} -L y install-plugin -u slash {....} /usr/local/slash/bin/template-tool {...} then the symlink tool to finish it up. update vars set value='' where name like "cache%"; runtask -u slash new_headfoot runtask -u slash freshenup /usr/local/src/slash/slash/utils/createTestUsers -u slash 10 /usr/local/src/slash/slash/utils/createTestUsers -u slash -J 10 /usr/local/src/slash/slash/utils/createTestStories -u slash 10 /usr/local/src/slash/slash/utils/createTestComments -u slash -R 100 /usr/local/src/slash/slash/utils/createTestComments -u slash -R -J 100 /usr/local/src/slash/slash/utils/createTestStories -u slash 20 /usr/local/src/slash/slash/utils/createTestComments -u slash -R 50 /usr/local/src/slash/slash/utils/createTestComments -u slash -RJ 100 /usr/local/src/slash/slash/utils/createTestComments -u slash -Rt 100 /usr/local/src/slash/slash/utils/createTestStories -u slash 40 /usr/local/src/slash/slash/utils/createTestUsers -u slash 10 /usr/local/src/slash/slash/utils/createTestUsers -u slash -J 10 /usr/local/src/slash/slash/utils/createTestUsers -u slash 10 /usr/local/src/slash/slash/utils/createTestUsers -u slash -J 10 /usr/local/src/slash/slash/utils/createTestComments -u slash -R 100 /usr/local/src/slash/slash/utils/createTestComments -u slash -RJ 100 /usr/local/src/slash/slash/utils/createTestComments -u slash -Rt 100 /usr/local/src/slash/slash/utils/createTestMods -u slash -r -R /usr/local/src/slash/slash/utils/createTestMetamods -u slash /usr/local/src/slash/slash/utils/createTestSubmissions -u slash Here were some other handy (at the time, anyway) tidbits update vars set value ="http://it.{TLD}" where name='absolutedir'; update vars set value='it.{TLD}' where name='basedomain'; update vars set value='http://it.{TLD}/images/topics/topicslash.gif' where name='rdfimg'; update vars set value='//it.{TLD}' where name='rootdir'; update site_info set value="/usr/local/slash/site/it.{TLD}" where name='site_install_directory'; update site_info set value="webmaster\@{TLD}" where name="adminmail"; update site_info set value="it.{TLD}" where name="siteid"; update site_info set value="it.{TLD}" where name="basedomain"; update vars set value="webmaster\@{TLD}" where name="adminmail"; update vars set value="webmaster\@{TLD}" where name="adminmail_ban"; update vars set value="webmaster\@{TLD}" where name="adminmail_mod"; update vars set value="webmaster\@{TLD}" where name="adminmail_post"; update vars set value="/usr/local/slash/site/it.{TLD}/htdocs" where name="basedir"; update vars set value="/usr/local/slash/site/it.{TLD}" where name="datadir"; update vars set value="//it.{TLD}/images" where name="imagedir"; update vars set value="/usr/local/slash/site/it.{TLD}/logs" where name="logdir"; update vars set value="webmaster\@{TLD}" where name="mailfrom"; update vars set value="webmaster\@{TLD}" where name="mod_stats_reports"; update vars set value="it.{TLD}" where name="siteid"; update vars set value="IT Department INTERNAL" where name="sitename"; update vars set value="webmaster\@{TLD}" where name="stats_reports"; # then startup slashd and httpd Shane On Feb 15, 2011, at 4:17 PM, Marc G. Fournier wrote: > > 'k, am going to have to debug this one, since when I tried it thefirst > time, it seemed to work (created the link), but the second time it didn't > ... but thanks for the pointer at what I need to look at ... > > but ... should this not be part of the install-slashsite process itself? > Or was it always a seperate step / process? > > On my list to debug either way, just apprecaite the 'overview' aspect of > things ... > > > On Tue, 15 Feb 2011, Shane Zatezalo wrote: > >> try running the symlink-tool >> >> "symlink-tool -U -u virtusername" and "template-tool -U -u virtusename" >> >> On Feb 15, 2011, at 1:25 PM, Marc G. Fournier wrote: >> >>> >>> Just did a bunch of work on the javascript files, grouping htem better, so that I'm to the point that I havea couple of small issues taht need to be resolved ... but ... >>> >>> I'm still getting: >>> >>> File does not exist: /usr/local/www/d_admin/ap13.haxlash.org/www/site/www.haxlash.org/htdocs/slashcode.css >>> >>> using the slashcode theme ... there is a slashcode.cssraw file, and there is a slashcode.css file under the slashcode.com theme ... >>> >>> doing a diff between the two, the slashcode.cssraw file is the better one as it uses variables vs hard coded URLs ... and copying it to slashcode.css does appear to work ... >>> >>> So the question is, why the .cssraw extensions vs straight .css? I *think* I'm safe to just rename it to .css, but if someone with more intimate knowledge could shed some light before I do ... ? >>> >>> >>> ---- >>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>> sc...@hu... http://www.hub.org >>> >>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >> >> > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > sc...@hu... http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |