Answered Getting Discuss working with Github

Hi Everyone:

I am starting up a forum using Discuss. I plan to develop this forum quite a lot, and develop some internal or external capability to help me build it out. However at this stage I have to figure out all the basics myself, so I know what is going on (as a non-tech person).

I installed discuss according to the instructions and changed all the values manually already, it seems to be working so far. However, then I realized it might not be in sync with the github version, and I want it to keep in sync. So, I checked the instructions for that, and connected my computer with my github account (I am Nuan8 over there). I do want to make a very customized theme finally, although it will take time.

By the way the website is www.rayxilawforums.com, just FYI. And the install is just at the default, ~.

The part that is holding me up is the part about building my own package, which is daunting to say the least. Can I avoid that and connect the standard install of Discuss that I already have to github? That would be the best solution for me, avoiding any of the messy coding stuff, which I don't have the background to handle. So I really hope this way would work, it would solve a lot of problems for me.

If I can't avoid it, well then I have a question about the build_config_php file. I asked my admin to put the info in, and he tried, but it still doesn't work right.

The problem seems to be in line 22. Here is the sample and what my admin put in there:



I can see now that he didn't understand, this process is supposed to make a package and send that package to the server and into the modx install.

Anyway, can someone tell me how to configure this? Then I can remove the discuss package I installed before and install this custom package (although again I wish I could just hook in the standard package to github and be done with this step).

Thanks in advance! I know the Discuss community isn't very big now, but after a lot of investigation and consideration we have decided to bet on the future of Discuss. This is a very long term plan and we think the extensibility and flexibility of Discuss outweighs the relative weakness of the community support that exists now.

Cheers!

The build.config.php file is only there to tell the PHP file that *builds* the package where the MODX root directory is. It doesn't figure into the installation or the transport file at all. You can hard-code the path rather than using dirname() if it's easier.

You might want to park your Discuss plans for the moment. I believe there is work proceeding on Discuss 2. The Core team are the guys to ask though.

You can take a look at the discuss2 repo here: https://github.com/modxcms/discuss2

Gah! Can I implement Discuss2 now or would I have to wait? (I seriously cannot wait)

As I understand it discuss2 is in alpha and is probably not suitable for production right now.

Ok then I will stick with the stable one and migrate over later. Not a fun plan but its presumably managable. Actually we did the same thing with Evo and Revo, we felt at that time that Revo was too unstable, and migrated last year to Revo.

Thanks to all for the input, including BobRay. I will be back on these boards soon enough with more questions heh. Really appreciate the feedback.