Shared Custom-Built Django Packages: Difference between revisions

From Littledamien Wiki
Jump to navigation Jump to search
No edit summary
Line 5: Line 5:
! package name
! package name
! description
! description
! status
! repo
! repo
|-
|-
| `addresses`
| `addresses`
| Management of basic address information, e.g. name, street, phone, city, state, zip, etc.
| Management of basic address information, e.g. name, street, phone, city, state, zip, etc.
| '''Deprecated.''' Use `contact_info` app instead.
|
|
|-
|-
| `contact_info`
| `contact_info`
| Management of individuals' contact information. How does this relate to the `addresses` package?
| Management of individuals' contact information. How does this relate to the `addresses` package?
| Under active development.
| [https://github.com/northrose/django-contact_info GitHub: /northrose/django-contact-info]
| [https://github.com/northrose/django-contact_info GitHub: /northrose/django-contact-info]
|-
|-
| `reverseadmin`
| `reverseadmin`
| Module that makes django admin handle OneToOneFields in a better way. Overrides Django's default behavior to display the relationship as an "inline" in the admin. It relies heavily on previous versions of Django. Not a good option in terms of maintenance.
| Module that makes django admin handle OneToOneFields in a better way. Overrides Django's default behavior to display the relationship as an "inline" in the admin. It relies heavily on previous versions of Django. Not a good option in terms of maintenance.
| '''Deprecated.''' Not compatible with current version of Django.
|
|
|}
|}

Revision as of 23:06, 30 November 2015

List of packages

package name description status repo
addresses Management of basic address information, e.g. name, street, phone, city, state, zip, etc. Deprecated. Use contact_info app instead.
contact_info Management of individuals' contact information. How does this relate to the addresses package? Under active development. GitHub: /northrose/django-contact-info
reverseadmin Module that makes django admin handle OneToOneFields in a better way. Overrides Django's default behavior to display the relationship as an "inline" in the admin. It relies heavily on previous versions of Django. Not a good option in terms of maintenance. Deprecated. Not compatible with current version of Django.

Installation

TK

Location

Windows

//damien-mg/d/develop/labs/shared/

Mac

~/develop/labs/shared/

Syncing codebase

PyCharm

  • Create a remote host
    • View > Tool Windows > Remote Host
    • Click the “…” button to create a new host.
      • Connection tab
        • Type: Local or mounted folder
        • Folder: /path/to/remote/project/
        • Web server root URL: remote url
      • Mappings tab
        • Make sure to enter at least a leading slash for Deployment path
      • Excluded Path tab
        • List of local and remote directories and files to ignore when syncing.
  • Sync to deployed
    • Right click on the root directory of a project > Deployment > Sync with deployed to [remote_host]
    • A dialog will appear that will traverse the project doing a diff on all the local and remote files.
    • Any files that should be excluded from the diff can be added through File > Settings > Build, Execution, Deployment > Deployment > select remote host > Excluded Paths tab

Git

TK: documentation of central repository on Github.

Without Git

Mac
$ cd ~/develop/labs/shared/
$ rsync -a /Volumes/d/develop/labs/shared/django-addresses/ django-addresses

TK: confirm what happens when a file in the target directory is newer than the file in the source directory above.

Windows
  • SyncToy
Retrieved from "https://wiki.dbarchowsky.com/index.php?title=Shared_Custom-Built_Django_Packages&oldid=1625"