Setup Server (Task #50)

Regarding the DB: IIRC most here are more comfortable/accustomed to PostgreSQL rather than MySQL. I don't care which one it is, but if the general XP is more towards managing PostgreSQL rather than MySQL, I'd favor that.

+1. I learned my way around MySQL recently, but still prefer Postgres for its configuration and standard-conforming semantics.

One issue we might face with Postgres is if we want to use one of the LAMP-apps (like wordpress) which still mostly require MySQL. If we stick to MySQL, then I would vote to at least use InnoDB tables.

• RE - SSH login: Worked for me
• RE - Postgres vs MySQL: I'm stronger with MySQL but I'm moving all of my sites to Postgres. It doesn't matter to me much
• RE - MySQL because of Wordpress: I strongly recommend that Wordpress be on a different server (I have one). So it shouldn't affect this decision.

Few suggestions:

• Install htop and emacs23-nox
• Need iptables
• Should disable root login and require users to login as themselves and sudo

Once you have the base server setup we will need to coordinate moving the code from here. I'm running a specific commit from Redmine with some security patches and then the theme.

Need a final decision: Postgres or MySQL.

Also, could I remove Ubuntu's version of Ruby in favor of REE?

Eric Davis wrote:

Need a final decision: Postgres or MySQL.

Just go with MySQL, we can always switch (also agreed in IRC)

Also, could I remove Ubuntu's version of Ruby in favor of REE?

Yes, feel free to do as you see fit.

The staging server is almost setup but Apache is throwing an error and I'm out of ideas on how to fix it. If someone else wants to take a look at it, it's in /var/log/apache2/error.log as.

Symbolic link not allowed or link target not accessible: /srv/chiliproject/current

I've already gone though a bunch of steps to debug it:

• turned off ssl
• make sure FollowSymLinks is enabled
• make sure the www-data user has permission to cd into the Document Root
• set the document root to the parent directories and tried to load a static HTML file (worked correctly until it hit the current/ symlink)

[2:34] <meineerde> edavis10: works now
[2:35] <meineerde> it was because in /etc/apache2/conf.d/security, I disabled symlink-following globally.
[2:35] <meineerde> thus, you needed to enable symlinks in /srv/chiliproject, because else it wouldn't follow the symlink in /srv/chiliproject/current

Holger:

Not working. Can you post your changes here so I can make sure they aren't overwritten when I deploy?

Felix:

(Like we discussed on IRC) I think it was lost in the import/export/download/upload process I had to do, somewhere along the lines the encoding must have been lost.

Going to move to the production server now!