> On July 23, 2013, 1:02 p.m., Aaron J. Seigo wrote:
> > why a clone of the discourse repo on github? was this to ensure that 
> > changes that happen in upstream discourse do not cause unexpected problems? 
> > or do you have actual changes in your github clone?
> > 
> > the installation procedure needs to be recorded in the README, but i 
> > suppose i can do that once this is in.
> > 
> > one this patch is in, there will need to modifications made to the asset 
> > info API in bodega-server to include a link to the discussion forum. that 
> > implies adding a new service block to the config.json for things like the 
> > url to the discourse server.
> 
> Giorgos Tsiapaliokas wrote:
>     >why a clone of the discourse repo on github? 
>     
>     The repository is in github because at the time that I created I wasn't 
> sure
>     if we will need it and then I just continued to use it. If github isn't 
> good
>     for us I can move it to projects.kde.org.
>     
>     >was this to ensure that changes that happen in upstream discourse do not 
> cause unexpected problems? 
>     >or do you have actual changes in your github clone?
>     
>     yes to both of them.
>     
>      The changes to my github clone are related to our encryption. Discourse 
> wasn't
>     using bcrypt and since we are syncing the password hashes there was no 
> other way in order to make
>     it possible for the users to log in.
> 
> Aaron J. Seigo wrote:
>     Ah, right, BCrypt. What does discourse use by default? I wonder if we 
> could convince them (e.g. by a patch) to make that configurable. Hummmmm...

By default they are using Pbkdf2.

Yes we could send them a patch, the config files are already 
there(discourse/config/database.yml.production-sample).


- Giorgos


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111654/#review36379
-----------------------------------------------------------


On July 23, 2013, 10:20 a.m., Giorgos Tsiapaliokas wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/111654/
> -----------------------------------------------------------
> 
> (Updated July 23, 2013, 10:20 a.m.)
> 
> 
> Review request for Bodega.
> 
> 
> Description
> -------
> 
> This patch keeps in sync the DBs of the bodega-server and discourse.
> 
> It syncs,
> 
> a. the user accounts*
> b. for each asset that has a partner with id > 1000 it create a new forum 
> which has a topic and a post
> 
> * there is a default account for the discourse
> username: forumadmin
> password: password
> 
> 
> Diffs
> -----
> 
>   server/bodegaDbHelper 273e34f 
>   sql/discourse.plsql PRE-CREATION 
> 
> Diff: http://git.reviewboard.kde.org/r/111654/diff/
> 
> 
> Testing
> -------
> 
> How to test it,
> 
> * git clone https://github.com/terietor/discourse.git
> * cd discourse
> * git checkout bodega
> * https://github.com/terietor/discourse/blob/master/docs/DEVELOPER-ADVANCED.md
> * cd bodega-server/server
> * make sql && make test-sql (your bodega user must be a superuser in order to 
> enable the dblink extention)
> * then go back to discourse and do `bundle exec rails s`
> * go to localhost:3000
> 
> 
> Thanks,
> 
> Giorgos Tsiapaliokas
> 
>

_______________________________________________
Active mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/active

Reply via email to