Deployment: Difference between revisions
No edit summary |
(→MongoDB setup: in 2.0, journaling is on and preallocates multigigabyte journal files) |
||
| Line 7: | Line 7: | ||
= MongoDB setup = |
= MongoDB setup = |
||
You should almost certainly [http://www.mongodb.org/display/DOCS/Journaling run MongoDB with Journaling on] if you have a new enough version of MongoDB. (If you don't, maybe you should get a newer version!) Without journaling there's some risk you could lose data that isn't yet written to disk if MongoDB is shut down incorrectly. |
You should almost certainly [http://www.mongodb.org/display/DOCS/Journaling run MongoDB with Journaling on] if you have a new enough version of MongoDB. (If you don't, maybe you should get a newer version!) Without journaling there's some risk you could lose data that isn't yet written to disk if MongoDB is shut down incorrectly. '''But see below.''' |
||
Also, keep in mind the following [http://www.snailinaturtleneck.com/blog/2010/08/19/if-it-quacks-like-a-rdbms/ assumptions MongoDB makes] about your deployment environment |
Also, keep in mind the following [http://www.snailinaturtleneck.com/blog/2010/08/19/if-it-quacks-like-a-rdbms/ assumptions MongoDB makes] about your deployment environment |
||
| Line 14: | Line 14: | ||
* little-endian |
* little-endian |
||
* more than one server |
* more than one server |
||
* speed is more important than reliability, and journaling is off by default |
* speed is more important than reliability, and journaling is off by default (apparently that’s not true anymore, at least in 2.0, [http://www.mongodb.org/display/DOCS/Journaling journaling is on and will preallocate ''gigabytes'' for the journal files], unless you [[Scaling Down|disable preallocation]].) |
||
= Running MediaGoblin's web server and Celery separately = |
= Running MediaGoblin's web server and Celery separately = |
||
Revision as of 09:28, 9 October 2011
This page could use a lot of work. For now, a few smaller deployment tips!
Use Virtualenv
Our Development quick start guide recommends using zc.buildout, but this system is somewhat problematic for actual deployments (if a buildout goes badly, buildout removes all your packaging setup and your scripts in bin/ and other things... yuck :\). Use Virtualenv instead. In the future, all our docs will bet set up to recommend using Virtualenv.
MongoDB setup
You should almost certainly run MongoDB with Journaling on if you have a new enough version of MongoDB. (If you don't, maybe you should get a newer version!) Without journaling there's some risk you could lose data that isn't yet written to disk if MongoDB is shut down incorrectly. But see below.
Also, keep in mind the following assumptions MongoDB makes about your deployment environment
- 64-bit machine
- little-endian
- more than one server
- speed is more important than reliability, and journaling is off by default (apparently that’s not true anymore, at least in 2.0, journaling is on and will preallocate gigabytes for the journal files, unless you disable preallocation.)
Running MediaGoblin's web server and Celery separately
./lazyserver.sh is all good and well for debugging, but probably not for deployments. Instead, you should probably run