@Jackson_Cunningham wrote:

We have an existing rails app on Heroku and we're looking to incorporate a community component.

We were going to build this from scratch but then discovered Discourse and it has all the features we need. The ideal setup would allow each section (main app & community) to access the other's data. That way, we could include components from the community into the main app, and we could also tailor the community section to each user.

Is this type of setup possible? Everything I've read so far talks about installing Discourse as a completely standalone project (or subdomain, separated part of an existing app community.mysite.com).

Thanks!

Posts: 2

Participants: 1

Read full topic

@mattdamod wrote:

Hi, all

I am designing a new topic and I want to use an image for the header of the category. There are two questions to this...

1. I'd like to include the name of the category in the image, this would mean that I don't want anything in the title of the category - is that possible or is not possible?

2. What is the best image size (pixels) to use in the category image header?

Cheers

Posts: 3

Participants: 2

Read full topic

@smbogan wrote:

Is there a way to disable the password reset by email feature on the login page? I would like to only allow a password reset when an administrator initiates the sending of the email. The ability of a user to change their password when logged in shouldn't be affected.

Posts: 8

Participants: 5

Read full topic

@RobMeade wrote:

Hi,

I think there is perhaps a minor issue with the above, screenshot to demonstrate;

I'm guessing the two zeros should be words?

Kind regards

Rob

Posts: 3

Participants: 2

Read full topic

@Er00 wrote:

I noticed that one day had significantly (like, 10x) more posts recorded in the last month on the admin panel and dug into it as we need to report such stats and would be asked what had caused it.

This is the output from the forum DB:

post_type | count
-----------+-------
1 | 94
2 | 12
3 | 935

It looks like type 3 is causing the issue here but I'm not sure what that is.

I've checked and it really doesn't look like there were a gazillion posts on that day, but if I can figure out what post_type 3 is then we can maybe work out what's causing the issue. For now, I've just used 106 as the number of posts (ie excluding type 3 entirely) but ideally I'd have more confidence on that decision!

---

Edited to add
Just found this:
"post_type":{"regular":1,"moderator_action":2,"system_action":3}

I think system actions probably ought not to be counted in posts? Unsure about mod actions either really... Maybe only regular posts should be counted for the post count?

Posts: 1

Participants: 1

Read full topic

@Clement_Decou wrote:

The directory views doesn't exist in discourse 1.8 so i don't find the class TopicView...

There is an example of an old code and i want to replace it :
import TopicView from "discourse/views/topic";

TopicView.reopen({

      didInsertElement: function () {
        this._super();
        Ember.run.scheduleOnce('afterRender', this, this.afterRenderEvent);
      },
      afterRenderEvent: function () {
        var is_wordpress = this.get('topic').is_wordpress;
        var creator = this.get('posters.firstObject');
        if (is_wordpress) {
          this.$().addClass("topic_wordpress");
          $('#main-outlet').addClass("is_wordpress");

Etc.

Does the TopicView class still exist in js ?

Posts: 3

Participants: 2

Read full topic

@Gina_Patterson wrote:

I currently have a shared hosting account with Bluehost. I'd like to install Discourse, and understand I need at least the VPN account:

bluehost.png1257x757 50 KB

Is a Bluehost Cloud account an option?
http://cloud.bluehost.com/products/cloud-sites

I know I can use Digital Ocean, but I'd rather not have yet another account to deal with.

Posts: 5

Participants: 3

Read full topic

@Philip_Finlay_Bryan wrote:

"Some problems have been found with your installation of Discourse:
Email polling has generated an error in the past 24 hours" I don't understand this or how to rectify it

Posts: 2

Participants: 2

Read full topic

@zbor wrote:

When the list is Numbered it's fine.

1. Number one
2. Number two
3. Number three

But as soon you have some comments in between list then it resets numbers, no matter what you write.

1. Number four

Some text here

1. Number five

Some text here

image.png905x387 20.6 KB

Posts: 4

Participants: 2

Read full topic

@kuba-orlik wrote:

I think the explanation next to the "allow uncategorized topics" should be a little more descriptive, explaining that staff are immune to this limitation.

Posts: 5

Participants: 3

Read full topic

@ChrisBeach wrote:

In the last few days, two separate members of my forum have commented at their shock when their reply to a notification email was posted publicly on the forum. To them, it wasn't at all clear this would happen - they thought they were replying to the person who wrote the post (and whom the email was "from")

To make things clearer I changed the wording of notification emails (Admin > Customise > Text Content > user_notifications.reply_by_email)

Before

Screen Shot 2017-02-16 at 20.58.47.png938x128 13.2 KB

After

Screen Shot 2017-02-16 at 20.58.19.png954x138 15.6 KB

I think it might be worth considering a change to the defaults here. The affected members really weren't happy about the situation.

Posts: 6

Participants: 5

Read full topic

@erlend_sh wrote:

Originally published at: https://blog.discourse.org/2017/02/the-discourse-encouragement-fund/

For almost a year now, we’ve been doing something that’s considered quite risky for an open source project: Paying contributors. Communities like ours are fundamentally built on intrinsic motivation. Getting money involved can jeopardize the whole ecosystem, but for the past year we’ve been experimenting with a model that lets us pay contributors for mission-critical…

Posts: 9

Participants: 5

Read full topic

@David_Thompson wrote:

Our forum moderators determined that they'd rather have the community invite the 'moderators' group to a topic that needs attention as opposed to creating a post, and using @moderators.

However, this is the error message that pops-up when I try to invite the moderators group:

2017-02-16_15-23-25.png980x359 16.9 KB

Initially thought that "rate limited" referred to how many users I could invite in a 24-hour period, but as a "Regular", I tested this theory by inviting 20+ users to a topic within several minutes.

Perhaps "rate limited" could also refer to how many users can be invited in one-go but our moderators group consists of a measly 14 users.

Another theory I had was that one of the users, "system", couldn't be invited, but that theory proved wrong too. I tested inviting each moderator individually to a topic to make sure that it wasn't a problem with their account but it seems to be fine (I could manually invite all the moderators).

Additional Information:

• The forum that we're using doesn't use email for accounts, but is linked and created by another account unique to each user.

• Unfortunately we don't have another group on our forum, so I can't see if I can invite other groups besides moderators. And the admin is never active, so it's hard to get into contact.

• I just noticed that most Discourse forums don't have the Invite feature for normal topics, just messages. However, would the behavior of a 'normal' topic and a message be the same?

Thanks in advance.

Posts: 4

Participants: 4

Read full topic

@YesYesiAmKamil wrote:

Hi!

I'm trying to add image to default badge but after that i cannot translate the name of that badge through the translate tool: i'm changing the name, but nothing happens. Is it normal?

Posts: 1

Participants: 1

Read full topic

@Der-Eddy wrote:

I wanted to get a log of name changes via the Data Explorer Plugin but can't find anything useful in the db sidebar about this

Could someone head me to right direction? Or is this not being logged? (Besides the one changed by an administrator in the team log)

Posts: 3

Participants: 3

Read full topic

@samliew wrote:

Steps to repro:

1. I have a browser bookmark/link/homepage for https://meta.discourse.org/new?order=category (click on this link first)

2. Now click on "Latest". Posts are sorted incorrectly. Have to click "Latest" a second time to reset sort order.

Expected:

Latest should be sorted by activity on first load.

Posts: 3

Participants: 2

Read full topic

@jomaxro wrote:

From time to time on Meta there are reports of new site staff being surprised by their ability to override site settings without warning. For example, staff can reply to closed topics, staff can post to #uncategorized even if it is disabled in site settings, staff can more posts to a topic that the user cannot see, etc. (An example, another example).

I'd like to propose a just-in-time warning that appears when staff are about to do this. Something like:

image.png695x158 6.48 KB

Here is a (non-exhaustive) list of actions where a similar warning would be useful:

• Replying in a closed/archived topic.
• Posting in the #uncategorized category when uncategorized is disabled.
• Moving a user's post to a topic the user cannot view.
• (Admin only) Posting in a PM the admin isn't a participant in.

Posts: 5

Participants: 5

Read full topic

@zsero wrote:

I'm using Discourse on a VPS with 10 GB SSD space, using stable branch, no swap.
The forum has about 22 MB of total backup data (including attachments).
There is nothing else installed on the server, and never was.

Upgrade couldn't complete, then I did a rebuild which completed but threw errors about no space left on device, yet the forum seems to be back up.

/var/lib/docker is 7.5 GB
/var/discourse is 285 MB

docker images -a says:

REPOSITORY            TAG                 IMAGE ID            CREATED             SIZE
local_discourse/app   latest              dd1e2641ac41        5 weeks ago         2.363 GB
discourse/discourse   1.3.10              1881a9bd3afd        7 weeks ago         1.539 GB
<none>                <none>              02022664486c        8 weeks ago         2.297 GB
<none>                <none>              ea110ef52b9c        8 weeks ago         2.296 GB
discourse/discourse   1.3.9               d2fbe0833acf        9 weeks ago         1.539 GB

Shouldn't there be some automatic cleaning of docker images via docker-gc or similar?

A forum with 22 MB of data should really not have problems with space on a 10 GB VPS.

My only idea is to docker images -qa | xargs -r docker rmi before each upgrade and to use rebuild instead of upgrade every time. But this is a slow and stupid workaround.

Posts: 8

Participants: 4

Read full topic

@zh99998 wrote:

I'm migrating my discourse forum to another database...
I've do backup, create a new one, and restore, but..

[2017-02-17 06:42:41] 'zh99998' has started the restore!
[2017-02-17 06:42:41] Marking restore as running...
[2017-02-17 06:42:41] Making sure /var/www/discourse/tmp/restores/default/2017-02-17-064240 exists...
[2017-02-17 06:42:41] Copying archive to tmp directory...
[2017-02-17 06:44:11] Unzipping archive, this may take a while...
[2017-02-17 06:47:11] Extracting metadata file...
[2017-02-17 06:47:46] Validating metadata...
[2017-02-17 06:47:46]   Current version: 20161216101352
[2017-02-17 06:47:46]   Restored version: 20161216101352
[2017-02-17 06:47:47] Extracting dump file...
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
[2017-02-17 06:48:29] invalid command \N
...many many times
[2017-02-17 06:55:09] invalid command \N
[2017-02-17 06:55:09] EXCEPTION: psql failed
[2017-02-17 06:55:09] /var/www/discourse/lib/backup_restore/restorer.rb:281:in `restore_dump'
/var/www/discourse/lib/backup_restore/restorer.rb:44:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:164:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:20:in `restore!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:81:in `restore'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/config/initializers/008-rack-cors.rb:15:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/conditionalget.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:278:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `<main>'
[2017-02-17 06:55:09] Trying to rollback...
[2017-02-17 06:55:09] There was no need to rollback
[2017-02-17 06:55:10] Notifying 'zh99998' of the end of the restore...
[2017-02-17 06:55:30] Cleaning stuff up...
[2017-02-17 06:55:30] Removing tmp '/var/www/discourse/tmp/restores/default/2017-02-17-064240' directory...
[2017-02-17 06:55:30] Unpausing sidekiq...
[2017-02-17 06:55:30] Marking restore as finished...
[2017-02-17 06:55:30] Finished!

Posts: 3

Participants: 3

Read full topic

@Gina_Patterson wrote:

Got Discourse installed (yay me!) at http://107.170.201.40/. How do I get it to come up at http://discourse.bite-nutrition.com/ ? I know I have to do something with my DNS settings but I don't know what/where to do that.

Bought domain through GoDaddy, domain is still registered there.
Website (https://bite-nutrition.com) is hosted through Bluehost (nameservers point to bluehost).
Using a Digital Ocean droplet for Discourse installation.

I searched for other topics regarding DNS configuration but didn't find what I was looking for.

Posts: 3

Participants: 2

Read full topic