Word to the Bird Dec 27 9:34PM 2017 GUI
on the main issues page it just shows you page after page of issues but there is no option to search... Will this ever happen?? i feel like i ask questions that have already been answered
Nelvin Dec 28 4:00AM 2017
As a workaround, you can use Google with a search limited to the issues url here, like f.i. type
site:duplicacy.com/issue backup
into google search to look for issues including the word backup. I know it's just a partial solution as the results depend on what google has already indexed and there's quite a bit of the newest issues missing, but still might be good for a quick first search.
gchen Dec 28 1:39PM 2017
Yes, a google search is the only way to search for past posts. It is okay to ask the same questions again -- I don't mind it and in fact there have been so many changes so old answers may not apply any more.
towerbr Dec 28 7:08PM 2017
I would like to suggest that you evaluate the Discourse platform for the forum .... Discourse at GitHub
An example:Rclone forum
Some advantages:
And a more beautiful look ... ;-)
And I also think that the entry in the above menu could be "forum", not "issues".
Only humble suggestions ...
gchen Dec 29 1:07PM 2017
There are several obstacles to Discourse migration:
Considering these factors, I will keep an eye on this option in 2018.
TheBestPessimist Dec 30 11:47AM 2017
https://cloud.google.com/community/tutorials/setting-up-ruby-discourse This may be ~interesting~ useful.
Christoph Jan 1 1:02PM 2018
I have been running my own discourse forum since last year, helped set up another one and am at this very moment setting up another one. I'd be happy to help as much as I can should you decide to migrate to discourse. Apart from that, the go to place for support is at meta.discourse.org.
I don't know if the login module in Discourse can be customized to work with the one we already have.
It depends, of course, which one you have, but discourse supports SSO. It can be setup either as an SSO client or an SSO provider. It also supports various social logins via oauth2, including Github.
Need to import existing po[s]ts into Discourse database. I assume this should not be too difficult.
I have not done it myself, so I won't make judgments about difficulty. Again, it depends on what format you can export these existing ports to, but since this issue tracker looks rather basic (and not particularly voluminous, compared to some huge forums or mailinglists that migrated to discourse), I would also assume that it would not cause a lot of problems. For more on importing (especially the various existing import scripts) see https://meta.discourse.org/tags/import.
Migrating to Discourse means we need to maintain the hosting machine ourself which is a negative.
I am not an engineer and I find it not a big deal to maintain a VPS for a couple of Euros per month, though, admittedly, it does take time here and there. So in a business context, it might make sense to pay others to take care of that. The discourse team offers hosting plans starting from 100 USD per month (https://payments.discourse.org/pricing). discoursehosting.com starts at 20 USD per month (https://www.discoursehosting.com/pricing/). The discourse team also offers free hosting for community friendly open source projects of a certain size (https://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/).