Django / Postgresql project + multiple databases architecture advice

I've got a pet Django / Postgresql project with multiple apps.

• It's not yet deployed.
• It's industry specific.
• It's target audience is worldwide.
• It's likely to have translated versions for certain countries later.
• It's not expected that its traffic will ever match that of the most popular websites.
• It's, however, expected that traffic may grow to millions of requests per day.
• It's expected that DB reads will prevail but writes will still be often.
• It's primary content will be text and files (usually up to 1 megabyte), no video or audio.

Should I now bother about scaling, multiple databases, and the like? I guess the answer is no but still not sure.

The following options are considered (but not limited to).

• Don't bother now. Add more resources later if needed. Even with millions of requests per day one DB would be enough.
• Don't bother now. Add replicas later if needed.
• Don't bother now. Partition by tables or rows later if needed.
• Partition now by grouping apps into separate databases on the same node. If later traffic happens to be high, put the databases on separate nodes.

So what would you advice.