I have my website (Wordpress) and Discourse forum sharing the same AWS instance with the same public ip address. The website has the domain name while Discourse forum has its subdomain. Both domain names point to the same public ip address (set in GoDaddy), my app.yml has the subdomain name for discourse forum set.
This probably isn’t the right settings because after rebuilding app both the main domain and subdomain (supposed to go to Discourse) go to my website. Discourse is no where to be seen.
Am I missing something in the setting? Can you shed some light?
We recently had a catastrophic failure of the hypervisor running or Discourse VM, and had to restore from a previous backup. Huge props to the people who on that, it was trivial to restore the site.
My question is about the data lost in the intervening time. Many of my users have mailing list mode enabled, and as such have a complete archive of the lost data. Is it possible to import that data in some way? have some vague ideas about dumping the data to disk in appropriate maildir / mbox format and using the importers… thoughts?
I’ve reached a bit of an impasse and I’m looking for a spot of help.
As part of our switchover to Discourse, we want to change the design of the default email templates and obviously, as only the copy can be changed via the control panel, we figured we’d need to substitute the email templates by building a plugin that allows our email templates to persist between upgrades.
I’ve sussed out how to override the digests, thanks to this thread here:
…however, this doesn’t help when it comes to the notification.html.erb template, which seems to be impervious to ::ActionMailer::Base.prepend_view_path.
I assume this is what is responsible for setting the location of the template file to be used, but see no obvious way to manipulate this without overriding the method in a plugin and admittedly, my experience with Ruby is somewhat limited, so any help you could provide would be very much appreciated.
Hi guys,
For about 4 weeks or longer I have been working on SSO between Auth0 and discourse, on and off. I have gone for different solutions and had to change my approach a few times. I am now at a point where I need further advice.
1- I started by using the SSO approach mentioned in this article:
Recently it has come to light that the redirect approach mentioned in this article (redirecting from auth0 rule to discourse via the SSO login url) results in an incomplete login on Auth0 end, hence a customer login is not registered, which impacts the SSO cookie etc on Auth0 side. So we have to move away from this approach.
2- I have now deployed the 0auth2 plugin and am using the approach specified below:
The issue I have now is the “requirement to verify email” before discourse creates the user record and logs the user in. Is there no way to turn this feature off via the dashboard config?
What is the best approach to work around this if the feature cant be turned off? I dont want the user to have to verify the email in discourse.
I have found a few articles but the seem overly complicated.
Hi everyone! Love discourse, it’s the backbone of our community.
We are an open source project with a strong presence on Github. We have a robot written in Python which manages our Github repositories and does things like merge pull requests automatically if they have been approved. Since we have a lot of repositories and not everyone follows every repository it would be awesome if the robot could post in the forums when a new project is created or when a pull request needs to be reviewed.
Can anyone point me in the direction of how I could best call the Discourse API from Python?
I manage a diabetes online community and have noticed our Google metrics are way different from the Discourse ones. Any idea why? All the settings seem to be okay, i would aprreciate any help or guidance.
I’m trying to figure out a good workflow for managing a live Discourse site and have a few more questions:
1. Development Environment
I have Discourse running on my laptop (Ubuntu 16.04), but the cloned Github repo is missing files like app.yml. Some of the tutorials here in the forum mention that I should edit the app.yml file, but it doesn’t exist in my development versions. How do people manage that difference on production sites? Are the local development versions always different codebases than the live site? Is there a recommended way to have a staging environment for the live codebase too?
2. Backups and Server Migration
I put an experimental Discourse forum online to test workflows before migrating my main site. When I backup the site through the UI, I get the database and uploaded files. How do people generally backup the rest of the site? What else needs to be backed up if I want to rebuild the site on a new server in the event of a disaster (like getting hacked) on the original server? Do I need to backup app.yml or any other files to rebuild it?
3. Upgrades
How do I upgrade a live site? If I click the upgrade button, the live site upgrades, but my local development version doesn’t update. Should I update the sites locally with Git and then push the changes to the live server by creating another remote setting in a fork of the main Discourse repo and working in a custom branch? Or do people generally have a development version that is a completely different installation of Discourse?
4. Plugins
Is it correct that I should write my plugins in separate repos, clone them to the live server, and then symlink them in the plugins directory? Or should I use app.yml to install them? Different posts in the forum here seem to suggest different things.
Simple counters for total posts, visits, searches, users, topics and a gauge for currently active users should be enough to do fun stuff like very granular graphs for what hours your site is busy, alerting if there is a sudden spike in new users, posts and so on, and it would be easier to correlate the existing performance stats with user activity.
The built-in graphs are great of course, but the more stuff I can add to a Grafana dashboard the happier I get
I am not sure if this behavior is intentional or not.
Prerequisites:
Have a custom footer in your Discourse (mine is defined in my theme /common/footer.html)
Have a group in your Discourse
Repro steps:
Click on the “hamburger menu” and go to “groups”
Select a group
Click “Activity” in the nav pills menu
Click “Topics” in the stacked nav menu
observe that when you scroll to the bottom (or inspect the DOM) the custom footer isn’t there.
Expected Behavior:
The custom footer shows on all pages
This felt like an issue in my development environment of Discourse. However, when I was testing it on Discourse Meta it made me realize that maybe the footer was intentionally not added to this page. Possibly due to the infinite scrolling?
I’m just starting to learn how to use the Discourse API.
I’ve got data coming back when I send an api_key and api_username to an endpoint.
However, specifying the user by their username seems mysterious and brittle. I need to know the right username but the user can change their username and I don’t know what it actually is from outside.
My Discourse users can only import an account from my Bubble app. In the SSO section there’s an ‘external id’ that looks like it’s the account’s unique id from Bubble.
Is there a way to specify the user I want based on their external id instead of their username?
I disabled “Prioritize username in ux” but the usernames are all that show still. I simply cannot get the names to show on posts at all.
I don’t know if there is something else necessary, but I logged in on another browser and the problem remained. I’m running the latest code (rebuilt in order to enable ssl this afternoon).
I installed bitnami discourse by using binami launchpad google, the forum is successfully launched, however, the new user is not receiving Activation Email, what should I do about it ? Anyone had experience of this before, thank you very much and the discourse installed looks a very old version, how to upgrade the things?
I was exploring some data this evening and came across the score and percent_rank fields in the topics table. But it wasn’t immediately obvious to me what these fields are, how they are calculated and what they are used for. I can spelunk through the source code if necessary, but I thought I’d ask if anyone has the TL;DR; on that info close at hand first.
As requested by @sam, a little color on what an influencer Dashboard metric might look like as I see it. Please feel free to share your thoughts. And my apologies if I understate anything. I’m still pretty new around here.
Trust levels and badges have taken Discourse far in the way of building a loving community. Perhaps it could be gamefied with an influencer leader board and weekly competition akin to what Swarm app does for social check-ins, and visualized as most influential people in the administration dashboard. This may also satisfy some individuals’ competitive itch while improving user retention for self-starting community builders.
and the discourse installed looks a very old version, how to upgrade the things?
