Re: NAS using Django

[reduxionist]

On Wednesday, March 9, 2016 at 7:15:17 PM UTC+7, Vayuj Rajan wrote:
>
> Hi,
> I have a query whether we can implement NAS (network attached storage) 
> functionality using Django framework?
>

FWIW FreeNAS  uses Django for its web admin (at 
least it did last time I installed it).

Best wishes,
Jonathan 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/25ec850a-d259-4a06-8579-6addff9de2a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: sqlalchemy with django

[reduxionist]

On Saturday, October 10, 2015 at 6:11:55 PM UTC+7, suyog wrote:
>
> can we use sqlalchemy with django?
>

Yes, try one of these depending on your use case:

https://github.com/Deepwalker/aldjemy
https://github.com/johnpaulett/django-sabridge

If they don't suit your needs & you're willing to be a little more 
adventurous:

https://github.com/grampajoe/tincture
https://github.com/devhub/baph
https://github.com/paylogic/forms2

Or DIY:

http://lethain.com/replacing-django-s-orm-with-sqlalchemy/

Good luck!

note:we don't need admin interface
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cee38869-4af3-4b15-81dd-868542be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Supprimer un COMMIT sur git

[reduxionist]

On Wednesday, August 12, 2015 at 5:01:03 PM UTC+7, Bassirou Ndiaye wrote:
>
> Bonjour j'ai commité une une nouvelle application sur GIT avec django et 
> je veux l'annuler Comment faire?
>

Vous n'êtes pas sur la bonne liste, ici c'est du Django en anglais, ce 
n'est pas de git en français, mais s.v.p. voire: 

https://git-scm.com/book/fr/v2/Utilitaires-Git-Reset-d%C3%A9mystifi%C3%A9#Le-rôle-de-reset
 

pour l'utilisation de:

 git reset --hard

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c17747c5-3fc5-4d06-bae2-32963f517b61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best Practices for Migrations in Reusable Apps?

[reduxionist]

Wow, terrific and comprehensive answer (as usual) Carl, thanks! I'll adjust my 
approach accordingly, thanks very much!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/dcd22073-1382-496e-8b3d-37f4f94a76b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best Practices for Migrations in Reusable Apps?

[reduxionist]

I was afraid of that, glad I asked. Thanks for your input!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7d77a29f-7109-496e-b29e-cebd288f5573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What is the ideal web server to use with Django?

[reduxionist]

On Wednesday, May 13, 2015 at 5:06:47 AM UTC-4, termopro wrote:
>
>
> No. 
>>
>> Cheers 
>>
>> Tom 
>>
>
> OK 
> 
>  
> :) 
>

That's only evidence that a lot of people don't know how to 
"performance-tune" (a.k.a. configure) Apache.

The question you asked Tom was "Doesn't Apache create new process for each 
request [thus eating memory when serving large amounts of static files 
during traffic peaks]?", and the reason that Tom correctly answers "No" is 
that as far as "serving large amounts of static files" goes you should be 
using mpm-worker (multi-threaded Apache) which most definitely does not 
spawn a new process for each request.

The reason for those search results is that mpm-prefork does, however, 
spawn a process per request, but it is only needed for non-thread-safe 
environments (most notoriously mod_php) and you shouldn't have to use it as 
long as you've been a good coder and avoided global state in your Django 
app (e.g. keep request-specific shared-state thread-local).

I think the reason a lot of people seem to run mpm-prefork is just that 
it's the default multi-processing module for Apache on most (all?) *nix 
platforms and they don't know any better.

Hope that helps explain away that myth! :)

Best wishes,
Jonathan

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/425d7d29-e6e3-495f-9901-239570a96622%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Obtaining content from Git

[reduxionist]

Arg, Google Groups' mobile interface sucks for posting rather than reading. 
As I was trying to say:

On Tuesday, November 25, 2014 2:43:55 AM UTC+7, reduxionist wrote:
>
> >Hence I was thinking: how much trouble would it be to have Django 
> >reach into Git rather than its database and obtain data there to be 
> >filled into template slots? Ideally, there'd be the possibility of 
> >running a filter (e.g. reStructuredText) between Git and the 
> >template rendering. 
>
> >What I envision is a storage layer (with optional caching) that 
> >either fetches from the filesystem (with a Git checkout, using mtime 
> >for cache expiration), or directly from a local Git repo (using 
> >either commit or blob hash for cache expiration). 
>
> >Does anyone know of such a module? 

 
Yes:
https://bitbucket.org/bors_ltd/django-gitstorage
(before you fork to github anew, consider updating this existing, but out 
of date, github mirror: https://github.com/9h37/django-gitstorage)
 

> >Would it be hard to write? Where would one start? 
>

Here's a couple of example projects that do similar things.

A git-backed wiki: 
https://github.com/mgaitan/waliki

A mercurial based latex hosting site:
https://bitbucket.org/Svedrin/webtex
("This is a Django Project providing a WebTeX service. The way this works 
is totally ripped from BitBucket: Users have HG Repos, push their Documents 
into it, and can get a compiled version and other cool stuff over the net.")

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/13c2e5eb-0f34-41c8-a77d-6c8b799f1a96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Obtaining content from Git

[reduxionist]

>Hence I was thinking: how much trouble would it be to have Django 
>reach into Git rather than its database and obtain data there to be 
>filled into template slots? Ideally, there'd be the possibility of 
>running a filter (e.g. reStructuredText) between Git and the 
>template rendering. 

>What I envision is a storage layer (with optional caching) that 
>either fetches from the filesystem (with a Git checkout, using mtime 
>for cache expiration), or directly from a local Git repo (using 
>either commit or blob hash for cache expiration). 

>Does anyone know of such a module? 

Yes:

>Would it be hard to write? Where would one start? 

For examples of projects that do similar things:

A git-backed wiki:

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7de0a097-ac9b-4231-86c0-e242c36a88cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Actively developed/supported piston fork?

[reduxionist]

On Thursday, October 30, 2014 4:34:32 PM UTC+7, sams...@gmail.com wrote:
>
> I've inherited an app that was written for Django 1.4, and updated it to 
> Django 1.7.
> ...
> Are any being actively used/fixed/supported?  Which one should I try?
>

While Russell Keith-Magee is definitely correct when he says "the bulk of 
the energy around REST tools in the Django community has moved to Django 
REST Framework," given that you have inherited legacy code, the good news 
is that there are indeed active forks of 
Piston, thanks to how widely used it was before the advent of DRF 
fore-runner TastyPie. The most recently active fork I know of is: 
https://github.com/matllubos/django-piston, which is currently actively 
maintained. If that doesn't work for you for any reason, let me know and 
I'll dig up my other, next-most-recently-active, Piston forks…

Best wishes,
Jonathan Barratt

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3ef0628f-fe4e-4186-ad74-b6906043f24e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.