Fixes #157 - Add mention of seed_fu to docs.

This commit is contained in:
Robin Ward
2013-02-26 12:45:56 -05:00
parent 6c30e0b09c
commit ddf1f27633
3 changed files with 14 additions and 12 deletions

View File

@ -14,7 +14,7 @@ Discourse.ComboboxViewCategory = Discourse.ComboboxView.extend({
if (!templateData.color) return text; if (!templateData.color) return text;
var result = "<span class='badge-category' style='background-color: #" + templateData.color + "' " var result = "<span class='badge-category' style='background-color: #" + templateData.color + "' "
if (templateData.description && templateData.description != 'null') { if (templateData.description && templateData.description !== 'null') {
result += "title=\"" + templateData.description + "\" "; result += "title=\"" + templateData.description + "\" ";
} }
return result + ">" + text + "</span>"; return result + ">" + text + "</span>";

View File

@ -19,8 +19,9 @@ to rails, you are likely much better off with our **[Discourse Vagrant Developer
1. `bundle install` 1. `bundle install`
2. `rake db:migrate` 2. `rake db:migrate`
3. `rake db:test:prepare` 3. `rake db:test:prepare`
4. Try running the specs: `bundle exec rspec` 4. `rake db:seed_fu`
5. `bundle exec rails server` 5. Try running the specs: `bundle exec rspec`
6. `bundle exec rails server`
You should now be able to connect to rails on http://localhost:3000 - try it out! The seed data includes a pinned topic that explains how to get an admin account, so start there! Happy hacking! You should now be able to connect to rails on http://localhost:3000 - try it out! The seed data includes a pinned topic that explains how to get an admin account, so start there! Happy hacking!
@ -38,7 +39,7 @@ Vagrant version 1.0.5. With this Vagrantfile:
config.vm.box = 'precise32' config.vm.box = 'precise32'
config.vm.box_url = 'http://files.vagrantup.com/precise32.box' config.vm.box_url = 'http://files.vagrantup.com/precise32.box'
config.vm.network :hostonly, '192.168.10.200' config.vm.network :hostonly, '192.168.10.200'
if RUBY_PLATFORM =~ /darwin/ if RUBY_PLATFORM =~ /darwin/
config.vm.share_folder("v-root", "/vagrant", ".", :nfs => true) config.vm.share_folder("v-root", "/vagrant", ".", :nfs => true)
end end
@ -63,21 +64,21 @@ Vagrant version 1.0.5. With this Vagrantfile:
export LANGUAGE=en_US.UTF-8 export LANGUAGE=en_US.UTF-8
export LANG=en_US.UTF-8 export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8 export LC_ALL=en_US.UTF-8
locale-gen en_US.UTF-8 locale-gen en_US.UTF-8
dpkg-reconfigure locales dpkg-reconfigure locales
## RVM and Ruby ## RVM and Ruby
apt-get -yqq install libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt-dev autoconf libc6-dev ncurses-dev automake libtool bison subversion pkg-config curl build-essential git apt-get -yqq install libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt-dev autoconf libc6-dev ncurses-dev automake libtool bison subversion pkg-config curl build-essential git
su - vagrant -c "sudo bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer)" su - vagrant -c "sudo bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer)"
adduser vagrant rvm adduser vagrant rvm
source /etc/profile.d/rvm.sh source /etc/profile.d/rvm.sh
su - vagrant -c "rvm pkg install libyaml" su - vagrant -c "rvm pkg install libyaml"
su - vagrant -c "rvm install 1.9.3-p374" su - vagrant -c "rvm install 1.9.3-p374"
su - vagrant -c "rvm use 1.9.3-p374 --default" su - vagrant -c "rvm use 1.9.3-p374 --default"
echo "gem: --no-rdoc --no-ri" >> /etc/gemrc echo "gem: --no-rdoc --no-ri" >> /etc/gemrc
su - vagrant -c "echo 'gem: --no-rdoc --no-ri' >> ~/.gemrc" su - vagrant -c "echo 'gem: --no-rdoc --no-ri' >> ~/.gemrc"
@ -102,7 +103,7 @@ Also, a user "discourse" is needed when importing a database image.
Edit /etc/postgresql/9.1/main/pg_hba.conf to have this: Edit /etc/postgresql/9.1/main/pg_hba.conf to have this:
local all all trust local all all trust
host all all 127.0.0.1/32 trust host all all 127.0.0.1/32 trust
host all all ::1/128 trust host all all ::1/128 trust
host all all 0.0.0.0/0 trust # wide-open host all all 0.0.0.0/0 trust # wide-open

View File

@ -2,11 +2,11 @@
We have deliberately left this section lacking. From our FAQ: We have deliberately left this section lacking. From our FAQ:
> Discourse is brand new. Discourse is early beta software, and likely to remain so for many months. > Discourse is brand new. Discourse is early beta software, and likely to remain so for many months.
> Please experiment with it, play with it, give us feedback, submit pull requests – but any consideration > Please experiment with it, play with it, give us feedback, submit pull requests – but any consideration
> of fully adopting Discourse is for people and organizations who are eager to live on the bleeding and broken edge. > of fully adopting Discourse is for people and organizations who are eager to live on the bleeding and broken edge.
When Discourse is ready for primetime we're going to provide several robust and easy ways to install it. When Discourse is ready for primetime we're going to provide several robust and easy ways to install it.
Until then, if you are feeling adventurous you can try to set up following components. Until then, if you are feeling adventurous you can try to set up following components.
- Postgres 9.1 - Postgres 9.1
@ -16,8 +16,9 @@ Until then, if you are feeling adventurous you can try to set up following compo
- Ruby 1.9.3 - Ruby 1.9.3
- Install all rubygems via bundler - Install all rubygems via bundler
- Edit database.yml and redis.yml and point them at your databases. - Edit database.yml and redis.yml and point them at your databases.
- Run `rake db:seed_fu` to add seed data
- Prepackage all assets using rake - Prepackage all assets using rake
- Run the Rails database migrations - Run the Rails database migrations
- Run a sidekiq process for background jobs - Run a sidekiq process for background jobs
- Run a clockwork process for enqueing scheduled jobs - Run a clockwork process for enqueing scheduled jobs
- Run several Rails processes, preferably behind a proxy like Nginx. - Run several Rails processes, preferably behind a proxy like Nginx.