Leung Aaron wrote:
Now in admin/docker , no matter I refresh how many times, the upgrade button wont appear and I am stuck now
Any ideas to solve it ?My version using right now is 0.9.9 (the latest target version I wanted to upgrade now should be 0.9.9.2 )
Posts: 3
Participants: 2
David wrote:
Pulled the latest release from the upstream this morning. Wanted to test the new poll plugin.
Result: it's easy to break a poll by changing your vote.
Posts: 14
Participants: 6
To The Tick Llc wrote:
We've had a great developer for our project so far, but sadly his time and availability to our project has become increasingly limited. We're doing some cool things with DC (including google hangouts plugins, widgets, pop ups), looking a for a sharp Ruby developer to help complete some important aspects of our project and to work with us as we created new DC implementations.
Aamar
skype:aamarx
Posts: 3
Participants: 2
arajvanshi wrote:
I selected the setting default_external_links_in_new_tab in the admin area. This resulted in the expected behaviour of setting default preference of all new users set to 'open external links in new tab'.
However, for non-logged-in visitors, the behaviour is still the old one, it is opening the external links in the same tab leading visitors to go away from the website. When admin selects the default_external_links_in_new_tab setting, it should change the behaviour for non-logged-in visitors as well.
Posts: 4
Participants: 3
Vassil Kalkov wrote:
Hi guys I want to add Bulgarian translation, but I can't register into Transifex. No confirmation email after registering, sent email to support still no answer.
I can do a pull request with Bulgarian translation, is this ok?
Posts: 1
Participants: 1
Jack James wrote:
In the ga_tracking_code I've pasted the code but it isn't working. Is there something specific I'm not supposed to include?
I've done it like so:
<script type="text/javascript"> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'id###']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); </script>
Posts: 8
Participants: 6
Andy Balholm wrote:
I want to run two small, private Discourse forums on one server. The first one is in a standalone Docker container. I thought it would be a good idea to just host the second instance in a second container. So I copied and modified my
app.ymlfile, ran./launcher bootstrap, and./launcher start. But./launcher startfails withError: Cannot start container 87c36c01e1c8fb760a28007304ccaba2756dbb0ebd6f85f30e57bad23cb904f9: port has already been allocated. It doesn't say which port is the problem. Has anyone else tried running two separate instances in separate containers? Or is this a bad idea; should I be figuring out how to do multisite?
Posts: 3
Participants: 2
Manthan Mallikarjun wrote:
Hello everyone!
I have taken the time to write up a blog post on how to setup Discourse on Amazon AWS. You can view the blog post here. http://0ak.org/how-to-setup-discourse-on-amazon-aws/
Please feel free to leave a comment on the blog post, or here and I will try to reply as soon as possible!
@sam and @codinghorror Is there anything I can improve with the tutorial?
Posts: 6
Participants: 3
Vikhyat Korrapati wrote:
Try it out on the following line, if you start selecting the text, proceed to select part of the link and release the mouse button the link will be opened:
Some text followed by a link: http://www.qwantz.com/index.php?comic=2611
This happens because the
mouseupevent is used for click-tracking here:Is there any reason for using
mouseupinstead ofclick?(cc @eviltrout)
Posts: 6
Participants: 5
Ioann wrote:
Want to see how does the badge system is working on live projects? Where can I check it? Or it's just unfinished feature?
Posts: 2
Participants: 2
Lee wrote:
Hi all,
I have an existing forum that is running Vanilla 2, I have an export of the database and I'm looking for someone with experience importing from another forum to help.
I see this project on GitHub https://github.com/rikkit/discourse-import-phpBB that looks like exactly what I need, just for phpBB.
From what I can gather it would just need to be modified slightly to reflect the tables that Vanilla rather than the phpBB table names. Ideally you'd be pro at this and able to tell me
I'm willing to offer $150 - $200 for a tested importer and someone to walk me through running the import via Skype.
Would be great if you were located in North America for timezones and able to get started on this right away as our current forum is down while I migrate this over.
Takers? Interested?
Posts: 13
Participants: 4
raly wrote:
20130618更新：在本指南发布后不久，官方推出了正式的安装指南，为了保持一致，ofGEEK 将对本指南进行较大幅度的升级，保持与官方的方法一致，暂时不推荐按照老指南进行安装，谢谢。
目前，Discourse 的英文安装指南已经很丰富了，但是仍然没有一份中文指南。为此，ofGEEK 专门编写整理了一份中文完全安装指南，希望能对需要的人有所帮助。
指南链接地址： http://www.ofgeek.com/2013/05/chinese-guide-on-discourse-install/
For non-Chinese readers, this is a post announcing that there is a Chinese guide on how to install Discourse on a VPS. Sorry for the bother and thank you for your attention.
Posts: 11
Participants: 7
Ieckert wrote:
Is it possible to merge two separate topics, but in the same category, into one new topic? I see that you can quote topics, then close the old ones. But that is all I could figure out at first look.
Posts: 4
Participants: 4
Jeff Atwood wrote:
As we edge closer and closer to Discourse 1.0 – which should happen in the next two months – we continue to improve our install story.
This topic is for comments on the original blog entry at: http://blog.discourse.org/2014/04/install-discourse-in-under-30-minutes/
Posts: 3
Participants: 3
Régis Hanol wrote:
So, you want to use S3 to handle image uploads? Here's the definitive guide:
S3 registration
Head over to http://aws.amazon.com/s3/ and click on
.
During the create account process, make sure you provide payment information, otherwise you won't be able to use S3. There's no registration fee, you will only be charged for what you use, if you exceed the free usage tier.
User creation
Creating a user account
Sign in to AWS Management Console and click on
to access the AWS Identity and Access Management (IAM) console which enables you to manage access to your AWS resources.
We need to create a user account, so click on the
Userslink on the left handside and then thebutton. Type in a descriptive user name and make sure the "Generate an access key for each User" checkbox is checked.
Here's the critical step: make sure you either download the credentials or you copy and paste somewhere safe both
Access Key IDandSecret Access Keyvalues. We will need them later.Setting permissions
Once the user is created, we need to set him permission. Select the user you've just created in the upper panel, click on the
Permissionstab in the lower panel and then click thebutton.
In the "Manage User Permissions" popup, select the
radio button and click the select button to manually enter the permission.
Type in a descriptive name for the policy and use the following piece of code as a template for your policy document:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:*", "Resource": [ "arn:aws:s3:::name-of-your-bucket", "arn:aws:s3:::name-of-your-bucket/*" ] } ] }Make sure you change both references to "
name-of-your-bucket" with the name of the bucket you will use for your Discourse instance before applying the policy.Discourse configuration
Now that you've properly set up S3, the final step is to configure your Discourse forum. Make sure you're logged in with an administrator account and go the Settings section in the admin panel.
Type in "S3" in the textbox on the right to display only the relevant settings:
You will need to:
- Check the "
enable_s3_uploads" checkbox to activate the feature- Paste in both "
Access Key Id" and "Secret Access Key" in their respective text fields- Enter the name of the bucket you've authorized in the "
s3_upload_bucket"The "
region" setting is optional and defaults to "us-east-1". You should enter the location (eg. eu-west-1, sa-east-1, etc...) that is nearest to your users for better performances.Enjoy
That's it. From now on, all your images will be uploaded to and served from S3.
Note how you did not have to create your S3 bucket? That's because Discourse will automagically create it for you if it doesn't already exists.
Posts: 18
Participants: 9
Bryan wrote:
Getting this error when I try to bootstrap. My yaml says it is valid when I test it. Not sure what to do here...
root@bestindustrygroups:/var/docker# ./launcher bootstrap app WARNING: No swap limit support Calculated ENV: ## ## After making changes to this file, you MUST rebuild for any changes ## to take effect in your live Discourse instance: ## ## /var/docker/launcher rebuild app ## ## this is the all-in-one, standalone Discourse Docker container template templates: - "templates/cron.template.yml" - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/sshd.template.yml" - "templates/web.template.yml" ## which TCP/IP ports should this container expose? expose: - "80:80" # fwd host port 80 to container port 80 (http) - "2222:22" # fwd host port 2222 to container port 22 (ssh) params: ## Which Git revision should this container use? version: HEAD env: ## How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 UNICORN_WORKERS: 2 ## ## List of comma delimited emails that will be made admin on signup DISCOURSE_DEVELOPER_EMAILS: 'bryan@sonomacountybest.com' ## ## The domain name this Discourse instance will respond to DISCOURSE_HOSTNAME: 'http://bestindustrygroups.org' ## ## The mailserver this Discourse instance will use DISCOURSE_SMTP_ADDRESS:smtp.mandrillapp.com DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: bry.bell@gmail.com DISCOURSE_SMTP_PASSWORD: jmHQW3T1pLfaVviP6c8lOw ## ## the origin pull CDN address for this Discourse instance # DISCOURSE_CDN_URL: discourse-cdn.example.com ## These containers are stateless, all data is stored in /shared volumes: - volume: host: /var/docker/shared/standalone guest: /shared ## The docker manager plugin allows you to one-click upgrade Discouse ## http://discourse.example.com/admin/docker hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git ## Remember, this is YAML syntax - you can only have one block with a name run: - exec: echo "Beginning of custom commands" ## If you want to configure password login for root, uncomment and change: #- exec: apt-get -y install whois # for mkpasswd ## Use only one of the following lines: #- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root #- exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'RAW_PASSWORD')" root ## If you want to authorized additional users, uncomment and change: #- exec: ssh-import-id username #- exec: ssh-import-id anotherusername - exec: echo "End of custom commands" - exec: awk -F# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}' #<Psych::SyntaxError: (<unknown>): could not find expected ':' while scanning a simple key at line 37 column 3> cd /pups && git pull && /pups/bin/pups --stdin Unable to find image '##' locally 2014/04/18 16:27:02 Invalid repository name (##), only [a-z0-9-_.] are allowed cat: cids/app_boostrap.cid: No such file or directory Usage: docker rm [OPTIONS] CONTAINER [CONTAINER...] Remove one or more containers -f, --force=false: Force removal of running container -l, --link=false: Remove the specified link and not the underlying container -v, --volumes=false: Remove the volumes associated to the container FAILED TO BOOTSTRAP
Posts: 3
Participants: 2
Optimae wrote:
I set up Discourse on a DigitalOcean install, following this guide: https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md
I configured email with Mandrill and set up a Sending Domain. DKIM and SPF are both valid.
And I'm having the issue that no emails whatsoever are being sent. When a new user registers or when I click to send them their activation link, I see a failed job over at Sidekiq with this message:
{"type"=>"signup", "user_id"=>3, "email_token"=>"cf45c57283d5a5cf81e709f18c25b74e", "current_site_id"=>"default"} Net::OpenTimeout: execution expiredWhich keeps retrying indefinitely.
I've re-checked app.yml configuration and everything is set up as per the guide with the correct Mandrill credentials. When I went through the installation guide again, I saw that I had no UNICORN_WORKERS, so I set that to 3 in case that affects email delivery. No visible difference afterwards.
I've also tried sending test emails from admin/email in the Discourse interface, which produces the following error:
There was an issue sending email. Please check your settings and try again.In case it's relevant, Mandrill and the Discourse installation use the same gmail email address. As far as I know, nothing has to be configured on the gmail end, unless I'm mistaken? Do I need to set up postfix?
I've checked out half-a-dozen or so other topics on this issue, but none of them appear to have the solution for whatever it is I have misconfigured/missing/broken/etc. The only topic with the same error that I could find was: https://meta.discourse.org/t/error-on-sending-email/14300 - I'm already using port 587.
Any help would be greatly appreciated!
Posts: 4
Participants: 2
Montana Harkin wrote:
I had never heard of http://vanillaforums.org/ until today, but it also looks to solve a lot of the same issues that Discourse aims to solve.
What are the main differences between the two? Why would I choose Discourse vs Vanilla Forums?
Posts: 25
Participants: 14
Sam Saffron wrote:
You may wish to host multiple domains on a singled Docker setup. To do so follow these instructions:
We strongly recommend you run a dedicated container
The standalone container is extremely easy to configure, however has a couple of drawbacks
- You will need to stop your site when bootstrapping a new image
- You run through the db bootstrap when uneeded
Multisite is a fairly advanced topic, you should start by running a dedicated data container, it will make troubleshooting much easier.
Understand hooks
Discourse templates use pups, its rules are simple and powerful.
Each rule you run may define a hook:
run: exec: cd: some/path hook: my_hook cmd: - echo 1Later on in your container you can insert rules before or after a hook:
hooks: before_my_hook: - exec: echo "I ran before" after_my_hook: - exec: echo "I ran after"So in the example above you will see output like the following:
I ran before
1
I ran afterYou can read through the templates in
/var/docker/templatesto see what hooks you have available.Provision your multisite db in your data container
Run the following commands to provision a DB in your data container:
hooks: after_postgres: - exec: sudo -u postgres createdb b_discourse || exit 0 - exec: stdin: | grant all privileges on database b_discourse to discourse; cmd: sudo -u postgres psql b_discourse raise_on_fail: false - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "alter schema public owner to discourse;"' - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists hstore;"' - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists pg_trgm;"'This will ensure a db called b_discourse i provisioned correctly.
If you wish you can ssh into your data container and run this manually.
Provision multisite.yml in your web container
In your web container run:
hooks: after_code: - file: path: /var/www/discourse/config/multisite.yml contents: | secondsite: adapter: postgresql database: b_discourse pool: 25 timeout: 5000 db_id: 2 host_names: - b.discourse - exec: cd: /var/www/discourse/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git after_web: - exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrateThis will ensure the multisite.yml file is layed down in the web container and run the migrations code.
Posts: 2
Participants: 2
Régis Hanol wrote:
So, you want to use S3 to handle image uploads? Here's the definitive guide:
S3 registration
Head over to http://aws.amazon.com/s3/ and click on
.
During the create account process, make sure you provide payment information, otherwise you won't be able to use S3. There's no registration fee, you will only be charged for what you use, if you exceed the free usage tier.
User creation
Creating a user account
Sign in to AWS Management Console and click on
to access the AWS Identity and Access Management (IAM) console which enables you to manage access to your AWS resources.
We need to create a user account, so click on the
Userslink on the left handside and then thebutton. Type in a descriptive user name and make sure the "Generate an access key for each User" checkbox is checked.
Here's the critical step: make sure you either download the credentials or you copy and paste somewhere safe both
Access Key IDandSecret Access Keyvalues. We will need them later.Setting permissions
Once the user is created, we need to set him permission. Select the user you've just created in the upper panel, click on the
Permissionstab in the lower panel and then click thebutton.
In the "Manage User Permissions" popup, select the
radio button and click the select button to manually enter the permission.
Type in a descriptive name for the policy and use the following piece of code as a template for your policy document:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:*", "Resource": [ "arn:aws:s3:::name-of-your-bucket", "arn:aws:s3:::name-of-your-bucket/*" ] } ] }Make sure you change both references to "
name-of-your-bucket" with the name of the bucket you will use for your Discourse instance before applying the policy.Discourse configuration
Now that you've properly set up S3, the final step is to configure your Discourse forum. Make sure you're logged in with an administrator account and go the Settings section in the admin panel.
Type in "S3" in the textbox on the right to display only the relevant settings:
You will need to:
- Check the "
enable_s3_uploads" checkbox to activate the feature- Paste in both "
Access Key Id" and "Secret Access Key" in their respective text fields- Enter the name of the bucket you've authorized in the "
s3_upload_bucket"The "
region" setting is optional and defaults to "us-east-1". You should enter the location (eg. eu-west-1, sa-east-1, etc...) that is nearest to your users for better performances.Enjoy
That's it. From now on, all your images will be uploaded to and served from S3.
Note how you did not have to create your S3 bucket? That's because Discourse will automagically create it for you if it doesn't already exists.
Posts: 18
Participants: 9
.
to access the 
button. Type in a descriptive user name and make sure the "Generate an access key for each User" checkbox is checked.
button.
radio button and click the select button to manually enter the permission.
