codeninjasllc/discourse
1
0
Fork 0
mirror of https://github.com/codeninjasllc/discourse.git synced 2024-11-27 17:46:05 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

increase required Postgres version to 9.2

Browse source
This commit is contained in:
Jeff Atwood 2015-04-25 01:16:18 -07:00
parent 7d5b5533c4
commit 7c98b16bfd
4 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/DEVELOPER-ADVANCED.md
View file

@ -82,11 +82,11 @@ Vagrant version 1.1.2. With this Vagrantfile:
echo "gem: --no-document" >> /etc/gemrc echo "gem: --no-document" >> /etc/gemrc
su - vagrant -c "echo 'gem: --no-document' >> ~/.gemrc" su - vagrant -c "echo 'gem: --no-document' >> ~/.gemrc"
## Postgres 9.1 ## Postgres 9.2
Configure so that the vagrant user doesn't need to provide username and password. Configure so that the vagrant user doesn't need to provide username and password.
apt-get -yqq install postgresql postgresql-contrib-9.1 libpq-dev postgresql-server-dev-9.1 apt-get -yqq install postgresql postgresql-contrib-9.3 libpq-dev postgresql-server-dev-9.3
su - postgres su - postgres
createuser --createdb --superuser -Upostgres vagrant createuser --createdb --superuser -Upostgres vagrant
psql -c "ALTER USER vagrant WITH PASSWORD 'password';" psql -c "ALTER USER vagrant WITH PASSWORD 'password';"

2
docs/INSTALL.md
View file

@ -20,7 +20,7 @@ Hosting Rails applications is complicated. Even if you already have Postgres, Re
### Software Requirements ### Software Requirements
- [Postgres 9.1+](http://www.postgresql.org/download/) - [Postgres 9.2+](http://www.postgresql.org/download/)
- [Redis 2.6+](http://redis.io/download) - [Redis 2.6+](http://redis.io/download)
- [Ruby 2.0+](http://www.ruby-lang.org/en/downloads/) (we recommend 2.0.0-p353 or higher) - [Ruby 2.0+](http://www.ruby-lang.org/en/downloads/) (we recommend 2.0.0-p353 or higher)

4
docs/TROUBLESHOOTING-prod.md
View file

@ -12,7 +12,7 @@ something like:
`ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]` `ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]`
1. Are you on Postgres 9.1 or later with HSTORE enabled? 1. Are you on Postgres 9.2 or later with HSTORE enabled?
You can check your postgres version by typing `psql --version`. To see if You can check your postgres version by typing `psql --version`. To see if
hstore is installed, open a session to postgres and type `\dx` and see if hstore is installed, open a session to postgres and type `\dx` and see if
@ -50,7 +50,7 @@ should *always* pass every test.
If links in emails have localhost in them, then you are still using the If links in emails have localhost in them, then you are still using the
default `host_names` value in database.yml. Update it to use your site's host default `host_names` value in database.yml. Update it to use your site's host
name(s). name(s).
1. Are you having problems bundling: 1. Are you having problems bundling:
``` ```

14
docs/TROUBLESHOOTING.md
View file

@ -6,11 +6,11 @@ reaching out to the community for help:
1. Are you running Ruby 2.0 or later? 1. Are you running Ruby 2.0 or later?
Discourse is designed for Ruby 2.0 or later. We recommend 2.0.0 p353 or later. You can check your version by typing Discourse is designed for Ruby 2.0 or later. We recommend 2.0.0 p353 or later. You can check your version by typing
`ruby -v` and checking the response. `ruby -v` and checking the response.
2. Are you on Postgres 9.1 or later with HSTORE enabled? 2. Are you on Postgres 9.2 or later with HSTORE enabled?
You can check your postgres version by typing `psql --version`. To see if hstore is You can check your postgres version by typing `psql --version`. To see if hstore is
installed, open a session to postgres and type `\dx` and see if hstore is listed. installed, open a session to postgres and type `\dx` and see if hstore is listed.
@ -30,21 +30,21 @@ reaching out to the community for help:
5. Have you migrated your database? 5. Have you migrated your database?
Our schema changes fairly frequently. After checking out the source code, you should Our schema changes fairly frequently. After checking out the source code, you should
run `rake db:migrate` run `rake db:migrate`
7. Do the tests pass? 7. Do the tests pass?
If you are having other problems, it's useful to know if the test suite passes. You If you are having other problems, it's useful to know if the test suite passes. You
can run it by first using `rake db:test:prepare` and then `rake spec`. If you can run it by first using `rake db:test:prepare` and then `rake spec`. If you
experience any failures, that's a bad sign! Our master branch should *always* pass experience any failures, that's a bad sign! Our master branch should *always* pass
every test. every test.
8. Have you updated host_names in your database.yml? 8. Have you updated host_names in your database.yml?
If links in emails have localhost in them, then you are still using the default host_names If links in emails have localhost in them, then you are still using the default host_names
value in database.yml. Update it to use your site's host name(s). value in database.yml. Update it to use your site's host name(s).
9. Are you having problems bundling: 9. Are you having problems bundling:
``` ```