Fresh install of version 1.1.0 on Windows / Apache
Fresh install of version 1.1.0 on Windows / Apache
| Issue ID: | 3622 |
| Issue Category: | documentation |
| Component: | documentation |
| Priority: | normal |
| Status: | active |
| Assigned: | Unassigned |
| Version: | 1.0 |
| Keywords: | installation notice_id |
As a total newbie to StatusNet (bit with 40 years in IT!) I have recently gone through a rather painful 2 hour process to get statusnet 1.1.0 to do a virgin install on Windows 2003 server with Apache 2.2.22 / php 5.3.14 and thought I would share the findings.
Some of these findings also appear to solve other issues raised in the forum.
------------------------
FIRST BUG:
The install process stalls because of the 'notice_id' issue documented (but no solution) elsewhere, but no solution is given (that I could find). The solution to this that I used is as follows.
The unix timestamp would appear to meet the description of the notice_id column which does not have a default value. .. and the installation does work with this value. I am happy to be corrected if anyone knows better.
WORKAROUND
(1) edit ../db/notice_source.sql to include a value for notice_id in and replace ', now()),' with ', now(), UNIX_TIMESTAMP()),'
The SQL will read like this
INSERT INTO notice_source
(code, name, url, created, notice_id )
VALUES
('adium', 'Adium', 'http://www.adiumx.com/', now(), UNIX_TIMESTAMP()),
... etc
(2) drop all tables in the MySQL database
(4) try again .. progress to next error!
------------------------
I also ran the command line checkschema.php at this point and it reported no errors. However it does not set any default value for the notice_id column in the notice_source table.
...\scripts>php checkschema.php
------------------------
SECOND BUG
This then progresses to another error related to setup of the configuration. After a lot of tests to try and cure this I found that the installation is complete EXCEPT that the administrator account is not set up and thus needs to be set up manually.
WORKAROUND - MANUALLY CREATING AN ADMINISTRATOR
Use the command line tools to create user who can log in, then promote them to admin:
...\scripts>php registeruser.php -n johndoe -w mypassword
...\scripts>php userrole.php -n johndoe -r administrator
------------------------
After this the server appears to work correctly, the administrator 'johndoe' can log in and change settings etc, and - in so far - as I have tested it I am able to send / receive status messages via iPhone / iPad clients.
Hope that is useful. The ../db/notice_source.sql in the distribution does need to be replaced or the database schema changed to include a default value for notice_id.

Updates
You can also subscribe to the
RSS feed for updates to this issue.