Changes between Initial Version and Version 2 of Ticket #26371


Ignore:
Timestamp:
Mar 17, 2016, 6:06:39 PM (9 years ago)
Author:
Becka R.
Comment:

(edited description in response to Claude's comment)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26371

    • Property Resolutionworksforme
    • Property Status newclosed
    • Property Component UncategorizedDocumentation
  • Ticket #26371 – Description

    initial v2  
    33I now have a solid understanding of the fundamentals, and have been struggling a lot to level up, and there are a lot of common use cases which are insufficiently documented. 
    44
    5 In a "beyond the basics" tutorial section, one chapter might include step by step instructions for moving over to Postgres using Psycopg2, and then using multiple settings files depending on the dev context, and understanding how to navigate this (honestly, I'm not even sure what questions to ask here, because I barely understand how it works).
     5In a "beyond the basics" tutorial section, one chapter might include step by step instructions for moving over to Postgres using Psycopg2, and then using multiple settings files depending on the dev context, and understanding how to navigate this (honestly, I'm not even sure what questions to ask here, because I barely understand how it works).
     6
     7ETA: correction. On some platforms, it is not possible to deploy with SQLite. Generally speaking, SQLite isn't the favored database for deployed applications.   
    68
    79 It's very, very easy to make mistakes here, and the documentation for the psycopg2 package itself is inaccurate, and the docs for Postgres are overwhelming.  The combination of Django and Postgres to the new dev feels very, very insurmountable without a pairing buddy.  Please add docs to add  support for this very standard and confusing process.
Back to Top