Hello, when I launch ./launcher bootstrap app I have this error:
Cannot connect to the Docker daemon. Is 'docker -d' running on this host? Cannot connect to the docker daemon - verify it is running and you have access
How I can fix this prblem please?
If y launch docker -d command, I have:
2014/11/29 14:49:33 docker daemon: 1.3.2 39fa2fa; execdriver: native; graphdriver: [2016daea] +job serveapi(unix:///var/run/docker.sock) [info] Listening for HTTP on unix (/var/run/docker.sock) [2016daea] +job init_networkdriver() [2016daea] -job init_networkdriver() = OK (0) 2014/11/29 14:49:33 WARNING: Your kernel does not support cgroup swap limit. 2014/11/29 14:49:33 Error loading docker apparmor profile: fork/exec /sbin/apparmor_parser: no such file or directory ()
Currently we have a MySQL database (server) containing the user names and passwords encrypted in whirlpool. Is there a possibility to integrate with Discourse? So that users can directly log in and if necessary further data deposits.
I would like to have the ability to add the custom user fields on the users profile to show up on the usercard if filled out.
Example. We use discourse as a gaming community. I would like to have users gamer tags (Xbox live, Steam, etc..) to show up on the card if they filled them out in their profile.
So my Discourse instance went from this (slightly old screenshot), which matched my regular site with a fixed-width design and the darker background color on the side...
To this, which looks kinda silly, and doesn't match the main site anymore.
I'm sure I can fix the logo to center properly in the display, but the white background on the topic list that extends to the side of the page is just a big difference.
Is it even possible to make it look the way it was? I don't need the width to be set to a specific pixel count, I just prefer having borders on the side.
Very tiny little UX glitch here, but I just noticed that the "Customize" tab loses its red highlight styling when a navigation item other than "Colors" is selected:
Integrating with Discourse we want to be able to provide our own profile page so the user only has one across our parts of the site and Discourse.
Ideally we would provide our own and pull in the Discourse stuff to render our own UI for the info shown here - merging our profile data with that of discourse.
Is this possible? To tell discourse that the users profile page is at a different URL?
I've just updated to discourse 1.2.0.beta3, and this problem is still here (I first noticed it a while back, not sure when)
I'm on my user's invited page, looking at the people I've invited to our forum.
The full list is 200 people (which I think is too short) but the 121st person in the list is the same as the 161st person, and that batch from 121 to 160 is the same group as from 161 to 200.
This is probably a unique case, but I'd like to be able to sign into one discourse forum instance with another discourse forum, probably with SSO. Is that possible? Thanks
Hi, everyone! While trying to diagnose why one of my pages with a Discourse Embed script wasn't working, I noticed that my error logs have many MANY entries being generated every second:
I wasn't able to find additional information from the logs that helps me go further, but I was hoping this might help one of you to point me in the right direction
I've been wanting to learn more about video editing, so for my first iMovie project (no budget for Final Cut Pro yet I'm afraid) I decided to make a video mimicking the format of the WordPress release video, hopefully with voiceover next time.
Please note that this is not intended for general consumption. Since it was a learning project I didn't spend time on polishing. Should however a similar video be desirable for the v1.2 release, I would be happy to spend more time making a solid showcase video.
Comments on pacing, timings, use of effects, transitions etc. are very welcome. And what did you think about the tune?
p.s. If some well-spoken smooth talker would like to volunteer for voice-overs, let me know. I tried myself, but my voice and my Norwegian dialect doesn't lend itself well to this sort of thing.
I help manage a Listserv group with 2,000+ subscribers and close to 1,000 posts per month. Posts are often relatively long (maybe averaging 3,000 char), and sometimes with attachments. Can anyone give me a rough estimate of resources needed to support this scale with good performance? I have a test site working on DigitalOcean, and need to consider whether we can afford a move from Listserv (which we are getting for free) to a hosted Discource forum.
Some mods on our forum have asked us about setting up a category for adults-only conversation. The design goals:
1) The category and thread titles are visible to all users (including logged out users, Google, etc.) 2) When attempting to view the thread posts, users should be required to sign in and check a box that confirms that they're over a certain age (e.g. 18 years) 3) Logged in users who have opted-in to adult-only conversation can view and participate in the category normally.
Is this possible today? (No, right?) Is the Discourse team working on anything like this? How close can we get to our goals just by using role-based security?
I have a parent's school forum where users are organized into groups (school classes and sections) and mapped to categories, all done using bulk invites.
Sometimes an existing user could be invited a second time, in a different group. What happens to the groups he belongs to?
For example, a parent has a son in class 4B, and a daughter in class 1A. The parent is enters the forum with the son's class 4B and belongs to group 4B. Later, the daughter's class wants to enter the forum and a bulk invite is prepared for class 1A. The desired behavior is adding the second group membership, or an error message fallback.
I did not test it yet, but could find time to simulate this case. Does anybody have experience with this situation?
This happens everywhere, but it's a bit more obvious on http://discuss.howtogeek.com/ because you can see the header width change...
It seems like the class "docked" is supposed to be appended to the body tag when the header is in its fixed position on scroll... but it's not actually working and the docked class is always appended unless I scroll up to a negative scroll position (doing this in Chrome on OSX).
There are many discussions on http://meta.discourse.org about the API and the lack of documentation. Now that Discourse is now past version 1.0, I think it would beneficial to many people if there was some actual documentation. This is my attempt at providing that documentation.
Developing software is not making a perfect thing from the beginning, but fixing an imperfect thing little by little to make it better. -- Matz
This is the very first draft of the API Documentation and should be considered v0.0.1. Most likely the format and the content will change as progress is made. But the most important thing is that we have something to start with to improve upon.
This document should not be considered complete. There is still a lot more to add and I'll do my best to keep it updated.
Current Version
Currently the API is not versioned (v1, v2, etc.). I'm assuming this will change at some point in the future, but could be a while (especially if I'm the one who ends up writing the code ).
Consuming the API
You can consume the API using cURL commands, but I recommend using the discourse_api gem so that you can use Ruby.
Authentication
Some endpoints do not require any authentication, pretty much anything else will require you to be authenticated.
To become authenticated you will need to create an API Key from the admin panel.
Once you have your API Key you can pass it in as a url parameter like this:
The notification emails sent from discourse have a helpful footer with links to respond or unsubscribe. I've had some feedback that this is too subtle and that it would help to have it be in a more active color that indicates it is a link, preferably blue.
Now that we're in December, I'm planning on shifting gears and working on extensibility for our 1.2 release of Discourse.
Extensibility is unfortunately one of those projects that can go on forever. I feel like no matter how much time I set aside to work on it, it will easily fill up that block. Instead, I'm going to focus on a few tasks that I feel are achievable by the end of the year.
I am going to approach this by working with two plugins that we feel are important, Tagger and Akismet, and making sure they integrate very nicely into Discourse. I will identify extension points that they need and try and make them as simple as possible.
I am going to be reiterating on them, sanding down any rough edges in Discourse in order to support development of this kind of thing.
Along the way, I have some secondary goals I'd like to achieve if time permits:
Allow plugin development without constantly deleting the tmp directory
Add a few webhooks to Discourse for integration with Github or Slack type services.
Support ES6 modules in the server side rendering pipeline
Convert the rest of Discourse to ES6 modules (we've done most of the hard work already on this)
Is there anything you'd like to see in extensibility? Any particular pain points or issues you'd like to see resolved?
).
