4

Just wanted to ask if this was an 'acceptable' use of the django sites framework and heroku - and if there would be any trouble running the two sites:

Main differences between sites will be templates, and some objects only published to one or other (or both) sites - notably users should be able to use both sites using their single account.

  • I have my one codebase. Any change in my settings.py file is dealt with by using heroku config variables.

  • I set up database that can be shared (either on an EC2 or using Heroku dedicated dbs)

  • I git push my code to two different Heroku Apps

Hey presto - one codebase, two running instances of Django, two separate sites.

Any issues with that?

Ryan
  • 3
  • 2
Guy Bowden
  • 4,997
  • 5
  • 38
  • 58
  • I don't have an answer for you, but I have the same question or desires. Did you ever get this working? Could you post your answer here? Thanks. – David S May 04 '12 at 14:22

1 Answers1

0

I went into great depth to answer this question in another thread, you can see my answer here: Multiple Django sites with shared codebase and DB

The short answer is NO, don't use the sites framework, use git branches.

Community
  • 1
  • 1
rdegges
  • 32,786
  • 20
  • 85
  • 109