Joshua Hogendorn wrote:
Feature suggestion time! Would it be possible for there to be a moderator/admin button for 'merge all these posts'? For when people can't get their thoughts together and post 6 times in a row on a topic.
Posts: 5
Participants: 2
Johan wrote:
I needed it for my own project, so I decided to quickly create a PHP class for Discourse SSO login via PHP-driven sites.
The class exposes 3 help functions for quickly integrating Discourse SSO to your existing PHP site.https://github.com/ArmedGuy/discourse_sso_php
Feel free to post suggestions/bug reports etc etc. =)
Posts: 1
Participants: 1
Johan wrote:
Quickly threw together an npm package for Discourse SSO as well.
It follows the same format as my PHP class.https://www.npmjs.org/package/discourse-sso
Repository on GitHub:
https://github.com/ArmedGuy/discourse_sso_node(Figured a new topic would be better than having 2 languages in the same)
Posts: 1
Participants: 1
Erlend Sogge Heggen wrote:
A couple things are wrong with this image. This is a post that was split off from another thread:
- It says that codinghorror was the one who created it (it's the same in the forum index, his avatar comes first). That's a bug really.
- Although the right sidebar contains a link to the thread this was split from, I don't think that's obvious enough, as that could quickly be dismissed as just some post that is linking to this one. It would be really nice if the "In reply to" tab was kept, or at least the "Continuing the discussion from..." was used.
Posts: 4
Participants: 2
Jeff Atwood wrote:
Wow, this is all pretty fascinating to me to see the business evolve in real-time. This is better than watching episodes of The Walking Dead. Well, maybe not..
I'm kind of curious now. Since the code is under the GPL, can I just fork it and call it something like "Odapolis" and create my own logos?
I'm not going to do this, but I'm just curious about the busienss model for CDCK.
Posts: 3
Participants: 2
alphydan wrote:
My landing page shows categories. However their order seems to change every time I login. And they change for other users not logged in. (I think according to popularity or views). This means that often the meta category where the forum is introduced ("welcome to this forum about X") ends up at the bottom of the page (not so popular category) ... and some popular but rather random article ends up at the top. So this can leave new users confused, and regular users searching for their category which has now changed positions again.
Q: Is there a way to organize categories in the /category/ page?
I would like to have:
Top left: The meta category (welcome, etc)
Top right: Some other important categoryand the other ones below. Is there any way to control this behaviour?
Thanks!
note that I have read http://meta.discourse.org/t/organizing-the-homepage-after-login/6954/5 but it's still not clear if anything beyond popularity + latest can be done
Posts: 11
Participants: 5
Paul Apostolos wrote:
I implemented the official single sign on for Discourse ( https://meta.discourse.org/t/official-single-sign-on-for-discourse/13045?u=paully21 thanks @sam ) in ASP.NET MVC.
I posted a Gist of a simple implementation using only a controller method here:
( https://gist.github.com/paully21/9232979 )
Hopefully others will find this useful.
Paul
Posts: 4
Participants: 2
Johan wrote:
The current grey background in the user profile page looks like a placeholder for something that could contain an image.
What about adding an option to link/upload a background image Twitter/GPlus style.
There could be an option to tile the background image like Twitter has.
PS. My email is public on my website, don't worry bout it. =)
Posts: 17
Participants: 7
Sam Saffron wrote:
Only include actual maintained sso implementations in this category.
Posts: 3
Participants: 2
Scott Schaffter wrote:
I was trying to run the rake db:migrate and get this... not sure why its happening. We are on a ubuntu setup similar to the ubuntu install guide. Any thoughts? Works fine on local VM.
As an aside - it seems like docker is now the preferred install - would it be worth upgrading?
Permission denied - /var/www/discourse/plugins/poll/auto_generated /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:245:in `mkdir' /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:245:in `fu_mkdir' /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:219:in `block (2 levels) in mkdir_p' /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:217:in `reverse_each' /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:217:in `block in mkdir_p' /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:203:in `each' /home/discourse/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:203:in `mkdir_p' /var/www/discourse/lib/plugin/instance.rb:65:in `ensure_directory' /var/www/discourse/lib/plugin/instance.rb:37:in `block in generate_automatic_assets!' /var/www/discourse/lib/plugin/instance.rb:35:in `each' /var/www/discourse/lib/plugin/instance.rb:35:in `generate_automatic_assets!' /var/www/discourse/lib/plugin/instance.rb:151:in `activate!' /var/www/discourse/lib/discourse.rb:73:in `block in activate_plugins!' /var/www/discourse/lib/discourse.rb:73:in `each' /var/www/discourse/lib/discourse.rb:73:in `activate_plugins!' /var/www/discourse/config/application.rb:152:in `<class:Application>' /var/www/discourse/config/application.rb:29:in `<module:Discourse>' /var/www/discourse/config/application.rb:28:in `<top (required)>' /var/www/discourse/Rakefile:5:in `require' /var/www/discourse/Rakefile:5:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/rake_module.rb:25:in `load' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/rake_module.rb:25:in `load_rakefile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:637:in `raw_load_rakefile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:94:in `block in load_rakefile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:93:in `load_rakefile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:77:in `block in run' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:75:in `run' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/bin/rake:33:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load' /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>'
Posts: 7
Participants: 2
Sam Saffron wrote:
Deploying Discourse on Docker is currently our recommended setup. It avoids many pitfalls installations have, such as misconfigured nginx, sub-optimal Ruby defaults and so on.
The Docker based setup ensures we are all on the same page when diagnosing installation issues and completely eradicates a class of support calls.
Today, all sites hosted by Discourse are on Docker.
This is a basic guide on how to move your current Discourse setup to a Docker based setup.
Getting started
- Get a blank site with working email installed.
Follow the Guide at: https://github.com/discourse/discourse_docker and install a blank site.
Tips:
- Bind the web to a different port than port 80, if you are on the same box. Eg:
expose: - "81:80"
- Be sure to enter your email in the developer email section, so you get admin:
env: # your email here DISCOURSE_DEVELOPER_EMAILS: 'my_email@email.com'
Make sure email is setup and working by visiting
/admin/emailand sending a test email.Make sure you have ssh access to your container
./launcher ssh my_containermust work.If any of the above is skipped your migration will fail.
At the end of this process you will have a working website. Great, time to move on.
Exporting and importing the old site
- Ensure you are running the latest version of Discourse
We had bugs in the export code in the past, make sure you are on latest before attempting an export.
- On your current instance
- go to
/admin/backupsand click on thebutton.
- once the backup is done, you will be able to
it.
On your newly installed docker instance
- enable the
allow_restoresite setting- refresh your browser for the change to be taken into account
- go to
/admin/backupsandyour backup.
- once your upload is done, click on the
button
Destroy old container
./launcher destroy webChange port binding so its on 80
Start a new container
Yay. You are done.
Posts: 2
Participants: 2
Kamal Patel wrote:
Haven't seen any formal reviews of paid discourse hosting, so here's a brief one.
Requirements: I'm starting/helping two new forums, using Discourse for each, and chose Discoursehosting.com to get the first one off the ground. They take care of updates and backups.
Price: Was first going to choose DigitalOcean's $10 or $20 plan, but since I won't have a ton of traffic for a while and am low on time and sysadmin experience, chose Discoursehosting's (aka @michaeld's) basic plan for $20 a month. Also thought about waiting for the formal Discourse hosting option, but my needs were pretty basic.
Support: They answered my pre-sales and post-sales questions within either a couple hours or less than a day. The forum went up almost instantaneously. They have a pretty simple admin dashboard to handle DNS, but other than that you can just head straight to Discourse admin.
Overall: It's all good so far! If you're low on time or expertise, I'd recommend them for sure.
Posts: 2
Participants: 2
Logan Rosen wrote:
I saw that the Ubuntu installation/upgrade guide on git was deprecated, which made me concerned about future support for our installation. Should we consider switching to Docker, or can we stay where we're at and expect that upgrades will work properly?
We're running DB and redis separately, and it looks like Docker packages them all into one container. If we were to split them out, would that break Docker upgrades?
Posts: 3
Participants: 3
Leung Aaron wrote:
I would like discourse to have this feature :
On the left hand side of each post , there is a thumbnail showing the 1st uploaded / linked picture.
The thumbnail doesn't need to be large, for example Reddit is just using a 70px size thumbnail.
This can let readers get more interested by have a sneak preview of what's inside the thread by attractive graphics.
( Of course, this should be set as an option, so any admin who doesn't like this function can enable / disable at will )
Posts: 2
Participants: 2
Neil wrote:
Continuing the discussion from Internationalization / localization, which has become a massive, unfocused topic:
Let's talk about translation tools and the process for getting translations done. If we were going to adopt a third-party tool to get translations done, which should be used? From the Internationalization / localization topic, there seem to be two leaders: Transifex and Localeapp.
Here are the things we need from a translation process:
- Notifications for translators when there's work to do, only for the languages they care about.
- No cost to translators.
- An easy way to upload our english yml files without clobbering anyone's work, ideally using an API.
- An easy way to get all the translations and add them to the Discourse repo in github. We must be able to automate this so it's a one-click operation!
I played with Transifex briefly, and it seems to have a very nice interface for translators. It has the ability to watch languages, leave comments on translations, tagging, etc.
Does anyone know about automation of this whole process?
Posts: 40
Participants: 13
dhyasama wrote:
I installed Sam's docker setup but can't ssh to the running container. I added an ssh key but am prompted for root@0.0.0.0's password when running ./launcher ssh app. Any suggestions?
Posts: 17
Participants: 8
Katie Hunter wrote:
Hi, i am not aware if whether or not Discourse uses sphinx for its search function http://sphinxsearch.com but it is very powerful and light. I know on my forum which uses Vbulletin, i had to integrate the sphynix search which works really well than the Mysql default search which comes with VB =) b/c we have around 5 million posts and 1.7+ million members. Vb Mysql default search was not the right approach for big to growing communities.
Does Discourse uses it for their search function? If not, i would really recommend it and if there is any plans for it?
Posts: 8
Participants: 5
Benjamin Kampmann wrote:
Heyah,
I'd like to open the debate on the item no 5 of the Contributors Guide of discourse:
5. Commit
First, ensure that if you have several commits, they are squashed into a single commit:
My question is pretty simple: Why?
pro
From all I got, squashing into a single commit (and rebasing in general) serves mainly two goals: In a review-system, where you send patches via email a single commit is easier to review than a bunch of them. Secondly, it is about keeping a clean git history of single branch with one-parent-only-commits, making it easier to get back in time and follow what was going on when (supposedly).
is that so?
Both of these arguments kinda don't seem to apply here, as we are using the Github Pull-Request system, which a) gives a very pretty view page for reviewing with one-single-resulting diff to review and comment and b) creates a merge-commit anyways instead of fast-forwarding a rebased commit ergo messing with the history in the same ugly way (as the graph shows). Our history is already messy and will stay messy, squashed single-commits won't change that. So, I don't get why there should be one squashed commit in the Pull-Request only. Am I missing some good reason here?
contra
On the other hand, messing with the history has a bunch of disadvantages. I'd like to point out the following two impacting us:
For once, the history shows the development but also the review process:
Thinking of the review of a big patch and few lines need to be changed after the first iteration of reviews. So to check up on those issues is very easy in a normal history, where you just look at those changesets commited since the comment (in the pretty github pull-request timeline it is even more convenient). Instead with a newly squashed commit, you can't follow that change anymore easily, as the whole changeset is "new". Reviewing becomes a pain as you'd need to review the entire patch every time again. Reviewing big patches becomes just impossible.(Aside from the person doing the changes having to
push --forceevery time they did what they've been asked to do - which feels clearly wrong.)But more over, it makes it impossible to base future work on work in review:
I have a pull-request for a stand-alone feature on github right now. Following this feature I have two others that depend on this one, I could easily start to develop now already, while this one is in review. But as squashing and rebasing commits creates new commits in the history, I can't base my work on top of this branch right now. The second the review requires, the commit I branched from will be gone and I will have a conflict later when getting this merged. Which is clearly not a problem, if there was a history of changes to rely on. Especially pull-request that might spark some longer discussing (like this one is), this is stalling time on future features, too. I'd rather work on the future features, also giving this pull-request more context and insight what is meant for instead.So, maybe I am missing some great reason to use squashed commits for our pull-requests here, but I don't see how these drawbacks are a good trade-off. Please enlighten me.
Posts: 5
Participants: 2
Shiv Kumar wrote:
What's the recommended method for testing plugins? I'm mainly referring to Unit tests, but Integration would be interesting to hear about, too. Can we simply create a
testfolder in each plugin's directory? Would that register properly?
Posts: 8
Participants: 4
jon wrote:
Sorry to ask a dumb ? but is there a chat service that currently exists or is planned in discourse? Would like to see but understand if outside the scope.
thx
Posts: 2
Participants: 2
button.
it.
your backup.
button
