Jacob Chapel wrote:
This keeps happening when I go between my phone and computer on my forum.
My phone for instance will update the unread count and other things like notifications but even though I've viewed the posts on my computer the count doesn't update.
See example:
It only fixes itself with a hard reload of the page. It also has happened the other way with desktop being stuck.
Posts: 2
Participants: 2
CP9 wrote:
As the image shows below:
![]()
Only these types sharing are available. What if my user want to share any other site, they have no way.
So my question is how can I custom my share button or make a plugin to make it possible to share to other site?
Posts: 4
Participants: 4
Martin Törnqvist wrote:
I am trying to setup discourse_docker so I can migrate my old, non-docker installation. The server is on DigitalOcean and runs Arch Linux x64, kernel 3.8.4-1. I'm following this guide and can't get past the step Bootstrap Discourse.
I have installed
dockerandlxc(standard packages). Not sure what aboutaufssupport since I can't update the kernel normally on a droplet, and DigitalOcean's instructions are only for apt-based systems...As the discourse user, I clone discourse_docker to /var/discourse, edit
containers/app.yml, then run./launcher bootstrap app, where rake fails:... I, [2014-09-27T15:44:09.852087 #39] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! NameError: uninitialized constant Onebox /var/www/discourse/plugins/lazyYT/plugin.rb:14:in `activate!' ...If I try this as root, it gets a bit further, then fails with a different error:
... I, [2014-09-27T16:34:02.876802 #38] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake assets:precompile' ... I, [2014-09-27T16:36:44.987772 #5653] INFO -- : Writing /var/www/discourse/public/assets/preload_store-48dc8094f8aedcfa1c243aae5eff1400.js I, [2014-09-27T16:37:42.763873 #5653] INFO -- : Writing /var/www/discourse/public/assets/vendor-b4a7d12c6e9c7418690f53abd46456a1.js /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sass-3.2.16/lib/sass/script/number.rb:53: [BUG] Segmentation fault ruby 2.0.0p576 (2014-09-19 revision 47628) [x86_64-linux] ... -- C level backtrace information ------------------------------------------- Segmentation fault I, [2014-09-27T16:37:45.658779 #38] INFO -- : 2014-09-27T16:34:07Z 5653 TID-osqtuq1zg INFO: Sidekiq client with redis options {:url=>"redis://localhost:6379/0", :namespace=>"sidekiq"} Purging temp files ...There's 8 GB of free space and a few hundred MB of free memory. I have tried rebooting the droplet a few times.
What's going on here? I don't know if it's obvious but I don't know Ruby, Rails or these ecosystems...
Posts: 1
Participants: 1
Rob wrote:
Hi,
Can I install Discourse on my dedicated server. If so could you point me to the install instructions so that I can show my server support how they install it. Thanks
Rob
Posts: 3
Participants: 2
dtester wrote:
For example someone has made many separate topics, but I want to merge or move them all into one big "thread" or topic how do I do this?
Posts: 10
Participants: 4
The long version of me wrote:
When sharing post/topic link to Facebook it would nice to pull avatar of the post creator instead of the image in the post (if any).
Possible reasons:
1.It is nice and always cropped nicely.
2.It gives proper credit to the content shared.
3.Shared post images sometimes are cropped, small, don't fit well.
Posts: 1
Participants: 1
Lee_Ars wrote:
Had a dipshit user register and power-level himself up to trust level 1, then begin sending inane PMs and posting inane messages to threads. Rather than allow flags to accumulate, I'd rather take direct action. Banning's always an option, but honestly, I'd rather have more granular putative measures at my disposal.
Specifically, I'd like to be able to:
1) Toggle on or off a user's ability to send private messages
2) Manually demote and lock a user at trust level 0
3) In lieu of #2, being able to manually create a limited user group (with rate limits set on daily post and topic creation) and drop problem children into it would be a fine substituteIt's not that I want to just eject people all together, but community guided self-adjustment takes time—I'd rather be able to provide an immediate adjustment that's a step of severity in between "nothing" and "ban."
I did indeed try manual demotion via the user's admin panel, but Discourse doesn't like that:
Posts: 2
Participants: 2
van wrote:
I follow this guide to install discourse: [link][1]
When I input ./launcher bootstrap app, I get this error:
fatal: unable to access 'https://github.com/SamSaffron/pups.git/': Could not resolve host: github.com
then
FAILED TO BOOTSTRAPAlso before inputting ./launcher bootstrap app, it is telling me that this user does not have ssh key. press y to generate key.
Any explanation for this or can someone guide me to installing discourse. I am using Digital Ocean 1gb and putty.
Thanks
Posts: 3
Participants: 2
Paul wrote:
Having read this:
and having decided I like the minimum character feature, I was wondering if there was any way to stop people from posting gibberish, as in
feirererfgerkjrehjr rejhhhreuhrer eiruhfruhrehr
You know, as in just banging on the keyboard.
Posts: 1
Participants: 1
Admir Hodzic wrote:
Looks like since version
1.1.0.beta3my discource wont to fetch mails from POP3 server anymore.
Before it worked well bu now there is remaning mails in mailbox
When I look at LOGS i seeJob exception: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
Backtrace
/opt/bitnami/ruby/lib/ruby/1.9.1/net/pop.rb:552:in `connect' /opt/bitnami/ruby/lib/ruby/1.9.1/net/pop.rb:552:in `do_start' /opt/bitnami/ruby/lib/ruby/1.9.1/net/pop.rb:532:in `start' /opt/bitnami/apps/discourse/htdocs/app/jobs/scheduled/poll_mailbox.rb:79:in `poll_pop3' /opt/bitnami/apps/discourse/htdocs/app/jobs/scheduled/poll_mailbox.rb:18:in `execute' /opt/bitnami/apps/discourse/htdocs/app/jobs/base.rb:154:in `block (2 levels) in perform'
ENV:
current_db: default current_hostname: 172.16.0.17 job: Jobs::PollMailbox problem_db: default opts:
Looks like Discourse complain to my self-singed SSL certificates which is installed on my mail server.
Is there a way to make discource ignore unsecured SSL certificate when fetchng mails from POP3
Posts: 1
Participants: 1
Subbu wrote:
I run Bitnami Discourse 1.0.2 currently, I was running 1.0.0 when i took the backup.
Help me in fixing the restore. sorry for the big paste.[Invalid date] 'xxx' has started the restore! [Invalid date] Marking restore as running... [Invalid date] Making sure /opt/discourse-1.0.2-0/apps/discourse/htdocs/tmp/restores/default/2014-09-27-163631 exists... [Invalid date] Copying archive to tmp directory... [Invalid date] Unzipping archive... [Invalid date] Extracting metadata file... [Invalid date] Validating metadata... [Invalid date] Current version: 20140818023700 [Invalid date] Restored version: 20140818023700 [Invalid date] Extracting dump file... [Invalid date] Restoring dump file... (can be quite long) [Invalid date] SET . . . [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] ALTER TABLE [Invalid date] setval [Invalid date] -------- [Invalid date] 1 [Invalid date] (1 row) [Invalid date] setval [Invalid date] -------- [Invalid date] 6 [Invalid date] (1 row) [Invalid date] setval [Invalid date] -------- . . . [Invalid date] 26 [Invalid date] (1 row) [Invalid date] setval [Invalid date] -------- [Invalid date] 1 [Invalid date] (1 row) [Invalid date] setval [Invalid date] Enabling readonly mode... [Invalid date] Pausing sidekiq... [Invalid date] Waiting for sidekiq to finish running jobs... [Invalid date] Switching schemas... [Invalid date] Migrating the database... [Invalid date] EXCEPTION: Error dumping database [Invalid date] /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/tasks/postgresql_database_tasks.rb:55:in `structure_dump' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/tasks/database_tasks.rb:150:in `structure_dump' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/databases.rake:269:in `block (3 levels) in <top (required)>' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `block in execute' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `each' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `execute' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain' /opt/discourse-1.0.2-0/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:172:in `invoke_with_call_chain' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:165:in `invoke' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/databases.rake:43:in `block (2 levels) in <top (required)>' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `block in execute' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `each' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `execute' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain' /opt/discourse-1.0.2-0/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:172:in `invoke_with_call_chain' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:165:in `invoke' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/databases.rake:37:in `block (2 levels) in <top (required)>' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `block in execute' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `each' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `execute' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain' /opt/discourse-1.0.2-0/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:172:in `invoke_with_call_chain' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:165:in `invoke' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/import/importer.rb:257:in `migrate_database' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/import/importer.rb:50:in `run' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/backup_restore.rb:160:in `block in start!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/backup_restore.rb:157:in `fork' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/backup_restore.rb:157:in `start!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/backup_restore.rb:17:in `restore!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/app/controllers/admin/backups_controller.rb:73:in `restore' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4:in `send_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:20:in `block in process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:229:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:229:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86:in `run_callbacks' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:19:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rescue.rb:29:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `block in instrument' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `instrument' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:30:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/params_wrapper.rb:250:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/controller_runtime.rb:18:in `process_action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:136:in `process' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/rendering.rb:30:in `process' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiling_methods.rb:79:in `block in profile_method' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal.rb:196:in `dispatch' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal.rb:232:in `block in action' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82:in `dispatch' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:50:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/mapper.rb:45:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:71:in `block in call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59:in `each' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:678:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.2/lib/rack/protection/frame_options.rb:31:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/builder.rb:59:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:35:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/lib/middleware/anonymous_cache.rb:119:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/params_parser.rb:27:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/flash.rb:254:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.5/lib/message_bus/rack/middleware.rb:55:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/cookies.rb:560:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/query_cache.rb:36:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:82:in `run_callbacks' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:27:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/remote_ip.rb:76:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/logster-0.1.6/lib/logster/middleware/reporter.rb:23:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/rack/logger.rb:38:in `call_app' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/rack/logger.rb:22:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets' /opt/discourse-1.0.2-0/apps/discourse/htdocs/config/initializers/silence_logger.rb:26:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/request_id.rb:21:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiler.rb:193:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/engine.rb:514:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/application.rb:144:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/railtie.rb:194:in `public_send' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/railtie.rb:194:in `method_missing' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each' /opt/discourse-1.0.2-0/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call' /opt/discourse-1.0.2-0/ruby/lib/ruby/gems/2.0.0/gems/passenger-4.0.50/lib/phusion_passenger/rack/thread_handler_extension.rb:74:in `process_request' /opt/discourse-1.0.2-0/ruby/lib/ruby/gems/2.0.0/gems/passenger-4.0.50/lib/phusion_passenger/request_handler/thread_handler.rb:141:in `accept_and_process_next_request' /opt/discourse-1.0.2-0/ruby/lib/ruby/gems/2.0.0/gems/passenger-4.0.50/lib/phusion_passenger/request_handler/thread_handler.rb:109:in `main_loop' /opt/discourse-1.0.2-0/ruby/lib/ruby/gems/2.0.0/gems/passenger-4.0.50/lib/phusion_passenger/request_handler.rb:455:in `block (3 levels) in start_threads' [Invalid date] Trying to rollback... [Invalid date] Rolling back... [Invalid date] Notifying 'xxx' of the end of the restore... [Invalid date] Cleaning stuff up... [Invalid date] Removing tmp '/opt/discourse-1.0.2-0/apps/discourse/htdocs/tmp/restores/default/2014-09-27-163631' directory... [Invalid date] Unpausing sidekiq... [Invalid date] Disabling readonly mode... [Invalid date] Marking restore as finished... [Invalid date] Finished!
Posts: 1
Participants: 1
Justin Gordon wrote:
I setup github oauth per https://meta.discourse.org/t/configuring-github-login-for-discourse/13745
Then when clicking the link, this window pops up.
I just did the docker install, and that put in the beta version of discourse. Is there potentially some serious security issue?
Posts: 3
Participants: 2
flexihack wrote:
I know that using Discourse and taking care of it could be pain in the butt. That's why created this topic to help you out. Currently, I'm available to do forum management for your Discourse forum or you can just contact me for the following:
- Give you advice on which Discourse hosting to use
- Managing your Discourse, if you don't have time. I will make sure that it is up and running smoothly
- And any other consultant related to Discourse
Feel free to pm me. Don't hesitate.
Posts: 1
Participants: 1
Zack wrote:
Hello, im trying to install Discourse on Ubuntu Server, however ive been getting this error all night and I cant seem to fix it. I have tried multiple tutorials and multiple reinstalls of Ubuntu to see if I can fix it, nothing seems to be working. Here is the error I am getting:
root@ubuntu:/var/docker# ./launcher start app WARNING: No swap limit support No cid found, creating a new container Calculated ENV: -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_MALLOC_LIMIT=40000000 -e RUBY_HEAP_MIN_SLOTS=800000 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e HOME=/root -e DISCOURSE_DEVELOPER_EMAILS=zelakto@zelakto.tv -e DISCOURSE_HOSTNAME=community.zelakto.tv -e DISCOURSE_SMTP_ADDRESS=smtp.googlemail.com Unable to find image 'local_discourse/app' locally Pulling repository local_discourse/app 2014/09/28 02:12:54 Error: image local_discourse/app not found root@ubuntu:/var/docker#A fast solution to this would be amazing, thank you for your time. <3
Posts: 8
Participants: 3
Rob wrote:
I am having Discourse put on my dedicated server and the support asked me to relay this error they are having.
We are facing issue during installation. Please share the below error in community and ask for suggestion
root@server [/var/discourse]# ./launcher bootstrap app
which: no docker.io in (/usr/local/jdk/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/root/bin)
ERROR: Docker version 1.1.2 not supported, please upgrade to at least 1.2.0, or recommended 1.2.0Thanks
Rob
Posts: 7
Participants: 3
Graham P Langley wrote:
Continuing the discussion from How to update to Discourse 1.0?:
Hi All,
After following all instructions my discourse has upgraded to V1 fine (running from tests-passed branch) however email is now not working when doing the test from email tab.
I can send email from the discourse server (postfix installed locally) fine to my personal email, but the mail.log isn't showing that discourse has even tried to route mail to it ....
I have checked the settings in app.yml and they are identical to my pre-upgrade snapshot - and mail was flowing fine pre-upgrade
My setup is docker on ubuntu 14.04 with postfix as mail server.
Posts: 2
Participants: 1
CP9 wrote:
I write a post, and share the link to my friends, however, they tell me that there is no post via mobile.
So I have a try, and I find that if a visit the link by mobile, which shows what my friends tell me , but when I goto the homepage , the post that I shared is there , and I can visit it .
Posts: 3
Participants: 2
Joe Seyfried wrote:
Hi there,
I just started to hack away with a new smiliey plugin (based on the original emoji plugin) to make transition from my old forums easier for my user base. However, I ran into an interesting problem: although the original emoji plugin was disabled in the site settings and the editor window displayed my own smiley list all right, the smilies did not get replaced in the posts (or the preview area). Only when I moved the original emoji plugin out of the way, things started working. Chances are that I'm doing something completely wrong, so I'd be glad for any pointers into the right direction. I'm currently wondering if you cannot call Discourse.Dialect.registerInline twice (the emoji plugin does that before it checks if it's disabled or not, so my smiley plugin wouldn't stand a chance to do the same if called second).
I refactored everything to avoid naming collisions, there's no mention of "emoji" in my whole plugin directory but for the Readme.md and the plugins.rb comment line (d'uh, I know).
To illustrate the problem, here we go:
Posts: 1
Participants: 1
van wrote:
I'm pretty new with this whole terminal and using putty.
I have my discourse set up and closed putty since I finished with the set up. Now, I have to open putty again and reconfigure something. How do I enter that session again?
Do I enter ssh root@111.111.111.11 then type out my password?
what's next after that?
nano containers/app.yml?Whenever I type nano containers/app.yml there is no file to edit.
thanks.
Posts: 4
Participants: 2
