Jake Whitaker wrote:

I'm using Digital Ocean hosting, as recommended. I took some time today to attempt to install some plugins, and made a mess (because, well, that's what happens when you require people in a GUI-based market to run a shell for plugin installation).

At first there were some typos in the git clone commands added to the app.yml file when I ran the rebuild, and eventually I fixed those only to find I'd deleted a / in the SSH call. Fixed that, ran the rebuild again, and still nothing. I've confirmed that the container files at least still exist, and I cancelled mid-bootstrap during one of the attempts (which I fear might've broken everything, since I didn't realize that ctrl+z would DO THAT). Tried running the bootstrap on its own and got this error.

Image.

I'd grab the log if I knew how to copy/paste the damn thing. I attempted to install Tagger, the Checklist, and shared editing privileges, and apparently attempted to copy Tagger which you aren't supposed to do either. As an otherwise extremely satisfied user, I'm more than a bit miffed that I've spent four hours breaking my forum for lack of something as standard as ACP-based plugin installs.

Does it look like I'm screwed? My forum's giving an ERROR 102.

Posts: 3

Participants: 2

Read full topic

Matt wrote:

I have a Docker install of Discourse.
Is it better to try to set up a multisite version of Discourse or can I set up a new instance of Discourse on another Droplet in Digital Ocean?

What is the benefit of a multisite Discourse?

Thank you!

Posts: 2

Participants: 2

Read full topic

Andrew LeCody wrote:

I have a cronjob that automatically populates a table "whmcs_emails" with the e-mail address of active users from another system. The idea is that any discourse account with an e-mail that matches this list will be granted a badge.

Here is the SQL statement I'm using:

SELECT u.id user_id, current_timestamp granted_at
FROM users u, whmcs_emails w
WHERE u.email = w.addr AND
(:backfill OR u.id IN (:user_ids) )

This is the error I'm getting:

PG::Error: ERROR:  permission denied for relation whmcs_emails
: SELECT COUNT(*) count FROM (SELECT u.id user_id, current_timestamp granted_at
FROM users u, whmcs_emails w
WHERE u.email = w.addr AND
('t' OR u.id IN (NULL) )) q WHERE 't' = 't'

I don't have much experience with PostgreSQL, is there an easy fix for this issue?

Posts: 3

Participants: 2

Read full topic

Helmi wrote:

Hey all,

I'm still fairly new to Discourse - just played around with a test installation a while ago. My plan is to migrate 3 other Forums to discourse and run another new one. I'm thinking about doing that in one multisite installation. I have of course read Multisite configuration with docker but i still have questions left.

1. As far as i got it until now, everything that is configured, individualized and styled with Discourse is done in the database and in some configuration files. This is why a collective codebase for all sites in a multisite installation is no problem, right? All sites run on that single base of files with only a different database.

2. Name based hosting. The hostname entry in the multisite.yml file is doing the name based stuff so all sites are fine to run on the same IP? So if i only run Discourse on this VM it would be no problem to map port 80 to the docker container that holds the app and not install any nginx or anything else - or would this be useeful for any other reasons? Would vanish be an option in combination with discourse to have additional caching or is this useless?

3. As far as i have come in reading about plugins i saw that they are installed by adding their Repo-URLs to the config. This can be done separately for each site, right?

4. I have read about a backup option that is included in Discourse now but only offers S3 as a target. Is this still right? Does anyone know of other plugins that support other backup target locations (s/ftp, dropbox, whatever)?

5. Are there any experiences with migrating vBulletin and Vanilla forums? I'd have to migrate to of them and i think that would be my biggest deal in the end.

Sidenote: I'm going to run this all in a VM on my own bare metal machine so i'm quite free with adding RAM, CPU and disc space and i thought i'd start with 2GB of RAM - is this a good idea or should i already add more?

Thanks for helping!
Frank

Posts: 1

Participants: 1

Read full topic

Aagat wrote:

Hi,

I want to use custom S3 compatible service for user uploads and backup but currently no way to enter custom server in the control panel because you can only choose between AWS availability zones. Wouldn't it be better to just expose the API endpoints instead of just availability zones? It's allow the rest of us to store data closer to our audiences for cheaper.

Thankyou

Posts: 4

Participants: 3

Read full topic

Ali wrote:

Having all settings-changes added to the log is incredibly useful.

How about a button to roll-back certain changes to the old value to make rolling back even easier?

Posts: 2

Participants: 2

Read full topic

wrote:

Hello,

I'm a newbie and want to install Discourse for a small community.
How much is worth?
Thanks.

asfweret.jpg958x978 348 KB

Posts: 2

Participants: 2

Read full topic

Spero Koulouras wrote:

I am able to use the create topic API to create simple text messages and push them into my Discourse instance. If I want to create richer messages containing links, images or other HTML what are the restrictions? I have already found that including image URL's with imgur links causes the API to return a 400 (Bad Request) error. Are there other restrictions on HTML Tags that may also cause problems? Is the HTML whitelist applied on the server side of these API's? How much must I sanitize?

The use case here is creating new topics from a structured page on our web site, not from within the forum itself.

Posts: 5

Participants: 3

Read full topic

Stefan Tatschner wrote:

Hi,

I think I have discovered a bug according to the setting suppress uncategorized badge.

What I have done:

• Renamed Uncategorized to Notopic.
• Disabled suppress uncategorized badge as I want to see the badge.

What's the problem?

The Notopic badge is not shown on pinned topics. Other badges ares shown on pinned topics. The badge should be shown on pinned topics as well.

Discourse Version

1.2.0.beta1

Screenshots

Every Screenshot is made on the Latest page.

Notopic pinned no badge

Bildschirmfoto23.png1118x95 17.3 KB

Another pinned topic with badge

Bildschirmfoto24.png1118x126 25.6 KB

Notopic unpinned with badge

Bildschirmfoto25.png1118x50 10 KB

Posts: 3

Participants: 2

Read full topic

wrote:

Continuing the discussion from Making Non-English Category URL Understandable. Not like /c/13-category:

If you are using the default locale(en), it will not be a problem.

However, like me, not using Latin Alphabet (I am using ko), need more distinctive & easy to understand URLs for categories.

Please let us have a control of each categories' URLs like this:

catURLs.png998x825 102 KB

Posts: 1

Participants: 1

Read full topic

Buddy wrote:

Continuing the discussion from talk.commonmark.org,

I wanted to suggest that quotes could be handled without an extension to markdown syntax: a new route could be created for quote links, with a special onebox engine that renders that link identical to existing quote box headers with no padding below the onebox, such that the following:

http://talk.commonmark.org/quote/sam/168/5
>The number 1 issue with using CommonMark here is lack Discourse specific extensions.

would render exactly the same as a quote using the current bbcode syntax does. If the quote were expanded by clicking the chevron however, the full post would show, as it currently does, except it wouldn't clobber the markdown quote.

I understand that currently, links to posts with restricted visibility do not onebox. Those links, in quote format, could onebox to a quote header with no chevron. By the way, I have found a related problem with quoting restricted visibility posts: http://what.thedailywtf.com/t/pm-quote-test/4972

Posts: 3

Participants: 2

Read full topic

wrote:

Hi,

I decided to create my own community on Discourse, instead of phpbb, but today when i clicked on the "Try It" (http://try.discourse.org/) i got this:

uncorr.png1920x1048 218 KB

Posts: 4

Participants: 2

Read full topic

Tobias Eigen wrote:

I am in the process of migrating a handful of related mailing lists (google groups, actually) to private categories in a new Discourse instance. These are people (about 50) who all work for the same organization and are required as part of their job to be in these mailing lists. We don't care about the archives, just the users.

I've spent some time searching meta for info on this and seem to be either sent to the import scripts (which are about importing from forums including content and require programming) or to the invite system (which requires acceptance of invitation by the user).

Correct me if I'm wrong, but the invite system seems inappropriate because we just want to copy over the lists and have them working in discourse just as they were working on google groups before. We do not want to have to chase down everyone and make sure they click to accept the invitation before they start getting emails and are able to send emails.

If anyone has used the import scripts with success just to import say a CSV of users along the lines of the invite system, I'd really appreciate a HOWTO on the steps to getting it done.

Posts: 6

Participants: 4

Read full topic

Tobias Eigen wrote:

I am in the process of moving three google groups to a discourse instance, and would be grateful for advice.

These groups are all run by the same organization, but the users are not all overlapping. All are private, one contains people that may or may not care to be kept informed about the organization generally but need to be in this one private group, and one contains people who need to talk about things that nobody else should not be privy to. Later we plan to open up the forum to include more discussions by the staff, by our wider network and interested citizens who find us and sign up via the web.

Here are the groups I am setting up first:

• staff - all staff in the organization
• leadership - only subset of staff, rest of staff should not have access
• office - subset of staff plus people from other organizations who share office space

Before I move forward, I can see I need to resolve two issues:

1. The people sharing the office space should not be getting any other mail from the forum except from the office category.
2. The staff with admin and moderator access to the forum shouldn't be seeing the messages in the leadership category.

For #2, I am considering setting up an admin user account that is used to handle admin functions and that can work. But later when we open up registration I can see there will be problems in identifying spam users and doing regular moderator tasks.

For #1, the solution seems to be to completely lock down all categories and to only provide access to the office category. But again this won't work once we open up the forum to the public. Some sort of "mute all but x category" user setting seems to be required.

We do want to get staff to get fully immersed in discourse and buy into it before we move to the next stage, so at all costs want to avoid splintering off some groups to discourse while we keep other google groups running.

Posts: 6

Participants: 4

Read full topic

Clay Heaton wrote:

Using the latest Discourse...

1. Bookmark a post
2. Go to the "Bookmarks" page under your avatar picture
3. Click to remove the bookmark
4. Browse back to the post in question

You'll notice a few things...

1. The bookmark icon remains highlighted in spite of the fact that the bookmark was removed.
2. You cannot bookmark the post again. You can click and it looks bookmarked, but the post will not appear on the "Bookmarks" page under your profile again.

Posts: 4

Participants: 3

Read full topic

Silver Quettier wrote:

I saw a similar question for Apache and Nginx, but found nothing about Lighttpd.

I have a server hosting several services, and various DNS records redirecting to it. Each record is linked to a subdomain. Discourse is installed on Docker (as per the manual), and container / host port mapping is as follows:

$ docker ps
CONTAINER ID        IMAGE                          COMMAND                CREATED             STATUS              PORTS                                                                                                              7b115219788e        local_discourse/app:latest     "/sbin/runit"          11 weeks ago        Up 8 weeks          0.0.0.0:3022->22/tcp, 0.0.0.0:3080->80/tcp

Lighttpd has been configured on the host with mod_proxy to redirect all traffic aiming "discourse.mydomain.com" to port 3080:

server.modules = (
        "mod_access",
        "mod_alias",
        "mod_compress",
        "mod_redirect",
        "mod_rewrite",
        "mod_proxy",
)

server.document-root        = "/var/www"
server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
server.errorlog             = "/var/log/lighttpd/error.log"
server.pid-file             = "/var/run/lighttpd.pid"
server.username             = "www-data"
server.groupname            = "www-data"
server.port                 = 80


index-file.names            = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny             = ( "~", ".inc" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )

compress.cache-dir          = "/var/cache/lighttpd/compress/"
compress.filetype           = ( "application/javascript", "text/css", "text/html", "text/plain" )

# default listening port for IPv6 falls back to the IPv4 port
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell "/usr/share/lighttpd/include-conf-enabled.pl"

$HTTP["host"] =~ "discourse.mydomain.com" {
    proxy.debug = 1
    proxy.server  = ( "" => ( "discourse" => ( "host" => "127.0.0.1", "port" => 3080, "fix-redirects" => 1 )))
}

Sadly, this doesn't work. It shows a blank page. However, accessing it through port 3080 directly, and bypassing Lighttpd works fine.

Lighttpd logs shows activity when I try to reach Discourse through it:

2014-11-17 21:15:55: (mod_proxy.c.1144) proxy - start
2014-11-17 21:15:55: (mod_proxy.c.1185) proxy - ext found
2014-11-17 21:15:55: (mod_proxy.c.1319) proxy - found a host 127.0.0.1 3080
2014-11-17 21:15:55: (mod_proxy.c.398) connect delayed: 10
2014-11-17 21:15:55: (mod_proxy.c.1000) proxy: fdevent-out 1
2014-11-17 21:15:55: (mod_proxy.c.1029) proxy - connect - delayed success
2014-11-17 21:15:55: (mod_proxy.c.969) proxy: fdevent-in 4
2014-11-17 21:15:55: (mod_proxy.c.667) proxy - have to read: 521
2014-11-17 21:15:55: (mod_proxy.c.969) proxy: fdevent-in 4
2014-11-17 21:15:55: (mod_proxy.c.667) proxy - have to read: 0

Do anyone know the correct configuration?
What could I do to debug further?

I have asked StackExchange yesterday, but no ideas there.

Posts: 1

Participants: 1

Read full topic

Tristan Goguillot wrote:

Hello Discourse !

The Markdown implementation in Discourse does not require to add a space after a # to convert to header. The problem with this behavior is that you cannot easily use # in your text, which is now pretty popular (even just for fun, without real tag management like on FB).

Other implementation like GitHub or Zendesk make the difference between the two cases:
#discourse > #discourse
# discourse >

discourse

Should we bring this issue to markdown-js?

Posts: 4

Participants: 2

Read full topic

Ratty wrote:

Is anyone familiar with SkimLinks? Curious as to how much leg work would be to implement a solution like this:
http://skimlinks.com/forums-communities

Posts: 2

Participants: 2

Read full topic

Accalia++ wrote:

Markdown:

***\*twitch\****

Expected output:
*twitch*

Actual output:
3389dae361af79b04c9c8e7057f60cc6twitch3389dae361af79b04c9c8e7057f60cc6

Golfed example:

***\****

3389dae361af79b04c9c8e7057f60cc6

Edit: additional information:

this line ***\**** is incomplete

this line 3389dae361af79b04c9c8e7057f60cc6

Posts: 4

Participants: 3

Read full topic

Jonathas Spalding wrote:

Hello everyone!

If you don't want to mess with the firewall rules and security of your server, you can configure your Docker multiple container setup with just links and no exposed ports!

This way you can share your data container (postgres/redis) with other containers without exposing it to the internet.

---

How to:

1. Edit your data.yml file commenting all the expose section:

   #expose:
   # - "5432:5432"
   # - "6379:6379"
   # - "2221:22"

2. Edit your web_only.yml file uncommenting the links section:

   links:
   - link:
   name: data
   alias: data

   (remeber to use the name of your data container here)

3. The trick! Also on web_only.yml file, use your data container's name to connect to the database:

   DISCOURSE_DB_HOST: data
   DISCOURSE_REDIS_HOST: data

---

The Docker's Magic:

As explained on Docker Container Linking documentation, when you --link containers:

Docker adds a host entry for the source container to the /etc/hosts file

So now the containers can communicate locally! Also:

If you restart the source container, the linked containers /etc/hosts files will be automatically updated with the source container's new IP address, allowing linked communication to continue.

Posts: 2

Participants: 1

Read full topic