Satchmo Multishop Documentation?

131 views
Skip to first unread message

Alec Taylor

unread,
Feb 13, 2012, 7:15:00 AM2/13/12
to satchm...@googlegroups.com
I am looking for documentation on Satchmo multishop.

Basically I am creating a multi-tenant (decoupled admin interface for
each client) solution.

So each shop has its own products, set by separate shop admins, with
separate PayPal accounts and whatnot.

Authentication will be centralised with Pinax.

How do I use Satchmo multishop, and does it support proper per shop
admin interfaces?

Thanks for all information,

Alec Taylor

hynekcer

unread,
Feb 13, 2012, 5:35:52 PM2/13/12
to Satchmo users
A problem is with expected "separate shop admins".
Look at the concept of sites and permissions in Django: The user has
the same permissions for all objects of the same model in the project.

You can read about Multishop extension in several discussions. The
most useful are posts written by author of the extension - Bruce
Kroeze - also what is the benefit of mutishop extension.
http://groups.google.com/group/satchmo-users/browse_thread/thread/845353be43e7a5e3
http://groups.google.com/group/satchmo-users/browse_thread/thread/7c1c8bc1e488c17d
http://groups.google.com/group/satchmo-users/browse_thread/thread/e3404a1482d9f2d2
http://groups.google.com/group/satchmo-users/browse_thread/thread/be20be4584ccbd17

I have read discussion about it last time in November that it was
successful used by some user.

Hynek

Tomas Neme

unread,
Feb 13, 2012, 6:38:59 PM2/13/12
to satchm...@googlegroups.com

I would *seriously* consider why do i actually need these shop/sites to share the same project, instead of setting up different virtualhosts no your server, and give each it's own database schema

-----Mensaje original-----
De: hynekcer
Enviados: 13/02/2012 19:35:52
Asunto: Re: Satchmo Multishop Documentation?

Hynek

--
You received this message because you are subscribed to the Google Groups "Satchmo users" group.
To post to this group, send email to satchm...@googlegroups.com.
To unsubscribe from this group, send email to satchmo-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.


Alec Taylor

unread,
Feb 13, 2012, 9:47:07 PM2/13/12
to satchm...@googlegroups.com, lacry...@gmail.com
Thanks Hynek, I will go through those threads later today.

Tomas: Because I want a centralised directory of shops, a sudo admin of all shops (to be used by me), centralised authentication and centralised receipts.

hynekcer

unread,
Feb 14, 2012, 4:08:20 PM2/14/12
to Satchmo users
What is Satchmo multishop extension:

Imagine that you want create more eshops for the same owner or a
family (you need no security barriers). You want use the same enabled
modules, the same database, only different templates and different
SITE_ID. You can do this all in the same directory with multiple added
configuration files settings_some_id.py, multiple sockets and multiple
independent server processes or processes pools.

Multishop extension only saves the memory for you compared to the
previous solution, in order you can serve them all by one process or
one process pool. It is nothing better. The memory is not probably the
most important for you.
_

Excuse my inaccuracy in the previous post. Django 1.2 added some hook
for object level permissions, but it requires an external backend for
implementation of fine-grained permissions and it is not supported by
Satchmo.
https://docs.djangoproject.com/en/dev/releases/1.2/#object-level-permissions

Think about what is easier:
- implement some advanced permissions to Satchmo?
I am sure you need to modify Satchmo)
- write a database router to share user models of django.contrib.auth?
https://docs.djangoproject.com/en/1.3/topics/db/multi-db/#automatic-database-routing
- write an application in Django which has access to all databases and
should do common tasks?

I think the third is the easiest or a combination of them because:
Who should / can safely delete or modify users if owners of stores are
competitors? (answer: nobody)

-- Hynek

On 14 ún, 00:38, "Tomas Neme" <lacrymol...@gmail.com> wrote:
> I would *seriously* consider why do i actually need these shop/sites to share the same project, instead of setting up different virtualhosts no your server, and give each it's own database schema
>
> -----Mensaje original-----
> De: hynekcer
> Enviados:  13/02/2012 19:35:52
> Asunto:  Re: Satchmo Multishop Documentation?
>
> A problem is with expected "separate shop admins".
> Look at the concept of sites and permissions in Django: The user has
> the same permissions for all objects of the same model in the project.
>
> You can read about Multishop extension in several discussions. The
> most useful are posts written by author of the extension - Bruce
> Kroeze - also what is the benefit of mutishop extension.http://groups.google.com/group/satchmo-users/browse_thread/thread/845...http://groups.google.com/group/satchmo-users/browse_thread/thread/7c1...http://groups.google.com/group/satchmo-users/browse_thread/thread/e34...http://groups.google.com/group/satchmo-users/browse_thread/thread/be2...

Alec Taylor

unread,
Feb 14, 2012, 8:43:28 PM2/14/12
to satchm...@googlegroups.com
Thanks Hynek.

Given the information you've given me (and what I've been thinking
over), it would be best to:

- Have `n` separate satchmo installs on one domain
- Link django.contrib.auth between them, thus centralising auth
- Centralise receipts (<website>/receipts/<shop-id>/<uid>)
- Create a simplified per shop config page (without any user db CRUD)
- Generate a model listing all shops on the server (needed also for searching)

At some point also I would like to link Pinax in, storing links to
each users' receipts into their profile.

What (if any) potential problems can you foresee from this setup?

Reply all
Reply to author
Forward
0 new messages