Using byteflow in an existing project

[Ramashish Baranwal]

Hi,

I am looking for a blog application for my django project. Byteflow
seems to be a great choice, however it is a complete project of its
own. I will try to add it as an application in my existing project,
but before I start I would like to know whether its a recommended way
to do it? I saw one thread where it was mentioned that it is a
complete project, but nothing was said on how hard/easy it will be to
import it in a project.

Looking for any inputs/suggestions in this regard :)

Thanks,
Ram

[daniellabeau]

Ram:

I'm no Django expert - but I've been using Byteflow for a while now.
If you already have a functioning Django project, an option might be
to cherry-pick desired applications from the Byteflow project (blog,
auth, tagging, discussion, etc..) and import them into your project
individually. You could "reassemble" the blog in this fashion. Just a
thought - I have a feeling that try to port the entire thing as a
single "application" might be overly complicated.

Of course, anything that is Byteflow specific you would want to credit
to the Byteflow engine!

-dan

On Mar 21, 1:33 pm, Ramashish Baranwal <ramashish.li...@gmail.com>
wrote:

[Alexander Solovyov]

There is no any recommended way, except if your project is still new and
blog is an essential part of it, you could just base on byteflow and evolve it
the way you need.

Another possibility (as Daniel already mentioned) is cherry-picking desired
functionality from byteflow to your project, although this will take more time.

And third possibility I see is just using this two projects together,
any webserver
(apache, nginx, lighttpd) allows you to bind them to different urls
(or subdomains).
There is no need to think about single sign on, while you're using Django's
sessions, but you need to be aware that Byteflow creates a user for every
commenter - you may want to change that (or not) depending on your needs.

Good luck! ;-) Ask more questions if you have them.

--
Alexander

[Ramashish Baranwal]

>
> There is no any recommended way, except if your project is still new and
> blog is an essential part of it, you could just base on byteflow and evolve it
> the way you need.
>
> Another possibility (as Daniel already mentioned) is cherry-picking desired
> functionality from byteflow to your project, although this will take more time.
>
> And third possibility I see is just using this two projects together,
> any webserver
> (apache, nginx, lighttpd) allows you to bind them to different urls
> (or subdomains).
> There is no need to think about single sign on, while you're using Django's
> sessions, but you need to be aware that Byteflow creates a user for every
> commenter - you may want to change that (or not) depending on your needs.
>

Thanks for the replies Daniel and Alexander. Unfortunately my project
is not new. I will try both the approaches suggested and see how it
goes.

Ram