Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60613 articles
Browse latest View live

Uploads to S3 broken, Backups to S3 work

$
0
0

Jim wrote:

I'm attempting to integrate S3 uploads with my Discourse instance. I'm using version 0.9.9.4 running in a docker container. I've filled in all the settings related to S3 uploads and S3 backups.

The Uploads aren't showing up on S3 but when I ran a backup it did show on S3.

Sidekiq shows the following:

I've tried to find more detailed error info but have come up empty handed. From what I gather it may be an issue with my S3 settings, yet those settings did work for the backup.

Any ideas?

Posts: 4

Participants: 3

Read full topic


Home page auto redirected to category

$
0
0

Leung Aaron wrote:

I have a discourse running under the domain name of http://loveliver.co .
I didn't know starting from when, my forum auto directed my home page from
http://loveliver.co , to http://loveliver.co/categories ( but on top of the address bar, it still shows http://loveliver.co )

Actually this is what I prefer first-time users to see as the 1st landing page as default , but in fact I didn't set anything to do so, this is a weird situation, and I suspect the problem above leads me to have some another problems happened in my discourse , i.e. after logout (or a new user access my web page) , a broken home page screen appeared :

I tried to make a new droplet and start install discourse from scratch.
When it is clean, everything is fine.
After I restore my backup data , at the beginning it was still fine, until I use it for a short time, and all the above problems will re-appear.

Are there something corrupted in my discourse forum data ?
I am quite puzzled right now.

PS. there is also a quite minor problem in my setup I have found, that is I am unable to delete any categories right now, is this a common problem for all discourse setups right now ?

Posts: 4

Participants: 3

Read full topic

Basic plugin template

$
0
0

Paul Apostolos wrote:

I need to create a plugin to implement some custom functionality for our forum. I have looked at a bunch of plugins on GitHub but I am wondering if there is a sort of template to follow.

It seems I just need a plugin.rb file and then a replication of the folder structure of Discourse for the files I want to replace or add included.

Is that right?

What is the purpose of the plugin.rb file? I am not going to be replacing or adding any javascript files only rb and erb files.

Actually, is that even possible with a plugin; replacing a core rb and erb file?

Posts: 1

Participants: 1

Read full topic

What's your mockup tool?

$
0
0

fantasticfears wrote:

Few days ago, I ask @riking and @erlend_sh about what tools they use for mockup. Here it's their reply to me.

@riking: Usually just the dev console. Type CSS in. In extreme cases, I draw freehand circles using my touchscreen and Paint.

@erlend_sh: Yeh, the dev console and a paint tool should suffice for 95% of all mockups. For most of my mockups I just copy existing UI elements in Discourse and reuse them in new places.

Maybe I'm going too far to look for great tool...For a mockup, there may be no need to take advantage of complicated tools but easily one. So how you make the mockup?

Posts: 3

Participants: 2

Read full topic

Home page 404s if top_menu is garbage

Change from chosen js to select2 js

$
0
0

nXqd wrote:

Beside some advantages being discussed here :

But this maybe already out of date. The reason I want to change to select2 because we don't need to type a "correct" string at the beginning to match options, select2 matches the text options partially.

If you are ok with this, I will create a pull request on this.

Try select2 here : http://ivaynberg.github.io/select2/

Posts: 4

Participants: 3

Read full topic

Only notified for first like

$
0
0

Kasper Peulen wrote:

If I write a post, I get a notification when somebody likes it.
This is something I like, you know, I like to be liked ! smiley

But.. for the second, third, fourth like, I don't get a notification anymore.
I may sound a little childish, but I would like to get a notification for that as well.

I'm not sure if this is on purpose or if this is an bug. But I would tell you my observation.

  • I start a topic, and I get a like, and I see a notification
  • some more posts happen in that forum
  • couple of minutes later, I see that my topic got 4 likes, but I never got a notification for that

Posts: 5

Participants: 5

Read full topic

Lightbox on onebox


Add option to name backups

$
0
0

Tobias Eigen wrote:

I have been playing with my site and am realizing that I will be making activeuse of the backup/restore system. But I don't know what each backup is that I am looking at - would be very helpful to see whether it's an automated daily backup or a backup that I made just before testing some new feature. So an ability to name the backup or describe it as I create it would be helpful, and a name and timestamp of daily backup as well.

Posts: 1

Participants: 1

Read full topic

Images Not Loading

$
0
0

Clever Moniker wrote:

What would cause an image to not load?

I have all the settings to support the image extensions in jpg. Yet, they won't load the specific jpg. Some jpegs load, some don't. frowning

Any ideas?

Posts: 10

Participants: 4

Read full topic

When a category is renamed, the previous URL should redirect to the new one

$
0
0

Camille Roux wrote:

Hi,

When a category is renamed or moved in a new parent category, its URL is changed. Sadly, the previous URL returns a 500 error, which is bad for SEO.

Posts: 9

Participants: 3

Read full topic

Moderators can access PMs that they are not invited to

$
0
0

cpradio wrote:

Continuing the discussion from Impersonation and reading private messages:

As stated in the above, moderators, who are not allowed to impersonate other users, can access other user's PMs by altering the URL.

Posts: 2

Participants: 2

Read full topic

Can't update expired SSL certs

$
0
0

David Celis wrote:

My SSL certs for my discourse forums recently expired. I uploaded my new certificate/key pair and overwrote the old ones. I then destroyed and re-bootstrapped my Docker container, but my web browsers (and the openssl CLI) still report my cert as being expired. I've reset my browser to make sure it isn't a caching issue. I've tried re-bootstrapping the container again, but no dice. For some reason, it isn't loading the new cert.

Posts: 4

Participants: 2

Read full topic

Username title layout issue on mobile

Invite user to a group

$
0
0

Sam Saffron wrote:

Users may be invited to the site and prestaged in a group.

Upon account creation the user will be added to this group.

This feature is useful when you wish to invite a group of private beta testers, employees, etc.

This feature is only available to forum admins

Using the UI:

Using the API:

require 'discourse_api'
client = DiscourseApi::Client.new("somesite",port)
client.api_key = "your key"
client.api_username = "an_admin"

client.topic_invite_user(topic_id: 1, email: "bob@bob.com", group_ids: "1,2,3")
client.topic_invite_user(topic_id: 1, email: "bob@bob.com", group_names: "bugs,cars,testers")

Limitations

At the moment you may not invite users to predefined groups such as, trust level groups, admin, mod or staff groups.

Posts: 2

Participants: 2

Read full topic


Categories SQL dump from backup for upload

$
0
0

Frank wrote:

I have a few hundred subcats I need to upload to the categories table. I have an excel file of the tab delimited records that currently exist in the categories whcih I have scraped from the SQL dump file.

I need to clarify what I am seeing first and I am not sure what is required. It looks like some have default values but others may not.

I have a question about few of the fields and a few other related things. So here is the table as I see it in the dump file.

id,
name,
color,
topic_id,
topic_count,
created_at,
updated_at,
user_id,
topics_year,
topics_month,
topics_week,
slug,
description,
text_color,
read_restricted,
auto_close_hours,
post_count,
latest_post_id,
latest_topic_id,
"position",
parent_category_id,
posts_year,
posts_month,
posts_week,
email_in,
email_in_allow_strangers,
topics_day,
posts_day

Question one: id and topic_id, I have a feeling topic_id is the primary key? but what is ID?

Question two: created at and updated at...do these have a default value or do I need to provide one.

It looks like this: 2014-05-11 20:00:51.567719 I can create default if I need to.

position...I am not sure this field is what I think it is. I would think it is a 'sort order' field so I can see categories arranged in the way I want. But I am not so sure. I used the position field under settings in the categories lightbox window and changed things up. I exported but I saw no changes which leads me to believe this is handled in another table a reference table perhaps?

I balled things back up in that tarball gz thing and uploaded it to see the small changes I made to position. I didn't see any change which again leads me to believe that position is somewhere else.

I never used postgres and I am noting a seq table. For categories. Is postgres one of those databases like Oracle that are not designed to auto increment on ints the the tables with the primary key? If this is the case, do I need to trip that increment number on the sequence table so if I add a category manually the system doesn't barf or is the system intuitive enough to check the sequence against the highest number in the topic_id field and grab the next incremented value?

Once I know these things, I will:

  • prepare my categories in excel
  • then cut and paste them back into the sql dump file
  • then add that SQL file back to the tarball gz
  • upload the .gz file to my discourse app where it will run its process on upload.

Does this last part sound like the right approach?

Thanks,
Frank

Posts: 3

Participants: 2

Read full topic

"New Topic" indicator on mobile is wrong color

Naked domains and the docker install

$
0
0

Justin Gordon wrote:

Any special advice or info on setting up discourse to without a subdomain? I'm setting up a site specifically for just a forum (at least that's the original intent). Thus, I've been advised to use mydomain.com rather than say www.mydomain.com. Any advice in regards to using a "naked" domain for this? Or pros and cons? I prefer that folks type mydomain into the address bar rather than www.

There's an interesting discussion here regarding the use of www: http://no-www.org/.

Posts: 3

Participants: 3

Read full topic

Add tooltips to Admin & Moderator fontawesome glyphs in topic view?

$
0
0

Lee_Ars wrote:

Now that admin & moderators have their fontawesome trophy/wand glyphs displayed next to their usernames in topic view, it'd be nice to have a tooltip for that particular element so that users can see what the glyphs mean. The glyphs are used consistently throughout the Discourse admin UI, but they're not given any meaning or context anywhere that regular users can see (beyond the fact that they're some kind of username flare that's probably important).

Just an element title tag with "Administrator" or "Moderator" would be perfect.

Posts: 1

Participants: 1

Read full topic

Error with Docker image

$
0
0

Justin Gordon wrote:

I'm getting an error when doing the bootstrap. I've tried twice. This is with a naked domain. I'm going to start over using a subdomain.

I, [2014-05-12T03:11:12.702035 #33]  INFO -- : > cd /var/www/discourse && sudo -E -u discourse bundle exec rake db:migrate
2014-05-12 03:11:19 UTC ERROR:  relation "users" does not exist at character 323
2014-05-12 03:11:19 UTC STATEMENT:                SELECT a.attname, format_type(a.atttypid, a.atttypmod),
	                     pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
	                FROM pg_attribute a LEFT JOIN pg_attrdef d
	                  ON a.attrelid = d.adrelid AND a.attnum = d.adnum
	               WHERE a.attrelid = '"users"'::regclass
	                 AND a.attnum > 0 AND NOT a.attisdropped
	               ORDER BY a.attnum

rake aborted!
NoMethodError: undefined method `word_count=' for #<Post:0x007f9f90cfb458>
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:46:in `eval'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/attribute_methods.rb:206:in `method_missing'
/var/www/discourse/lib/post_creator.rb:93:in `before_create_tasks'
/var/www/discourse/app/models/post.rb:324:in `block in <class:Post>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:438:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:438:in `block in make_lambda'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:160:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:160:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/callbacks.rb:306:in `create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/timestamp.rb:57:in `create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/persistence.rb:482:in `create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/callbacks.rb:302:in `block in create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/callbacks.rb:302:in `create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/persistence.rb:103:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/validations.rb:51:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/attribute_methods/dirty.rb:21:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:268:in `block (2 levels) in save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:329:in `block in with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:326:in `with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:268:in `block in save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:283:in `rollback_active_record_state!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:267:in `save'
/var/www/discourse/lib/post_creator.rb:220:in `save_post'
/var/www/discourse/lib/post_creator.rb:60:in `block in create'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/lib/post_creator.rb:56:in `create'
(eval):23:in `block (3 levels) in run_file'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:208:in `transaction'
(eval):8:in `block (2 levels) in run_file'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:46:in `eval'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:46:in `block (2 levels) in run_file'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:58:in `block in open'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:57:in `open'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:57:in `open'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:36:in `block in run_file'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:219:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:35:in `run_file'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:26:in `block in run'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:25:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:25:in `run'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/seed-fu-discourse-2.2.1/lib/seed-fu.rb:29:in `seed'
/var/www/discourse/lib/tasks/db.rake:3:in `block in <top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)

then later, this failure:

/pups/lib/pups/exec_command.rb:85:in `spawn': cd /var/www/discourse && sudo -E -u discourse bundle exec rake db:migrate failed with return #<Process::Status: pid 301 exit 1> (RuntimeError)
	from /pups/lib/pups/exec_command.rb:55:in `block in run'
	from /pups/lib/pups/exec_command.rb:53:in `each'
	from /pups/lib/pups/exec_command.rb:53:in `run'
	from /pups/lib/pups/command.rb:6:in `run'
	from /pups/lib/pups/config.rb:85:in `block (2 levels) in run_commands'
	from /pups/lib/pups/config.rb:76:in `each'
	from /pups/lib/pups/config.rb:76:in `block in run_commands'
	from /pups/lib/pups/config.rb:75:in `each'
	from /pups/lib/pups/config.rb:75:in `run_commands'
	from /pups/lib/pups/config.rb:71:in `run'
	from /pups/lib/pups/cli.rb:31:in `run'
	from /pups/bin/pups:8:in `<main>'
0abcda0756eabcab60ef35add08a2731f6a655e82cd3e17a963e582f65559cac

Posts: 4

Participants: 2

Read full topic

Viewing all 60613 articles
Browse latest View live




Latest Images