@watchmanmonitor wrote:
Continuing the discussion from Changing or removing the last poster avatar highlight:
In both these examples on Meta today (April 18, 10:30 PM CST) the OP is the first and last person to comment, but there's someone else who's commented is as well.
Posts: 4
Participants: 3
@rnovino wrote:
is there an official tutorial on how to install multiple discourse in one server? I am planning to install another discourse for another domain but it's still in the same server , so I have no idea how this works hopefully someone can guide thanks.
Posts: 12
Participants: 5
@Dharan wrote:
got error when trying to bootstrap. i checked in ubuntu and rebuilded git pckage. but same issue. Please help me to install in ubuntu 14.04 linode servers.
/var/discourse# ./launcher bootstrap app cd /pups && git pull && /pups/bin/pups --stdin fatal: unable to access 'https://github.com/SamSaffron/pups.git/': gnutls_handshake() failed: A TLS packet with unexpected length was received. cd82f860293acbd174f5582a16ef4593f7543c7b9dbaa3380dd6851e3bda65f2 FAILED TO BOOTSTRAP
Posts: 1
Participants: 1
@probus wrote:
While embedding comments from a Ghost blog with RSS, If the blog post title contains non English characters, the embed fails to create a comment topic. I can find this from sidekiq:
Jobs::RetrieveTopic
Jobs::HandledExceptionWrapper: Wrapped Encoding::CompatibilityError: incompatible character encodings: ASCII-8BIT and UTF-8
Posts: 2
Participants: 2
@steve_pd wrote:
0.6.5 and latest update, single letter avatar URLs are no longer shown on the remote site.
Verified on both live and staging sites.
Posts: 4
Participants: 3
@abarker wrote:
After using the official warning feature, I have come up with a couple proposals that I can't find anywhere else:
- Apply staff color to the OP of the message by default.
- Include
#moderatorsin the message, like with flags. This would remove the need to manually add other staff to the meadage.
Posts: 7
Participants: 5
@tonninseteli wrote:
Apparently on mobile some of my users have had trouble skimming through a topic when the site pauses to load more posts all too often. I've noticed similar problems with other sites that have implemented infinite scrolling, and it is quite annoying.
I would prefer to be able to adjust how many posts are initially loaded, perhaps even set that the whole topic would be displayed if there were less than twenty or even thirty posts or something similar to that, and also how many topics are loaded when reaching the end of displayed posts.
During my commute there are a couple of places where connection is lost, and connection loss is almost unbearably common when travelling long distances by train around here, so this would probably help a lot in those situations.
Any suggestions?
Posts: 2
Participants: 2
@Jong wrote:
I'm admin of forum site which powered by discourse. I have a plan to open new site(power by keystone.js). keystone.js has own User account. But I don't want my forum user can login with forum account without sing up to new site.
I just want to "Signin with Discourse" feature from my new site.
Is this feature already exist or not?
If not, can you give me a hint to Implement?
Posts: 6
Participants: 3
@tobiaseigen wrote:
There is a trailing period that looks lost at the bottom of topic pages. Consider removing it!
Posts: 4
Participants: 3
@wassame wrote:
Hello everyone, I am trying to place the script in my discourse:
<script>document.write('<script src="//sharebutton.net/plugin/sharebutton.php?type=vertical&u=' + encodeURIComponent(document.location.href) + '"></scr' + 'ipt>');</script>Original website: http://sharebutton.net/
I tried placing the code in the head, body and header and it works but once I enable the template, I cannot edit the code or css at all (like there is no textarea to write in), the solution is to disable the template first and then edit the code, but why does it break the code or something?
Posts: 4
Participants: 2
@downey wrote:
Reproduce:
- Ensure email notifications are on for User A for a given topic, such that User A receives an email notification for every reply to that topic. (Or, every post in a category.)
- Have User B reply to the topic.
- Immediately after (1-2 minutes, or within the editing window established), have User C reply to the same topic.
Expected results:
- Email notification from User B arrives before the notification from User C.
Actual results:
- Email notification from User C may arrive before the notification from User B.
Posts: 2
Participants: 2
@Patrick_David wrote:
I have users seeing this problem, particularly on a Samsung Galaxy Tab II, Chrome 42. When entering text into the text wmd-input textarea, the div#wmd-button-bar is above the text input, obscuring the first couple of lines of input.
It appears that due to the width of the viewport, the wmd-button-bar wraps, and this is what causes the obfuscation.
This can be replicated in a desktop browser by resizing the width of the window to below 700px.
I believe this same issue may be related to:
I'm wondering if it makes more sense to check for a min-width, then hide the preview entirely (it seems to work this way on iOS as far as I can tell - no preview, which is nice.
Posts: 2
Participants: 2
@rhulse wrote:
I am setting up embedding of a Discourse forum and I am having trouble understanding how to make it work.
I'm not able to create topics by RSS at this stage so I need to do the creation manually.
My question is how does Discourse tie a topic to the page on the remote site?
(For my use case it would be simpler to put the required topic URL to embed in the JS snippet rather than 'self'. Is that likely to be possible?)
Posts: 3
Participants: 2
@Lee_Ars wrote:
Had some downtime this afternoon and without even really planning to ended up setting up haproxy in front of my web server, which hosts a bunch of stuff including Discourse. The configuration, surprisingly, wound up working without much hassle at all; I give up SPDY support because haproxy doesn't support it, but I don't think that's going to have a whole lot of material effect.
I wound up dragging a second unused server into the mix to work as the haproxy host, but I don't think there'd be any issue in running everything on one box. My stack, when done, is haproxy -> varnish -> nginx, with the main nginx instance serving up my sites (including discourse, which seems perfectly happy being sandwiched behind haproxy and varnish and an nginx).
Why the hell am I doing this? Two reasons: I wanted to go all HTTPS so I could be HSTS compliant, and I also wanted to keep leveraging Varnish as my cache, since at least IMO it's still way better at serving static objects really fast than nginx, even with nginx mainline's caching (which I've since mostly turned off in favor of just letting varnish do its thing).
My haproxy config is pretty straightforward:
global log /dev/log local0 log /dev/log local1 notice chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin stats timeout 30s user haproxy group haproxy daemon # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private ssl-default-bind-ciphers EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl-default-bind-options no-sslv3 no-tlsv10 tune.ssl.default-dh-param 4096 defaults log global option httplog option dontlognull option forwardfor option http-server-close timeout connect 5000 timeout client 50000 timeout server 50000 errorfile 400 /etc/haproxy/errors/400.http errorfile 403 /etc/haproxy/errors/403.http errorfile 408 /etc/haproxy/errors/408.http errorfile 500 /etc/haproxy/errors/500.http errorfile 502 /etc/haproxy/errors/502.http errorfile 503 /etc/haproxy/errors/503.http errorfile 504 /etc/haproxy/errors/504.http frontend haproxyserver bind *:80 bind *:443 ssl crt first-wildcard-cert.pem crt second-wildcard-cert.pem crt third-wildcard-cert.pem redirect scheme https if !{ ssl_fc } acl secure dst_port eq 443 rsprep ^Set-Cookie:\ (.*) Set-Cookie:\ \1;\ Secure if secure rspadd Strict-Transport-Security:\ max-age=31536000 if secure mode http default_backend webserver backend webserver mode http http-request set-header X-Forwarded-Port %[dst_port] http-request add-header X-Forwarded-Proto https if { ssl_fc } server webserver 192.168.0.0:80Not a lot changed from default, but I did make sure to force no SSLv3 and no TLS 1.0 protocols, and sub in the cipherlist I've had the most success with with the SSL Labs tester. Also bumped up the dhparam to 4096.
I have three main domains I serve and I use wildcard certs from StartSSL, and haproxy is really good about accepting all 3 certs and figuring out which one to used based on the requested hostname—zero problems there, so the Chronicles of George and my Discourse instance both get SSL/TLS properly terminated.
My varnish config I left unchanged for Discourse:
sub vcl_recv { ... # Cache only the static assets and pass everything else if (req.http.host ~"discourse.bigdinosaur.org") { if (!(req.url ~ "^/uploads/"||"^/assets/"||"^/user_avatar/" )) { return (pass); } } ... sub vcl_pass { ... set bereq.http.connection = "close"; # Fix broken behavior showing tons of requests from 127.0.0.1 with Discourse if (req.http.X-Forwarded-For) { set bereq.http.X-Forwarded-For = req.http.X-Forwarded-For; } else { set bereq.http.X-Forwarded-For = regsub(client.ip, ":.*", ""); } } ...And my Nginx config without SSL/TLS in it has gotten a lot simpler, too:
server { server_name discourse.bigdinosaur.org; listen 8881; sendfile on; location / { access_log off; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_redirect off; proxy_pass http://localhost:8089; } }Then whatever magic @sam has in the Discourse docker image takes care of the rest.
Posts: 4
Participants: 3
@cpradio wrote:
Okay, so match_count is obviously the number of IPs that were matched to the given rule when a login/registration attempt was made, however, is that is ALL-TIME count or a monthly count?
I'm trying to do some research/statistical analysis on our usage of Screened IPs and am trying to get a better understanding of what this data represents.
Posts: 2
Participants: 2
@cocojoe wrote:
Trying to import a discourse backup ~ 3GB from version v1.3.0.beta5 +97 to latest-release +87.
During the import the following sql issue
[2015-04-21 08:34:05] psql:/var/www/discourse/tmp/restores/default/2015-04-21-083104/dump.sql:3781134: ERROR: could not create unique index "post_timings_unique" [2015-04-21 08:34:05] DETAIL: Key (topic_id, post_number, user_id)=(13868, 7, 6580) is duplicated. [2015-04-21 08:34:05] EXCEPTION: psql failed [2015-04-21 08:34:05] /var/www/discourse/lib/backup_restore/restorer.rb:217:in `restore_dump'
Posts: 3
Participants: 2
@doudou wrote:
If just only discourse installed on a server, and expose 80 to host, how to forbid direct IP visit to discourse?
If someone visit the direct ip address, how to make it return 500 error.
like:
server { listen 80 default; server name _; return 500; }If the nginx/conf.d/discourse.conf in the docker changed, is it permanent?
Posts: 4
Participants: 3
@oganer wrote:
Hi, while testing search feature found that search method in discourse_api doesn't work. It's make requests to
/search.json?term=xbut seems it's wrong. The corrects ways is/search?search=xor may be/search/query?term=xright?
Posts: 2
Participants: 2
@cpradio wrote:
I believe there to be a bug or two in whatever version of highlight.js is being used in Discourse now.
See my test topic at Meta where the curly braces do not line up properly (under certain scenarios).
What is the best approach for looking at getting this resolved?
Posts: 6
Participants: 2
