> > How would the communication look with a database involved? What does a > database provide to this picture?
I think you would be better off separating between Pyblish and Django/Flask where Pyblish don't know about Django and Django don't know about Pyblish. instead they both communicate to the database like this: Pyblish ---> Database <--- Django/Flask what type of communication you need from between Pyblish and Django directly? On Sunday, 28 September 2014 22:47:00 UTC-7, Marcus Ottosson wrote: > > Thanks Cesar and Asi, it’s getting more clear to me what they both are > used for. > > About sqlAlchemy, or any database such as Firebase like I had considered > initially. Ideally, there’d be as few players involved as possible, and it > sounds like just using either Flask or Django would be enough to handle > this task. > > Here’s how I’m imagining the communication between the two. > > 1. Pyblish sends an HTTP request (RESTful or whatever) > 2. Django/Flask receives it > 3. Django/Flask generates HTML for it > 4. User browses to Django/Flask address, e.g. > http://192.168.0.100/pyblish > 5. User’s browser polls from address every second, so as to not need > push notifications > > The request would contain something like: > > { > "name": "publish", > "source": "\\projects\spiderman\asset\my_asset.mb", > "ip": "192.168.0.20", > "time": "2014-09-29 6:44:12"} > > From which either Django or Flask could browse to the directory and fetch > whatever data is related to the source and gather username and host-name > from the ip. > > How would the communication look with a database involved? What does a > database provide to this picture? > > Best, > Marcus > > > On 29 September 2014 06:01, Asi Sudai <[email protected] <javascript:>> > wrote: > >> Like Justin said, Django gives you more of a framework, which you may or >> may not need. >> but what's nice, both are using Jinja template engine, so moving from one >> to the other can be easy for little site. >> >> We're using Django and sqlAlchemy as the ORM ( it's part of the pipeline >> anyways ) >> >> There's a nice book called two scoops of django ( for 1.6 but easy to get >> working for 1.7 ) >> I'm not on their marketing team ;) but it's a good book... >> >> the authors made a great start_project template on github, >> I think iit's a good base to start a django project running: >> https://github.com/twoscoops/django-twoscoops-project >> >> hope that helps :) >> >> >> On Saturday, 20 September 2014 19:01:54 UTC-7, Cesar Saez wrote: >>> >>> I'm no expert, but Flask is a great alternative to Django (less >>> overhead), there are plugins for everything you could possibly need and the >>> template engine (Jinja2) is even better than Django's one. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/ba80ff04-40b3-4f54-975a-94a8dc4ec01c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/python_inside_maya/ba80ff04-40b3-4f54-975a-94a8dc4ec01c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > *Marcus Ottosson* > [email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/54f5f123-e963-49e2-9404-f798e216bf95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
