Services/Sync/Server/Archived/0.3/Setup/Server: Difference between revisions

From MozillaWiki
< Services‎ | Sync‎ | Server‎ | Archived‎ | 0.3/Setup
Jump to navigation Jump to search
No edit summary
(Replaced content with 'This server is deprecated. Please use [https://wiki.mozilla.org/Labs/Weave/API the new servers]')
Line 1: Line 1:
[https://wiki.mozilla.org/Labs/Weave/0.5/Setup/Storage Preliminary 0.5 setup notes and migration guide]
This server is deprecated. Please use [https://wiki.mozilla.org/Labs/Weave/API the new servers]
 
== Pre-Setup Considerations ==
 
<b>This server is deprecated. Please use the 0.5 server above</b>
 
It is strongly recommended that the Weave Server be set up under https, or behind a firewall with an https proxy in front of it. It uses standard http auth, which will send the password in the clear unless done over https.
 
The Weave Server requires PHP with PDO and JSON support installed. This should be the case if you are running PHP 5.1+. PDO will need drivers for whatever storage and authentications engines are used.
 
WebDav must not be enabled for this server - it intercepts some of the http packets and syncing will fail.
 
== Setting up the Server ==
 
1) Unzip the server-directory into the location you plan to serve the files from. You can get the latest server from http://hg.mozilla.org/labs/weaveserver (there you can download it in different formats). Once things are fully established, we'll declare certain builds as stable, but for now assume all releases are beta quality.
 
2) Edit your apache conf files to add the following:
 
<pre>
Alias /0.3/user <full path to weave directory>/0.3/index.php
</pre>
 
Don't forget to set up the weave directory in a virtual-host-directive (or similar), or else php will not work. (See sample virtual host config below)
 
3) Edit the weave_constants.php file as described below, and move it into a directory in the php include path (usually just the same folder).
 
== Setting up Weave Authentication ==
 
In weave_constants.php at the beginning (e.g. directly after the license-block)
 
<pre>
define('WEAVE_AUTH_ENGINE', '[sqlite|mysql|ldap|none]');
</pre>
 
so for example
 
<pre>
define('WEAVE_AUTH_ENGINE', 'mysql');
</pre>
 
 
(note that LDAP support is preliminary and incomplete at this time)
 
=== Sqlite ===
 
<pre>
define('WEAVE_SQLITE_AUTH_DIRECTORY', '<path to stores directory>');
</pre>
 
additionally, create the users table
 
<pre>
$ sqlite3 <path to stores directory>/_users
SQLite version 3.4.0
sqlite> create table users (username text primary key, md5 text, email text, status integer, alert text);
sqlite> .quit
</pre>
 
Change the owner of the _users db file to the account your webserver runs under.
 
=== Mysql ===
 
Create the mysql database. Add the following tables:
 
<pre>
create table users
(
username varchar(32) primary key,
md5 varbinary(32),
email varbinary(64),
status tinyint,
alert text
) engine=InnoDB;
</pre>
 
Constants:
 
<pre>
define('WEAVE_MYSQL_AUTH_HOST', '<db host>');
define('WEAVE_MYSQL_AUTH_DB', '<db name>');
define('WEAVE_MYSQL_AUTH_USER', '<db username>');
define('WEAVE_MYSQL_AUTH_PASS', '<db password>');
</pre>
 
(Note that you don't need to define the second set of constants if you are using the same db for reads and writes)
 
You can create users directly in mysql with the following command:
 
<pre>
insert into users values ('username', md5('password'), null, 1, null);
</pre>
 
But it is recommended to use the create_user0.3.pl script after setting up the admin-interface (see below).
 
== Setting up Weave Storage ==
 
<pre>
define('WEAVE_STORAGE_ENGINE', '[sqlite|mysql]');
</pre>
 
=== Sqlite ===
 
Edit the following constant:
 
<pre>
define('WEAVE_SQLITE_STORE_DIRECTORY', '<path to stores directory>');
</pre>
 
Easiest way to create a user is to go through the admin server process below.
 
=== Mysql ===
 
Create the mysql database. Add the following table:
 
<pre>
CREATE TABLE `wbo` (
  `username` varbinary(32) NOT NULL default '',
  `collection` varbinary(64) NOT NULL default '',
  `id` varbinary(64) NOT NULL default '',
  `parentid` varbinary(64) default NULL,
  `predecessorid` varbinary(64) default NULL,
  `modified` decimal(12,2) default NULL,
  `sortindex` int(11) default NULL,
  `depth` tinyint(4) default NULL,
  `payload` longtext,
  `payload_size` int(11) default NULL,
  PRIMARY KEY  (`username`,`collection`,`id`),
  KEY `parentindex` (`username`,`collection`,`parentid`),
  KEY `modified` (`username`,`collection`,`modified`),
  KEY `weightindex` (`username`,`collection`,`sortindex`),
  KEY `predecessorindex` (`username`,`collection`,`predecessorid`)
) ENGINE=InnoDB
</pre>
 
 
Edit your constant file:
 
<pre>
define('WEAVE_MYSQL_STORE_READ_HOST', '<db host>');
define('WEAVE_MYSQL_STORE_READ_DB', '<db name>');
define('WEAVE_MYSQL_STORE_READ_USER', '<db username>');
define('WEAVE_MYSQL_STORE_READ_PASS', '<db password>');
 
define('WEAVE_MYSQL_STORE_WRITE_HOST', WEAVE_MYSQL_STORE_READ_HOST);
define('WEAVE_MYSQL_STORE_WRITE_DB', WEAVE_MYSQL_STORE_READ_DB);
define('WEAVE_MYSQL_STORE_WRITE_USER', WEAVE_MYSQL_STORE_READ_USER);
define('WEAVE_MYSQL_STORE_WRITE_PASS', WEAVE_MYSQL_STORE_READ_PASS);
</pre>
 
== Other Constants ==
 
<pre>
define('WEAVE_PAYLOAD_MAX_SIZE', '<bytes>');
</pre>
 
Caps the size (in bytes - watch out for large unicode characters!) of a payload.
 
<pre>
define('WEAVE_SHARE_DBH', '1');
</pre>
 
If both the storage engine and authentication engine are using the same database, setting this makes both engines use the same database handler rather than opening different ones. Note that SQLite cannot use the same db for authentication and storage.
 
== Setting up Weave Admin ==
 
You can create, update passwords and delete users through the Server Admin API. Using the [https://wiki.mozilla.org/Labs/Weave/0.3/Admin admin server] is optional and is offered as a convenience rather than a requirement.
 
Add the following to your apache conf:
 
<pre>
Alias /weave/admin <path to the admin.php script>
</pre>
 
Due to the security concerns, this script should be additionally protected, either through denying most IPs, or using htaccess. Additionally, the following constant, if set, is required to be passed in for all transactions to the server:
 
<pre>
define('WEAVE_USER_ADMIN_SECRET', '<secret>');
</pre>
 
== Testing the Weave Server ==
 
The load_data.pl script will run a series of tests against your server, creating, modifying, selecting from and deleting a collection. Make sure to change the parameters at the top before running it. Also, the script requires the libwww-perl module and the weave admin server above to be set up. It currently does not work with http-authentication, so also be sure to have your web-directory unprotected during the tests.
 
== Creating and deleting users ==
 
Simply use the create_user.pl for this. You will need to have the libwww-perl-module and admin-server set up for running it. Just edit the parameters at the top of the file.
 
== Sample virtual host config ==
Sample Virtual host config for a server having SSL enabled and requiring http authentication. For debian placed in /etc/apache2/sites-enabled/, weave server directory located at /var/www/weaveserver/server/.
<pre>
<VirtualHost weave.my.domain:443>
 
ServerName weave.my.domain
DocumentRoot /var/www/weaveserver/server/
 
ErrorLog /var/log/apache2/weaveserver-error.log
CustomLog /var/log/apache2/weaveserver-access.log combined
 
SSLENgine on
SSLCertificateKeyFile /path/to/server.cert.key
SSLCertificateFile /path/to/server.cert.crt
 
<Directory "/var/www/weaveserver/server/">
 
Options Indexes FollowSymLinks
AllowOverride none
Order allow,deny
Allow from all
AuthType Basic
AuthName "Weave Server"
AuthUserFile /path/to/auth/file
require valid-user
 
</Directory>
 
Alias /weave/admin /var/www/weaveserver/server/admin.php
 
Alias /0.3/user /var/www/weaveserver/server/index.php
 
</VirtualHost>
</pre>
 
In your weave-clients only enter https://weave.my.domain as server location.
Some hints:
* the username/password of the http-authentication must be the same as the one for the weave-user, or else it won't work
* if you have a self-signed certificate for SSL (or it is not valid because of any other reason) you have to visit your server once manually and accept the certificate permanently

Revision as of 18:41, 29 January 2010

This server is deprecated. Please use the new servers

Retrieved from "https://wiki.mozilla.org/index.php?title=Services/Sync/Server/Archived/0.3/Setup/Server&oldid=197781"