URGENT: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
Failed to initialize site default
And then opening localhost:3000 I see:
PG::ConnectionBad at / could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
The problem is new and I have run my local Discourse fine before.
So I'm used to working with the apache web server layout, but this is new to me!
I'd like to optimize my community by complying with Google's checklist on google/webmasters. This includes:
Adding a site map
Providing structured data by adding HTML markup to my site's pages
If anyone has already done this, or is able to help me with this - I'd appreciate it!
One last thing.. I also want to edit the .htaccess file, if there is one! I want to make it so that my site complies with SSL connections, so that chrome stops moaning at potential visitors and scaring them away due to "not being secure".
I'm a college professor working on a script to grade student's contributions to discussions. I see that avg_time is the logarithmic mean of post_timings.msec. When I look at data in post_timings.msec, I see that sometimes read times are on the order of 15 minutes. I guess that means that someone opened the page and went and did something else for a while? And I guess this is why we take the geometric mean.
I also wonder what effect it might have to publish post scores would be. If anyone's interested, here's how they are calculated.
Our instance currently has many pinned topics, but I've unpinned some of them for myself, meaning they're still pinned for others. Is there a quick and easy way to re-pin every topic that I've unpinned under my account to see which topics are currently pinned for everyone?
I have to fully read the new plugin api format but my first problem actually has to do with this error:
The discourse/components/post-menu object has been removed from Discourse and your plugin needs to be updated.
PostMenu is a pretty important one and as far as I can tell does exist upon searching the Discourse repo on github. This is what is in the plugin:
import PostMenu from 'discourse/components/post-menu';
import StringBuffer from 'discourse/mixins/string-buffer';
import { iconHTML } from 'discourse/helpers/fa-icon';
import ComposerController from 'discourse/controllers/composer';
...some code inbetween....
PostMenu.reopen({
buttonForLike() {
const likeAction = this.get('post.likeAction');
if (!likeAction) { return; }
var className = likeAction.get('acted') ? 'has-like fade-out' : 'like';
var uId = Discourse.User.current().id;
if (uId%2 == 0) className+= " custom-like"
const opts = {className: className};
if (likeAction.get('canToggle')) {
const descKey = likeAction.get('acted') ? 'post.controls.undo_like' : 'post.controls.like';
return new Button('like', descKey, 'heart', opts);
} else if (likeAction.get('acted')) {
opts.disabled = true;
return new Button('like', 'post.controls.has_liked', 'heart', opts);
}
}
});
I know it's been mentioned before, but I think it was not discussed on enough detail.
While openshift free tier doesn't offer Docker, they give 3 "gears" in their free plan, and each one of them has 512MB of memory.
It should be possible to make Discourse run distributing it's components between these 3 gears, like one for each database and another for rails, or something like that. It wouldn't be easy to do, because it's "cartridges" for rails and the databases are probably not the correct version asked by Discourse, and you can't install arbitrary stuff on the server, that is also redhat based.
If anyone with much more time than money available is looking for a free way to host a small Discourse instance, I think it's worth looking further. Did anyone try it?
So, there is a way to allow JS API requests from domains other than where you Discourse is hosted.
For example, you'd like to embed a topic list that is a result of search by some criteria - and you want to do it with JavaScript only, making it call your Discourse's API.
For this to work, you'll need to enable Cross-origin resource sharing:
For a multi-site setup, you can also use a per-instance setting:
Be it tiny, small, medium or large, may you elaborate please - which are the risks, drawbacks or other negative sides of enabling cross-origins for a particular domain.
In the categories page, the time of the last post is a link but it's broken. On mobile the number of replies is shown and is a link and is also broken.
So I came to know about discourse around 2013 end. There is a saying that first impression is always important. Without a doubt I loved the simplicity of discourse, yet so versatile! At first I was eager to try it so I launched a gaming community without much planning and thinking. Unfortunately didn't work out that well, so had move ahead with the closure. Later on after deep thinking and planning I got this idea of starting an otaku community. As I have some buddies who where interested in it. I moved ahead with discourse again. Here is why.
Simplicity
highly customizable
up to date with cool features.
mobile friendly.
super fast. .... 20 points more ( typing this with a mobile )
Thanks to the #howto I was able to migrate to .MOE DOMAIN without any issue. Plus add letsencrypt SSL.
Both moderators (myself and @8bitcrab) and admins (@sdee and @brad) on the site checked the logs, and we confirmed on Slack that no-one initiated the block manually. No posts appeared for approval or in Akismet. Can you check why the user was blocked please?
Understand what emotion your game is trying to invoke
Allow the player the ability to make the game personal
The details are where the players fall in love with the game
Allow your players to have a sense of ownership
Leave room for the player to explore
If everyone likes your game, but no one loves it, it will fail
Don't design to prove you can do something
Make the fun part also the correct strategy to win
Don't be afraid to be blunt
Design the component for the audience it's intended for
Be afraid of boring your players more than challenging them
You don't have to change much to change everything
Restrictions breed creativity
Your audience is good at recognizing problems and bad at solving them
All the lessons connect
There were several times when transcribing that list that I wanted to bold an item, but I restrained myself. #20 really says all that's needed in that respect.
In the realm of Discourse-specific, many of these just straight-out work if you replace "game" with "product" and "player" with "user".
Number 7 - with trust levels, the forum participants are allowed to take a moderate role in the moderation of the forum, which helps instill a sense of ownership, of "our" community.
Number 19 - the first post's recommended solution on Meta is pretty much always not the correct route, but there is a real problem there
Number 5, Number 18 - freeform tagging.
There are more parallels, but I'll let you think about them on your own
So, I have to download, as per official discourse development guide, vagrant software and then, run vagrant up in the git shell opened from the github desktop client for dicourse's master branch. My question is I get something like this:
The problem is that my internet connection is not very good and it automatically reboots every 2 hours or so. It's speed is also not very fast. So, trying to download vagrant through cmd is hopeless. I have already failed a dozen times. That's why I use Free Download Manager for big downloads like this one.
My question is: How can I download that .box file and complete all tasks that vagrant up does without using cmd?
I can download the discourse-vms.s3.amazonaws.com/discourse-1.3.0.box using FDM but I don't know which folder to put it inside and what else to do (which vagrant up does), for which I need guidance.
First I'd like to say I love the way Discourse is set up; a forum that's both advanced in features/design and simplistic for its users. I lurked around here for quite awhile before laziness stopped preventing me from making an account.
Now, with that said, the forum isn't without its faults. I looked around, and unless I'm missing something, there doesn't seem to be a way to prevent a thread from being closed down from hitting the flag threshold-- even if the thread is made by a TL4/Leader user. This is really inconvenient for large communities where 'disagreements' are more likely to occur.
This is a recent example (And not the only instance of it):
^A poll was made to vote on 3 options, and gamers being typical gamers, look at "opinions" as something offensive which eventually results in users flagging posts. That in turn resulted in the thread being locked 3 times from community flags, which in turn actually prevented the Poll in the first post from even being voted on until it was re-opened by Staff.
If there was an option for TL4+ users to give a thread 'flag immunity' when creating/editing it, this could prevent a lot of headache.
Thank you for the forum, and thank you for your time.
@eviltrout Would it be feasible to move the useful autosize library you wrote from admin/lib to discourse/lib? I've come across it working on Quick Messages and would prefer to use a working existing solution in the project over a 3rd party, or my own, solution. DivResizer doesn't quite fit the purposes of a smaller chat textarea that does not occupy most of the composer.
The problem is that admin code is not available to clients where the user is not an admin (i.e. if a non-admin user's client tries to import a module from admin/lib, it is unable to find it; I'm assuming this is by design for security purposes). The desire to autosize a textarea is relatively common, so it's possible others may find it useful in the future as well.
I recently updated Discourse from 1.4.3 to 1.4.5 and the tagging plugin stopped working. I disabled the plugin.
Now I wanted to try the Feature Voting plugin. Unfortunately I didn't know it only works with Discourse 1.5 beta. I also disabled the plugin after errors showed up.
Now I updated my Discourse instance from 1.4.7 to 1.5.0.beta13b and re-enabled the two plugins.
The problem: both plugins show up in the plugin settings and I can configure them but it seems the plugins are only loaded for the admin section. Whenever I want to add tags to a topic the tag bar does not show up and I also can't enable the feature voting for categories because the option is simply missing. It's like the plugins are not enabled.
Is there something like a plugin cache that got corrupted while trying both plugins with 1.4.5? Or any other cache that may lead to this weird behaviour?
Steps I already tried:
Rebuilding the app (maybe 10 times or more with different settings in the app.yaml)
Deleting the plugin directories from /var/www/discourse/plugins and rebuilding the app
Turning the plugins off and on again in the settings
Am wondering if there's a way to set trust level for sending invites. My discourse instance is small, private and I would like people to invite others to topics even if their trust level is 1 but currently I am unable to find a way to let them do that. Only trust level 2 and above are able to invite. In the initial stages would like let trust level 1 to invite too and then later when there are sufficient members would like to bump up the trust level to 2 to invite others to topics and site.
)
