MOSS/Setup - Revision history

Admin: JW: Fixed Scripts.zip link to Scripts902.zip.

2018-03-28T04:13:30Z

JW: Fixed Scripts.zip link to Scripts902.zip.

Christian Walther: /* Prerequisites */ Add some empirical version information

2012-04-02T19:47:28Z

Prerequisites: Add some empirical version information

Mac Fife: /* See Also */ Add more links

2012-03-09T08:00:14Z

Lyrositor: Fix tiny typo.

2012-02-27T13:45:11Z

Fix tiny typo.

Mac Fife: Bypass redirects

2012-02-21T13:20:34Z

Bypass redirects

Mac Fife: /* See Also */ Bypass redirect

2012-02-21T13:01:23Z

Mac Fife: moved MOSS-Setup to MOSS/Setup

2012-02-21T12:58:37Z

moved MOSS-Setup to MOSS/Setup

Lyrositor: Removed undesirable future tenses. Replaced "tt" with "code".

2012-02-21T03:26:29Z

Removed undesirable future tenses. Replaced "tt" with "code".

Show changes

Lyrositor: /* Start It Up */

2012-02-16T03:10:07Z

Start It Up

Lyrositor: Added `tags for file paths.`

2012-02-16T02:11:11Z Added <tt> tags for file paths. Show changes

@@ Line 138: / Line 138: @@
 Just like for the file and auth server data, the default game directory is <code>./game</code> (relative to where you start it up). I recommend using <code>''prefix''/game</code>.
-The game servers need unencrypted <code>.sdl</code> and <code>.age</code> files. The easiest way to get a set of these files is from the Cyan-provided <code>[http://assets.openuru.org/cyan/Scripts.zip Scripts.zip]</code>. Download this file and unzip it. Copy/move the <code>Scripts/SDL</code> directory to <code>''game-dir''</code>. Then create <code>''game-dir''/age</code> and copy <code>Scripts/dat/*.age</code> to it (MOSS does not use the <code>.fni</code> files).
+The game servers need unencrypted <code>.sdl</code> and <code>.age</code> files. The easiest way to get a set of these files is from the Cyan-provided <code>[http://assets.openuru.org/cyan/Scripts902.zip Scripts.zip]</code>. Download this file and unzip it. Copy/move the <code>Scripts/SDL</code> directory to <code>''game-dir''</code>. Then create <code>''game-dir''/age</code> and copy <code>Scripts/dat/*.age</code> to it (MOSS does not use the <code>.fni</code> files).
 Do not forget to copy any user-created ages' SDL and <code>.age</code> files here. This copy needs to be unencrypted.

@@ Line 11: / Line 11: @@
 * libiconv (almost certainly installed already)
 * OpenSSL (also almost certainly installed) -- you need both the libraries and the development headers if that's separate (I'm looking at you, Debian)
 * Zlib (also probably installed) -- both the library and the development stuff if separate
 * PostgreSQL -- both the sever and client, plus any development packages
 * libpqxx -- both the library and the development package
 * gcc, g++, whatever all you need for compiling C++
 If you are compiling from a clone of a Mercurial respository and there is no "configure" script, you also need the autotools:
 * autoconf
 * automake
 * libtool
 '''If you are reading this, please go over to''' [[MOSS/Distribution Specific Instructions]] '''and fill in how to install all these programs on YOUR distribution/OS. Thank you!'''

← Older revision		Revision as of 08:00, 9 March 2012
Line 237:		Line 237:

	== See Also ==		== See Also ==
		+	{{:MOSS/See Also}}

	Please see the following for more information of interest to running a server.		Please see the following for more information of interest to running a server.

@@ Line 93: / Line 93: @@
 You need to start with your current Uru install (MOULagain, presumably). This procedure assumes you can run a Windows application to create the file server manifest MOSS needs. This seems a reasonable assumption when the client itself is a Windows app. So temporarily leave your *nix server alone and switch to a Windows installation with Uru installed.
-Copy <code>support/ManifestCreator.exe</code> and <code>support/Mainfests.zip</code> to your Windows box. Unzip <code>Manifests.zip</code>. This makes a <code>CyanStructure</code> folder. The <code>.txt</code> files in this folder are input. They describe the files which need to be in the final manifests. It is important to use <code>\</code> as the directory separator.
+Copy <code>support/ManifestCreator.exe</code> and <code>support/Manifests.zip</code> to your Windows box. Unzip <code>Manifests.zip</code>. This makes a <code>CyanStructure</code> folder. The <code>.txt</code> files in this folder are input. They describe the files which need to be in the final manifests. It is important to use <code>\</code> as the directory separator.
 Start up <code>ManifestCreator.exe</code>. To generate a manifest, click "Make Manifest"; it brings up a dialog box. Navigate to the <code>CyanStructure</code> folder, and select all the <code>.txt</code> files in there. Then click OK and when it pops up with another dialog asking for the location of your Uru install, navigate to that directory, click OK and wait for a bit.

@@ Line 1: / Line 1: @@
-'''[[MOSS]]''' currently only runs on UNIX and other *nix operating systems (such as GNU/Linux). Not Microsoft Windows. It ought to work on Mac OS/X (even PowerPC) but nobody has tried yet. The following document assists in the setup of MOSS on any of the compatible afore-mentioned operating systems. For instructions pertaining to a particular OS or Linux distribution, take a look at [[MOSS-Distribution Specific Instructions]].
+'''[[MOSS]]''' currently only runs on UNIX and other *nix operating systems (such as GNU/Linux). Not Microsoft Windows. It ought to work on Mac OS/X (even PowerPC) but nobody has tried yet. The following document assists in the setup of MOSS on any of the compatible afore-mentioned operating systems. For instructions pertaining to a particular OS or Linux distribution, take a look at [[MOSS/Distribution Specific Instructions]].
 Please also see the [http://foundry.openuru.org/fisheye/browse/MOSS/doc/setup main setup instructions] for an alternative set of installation instructions.
@@ Line 21: / Line 21: @@
 * libtool
-'''If you are reading this, please go over to''' [[MOSS-Distribution Specific Instructions]] '''and fill in how to install all these programs on YOUR distribution/OS. Thank you!'''
+'''If you are reading this, please go over to''' [[MOSS/Distribution Specific Instructions]] '''and fill in how to install all these programs on YOUR distribution/OS. Thank you!'''
 === configure ===
@@ Line 38: / Line 38: @@
 : Boot users who don't download <code>python.pak</code>.
 ; --enable-encryption=type
-: The default is "cyan_dh". MOSS allows you to disable encryption, or (legacy) use [[MOSS-Notes#RSA | RSA]].
+: The default is "cyan_dh". MOSS allows you to disable encryption, or (legacy) use [[MOSS/Notes#RSA | RSA]].
 ; --enable-fork
 : The primary use for this is if you need to debug auth or file servers. It is much easier to debug single-threaded programs.
@@ Line 58: / Line 58: @@
 Now cd into the <code>postgresql</code> directory. Here you need to compile a custom PostgreSQL module that creates UUIDs. Follow the instructions in the README file there, but for most people this should just be running '''<code>make</code>''', followed by '''<code>make install</code>'''.
-Install the PostgreSQL module in your PostgreSQL install, if it's not there already by now. Do this by copying the moss_uuidgen.so file you just compiled. You'll need to log in as root to do this (<code>sudo cp moss_uuidgen.so /path/to/postgres/modules</code> on most systems). Please check [[MOSS-Distribution_Specific_Instructions]] and fill in where to copy it for your system. Consult PostgreSQL documentation if you're not sure. After the library is installed, restart the DB server.
+Install the PostgreSQL module in your PostgreSQL install, if it's not there already by now. Do this by copying the moss_uuidgen.so file you just compiled. You'll need to log in as root to do this (<code>sudo cp moss_uuidgen.so /path/to/postgres/modules</code> on most systems). Please check [[MOSS/Distribution_Specific_Instructions]] and fill in where to copy it for your system. Consult PostgreSQL documentation if you're not sure. After the library is installed, restart the DB server.
 == Set Up the Database ==

@@ Line 239: / Line 239: @@
 Please see the following for more information of interest to running a server.
-* [[MOSS-Notes]]
+* [[MOSS/Notes]]
 * [http://foundry.openuru.org/fisheye/browse/MOSS/doc/running doc/running]
 [[Category:MOSS]]

← Older revision	Revision as of 12:58, 21 February 2012
(No difference)

@@ Line 213: / Line 213: @@
 Now you should be set to run your server. For now, <tt>cd</tt> to the directory you planned from the start to start the server from (that's <tt>''prefix''</tt> in the earlier recommendations). Make sure you are su'd to the user you want to run as. '''NOT root!''' Start <tt>moss_backend</tt> first, then <tt>moss</tt>. E.g., if you have put the config files in <tt>''prefix''/etc</tt>, you can just do:
-  bin/moss_backend
+  ''prefix''/bin/moss_backend
-  bin/moss
+  ''prefix''/bin/moss
 You can instead specify the location of the config file with the <tt>-c</tt> option. If you've used absolute paths in the config files, you can thus easily run the server from any directory.