upstream/kallithea Files · rhodecode/lib/dbmigrate/migrate/versioning/templates/repository/pylons/migrate.cfg

pull request: use unionrepo instead of outgoing...

pull request: use unionrepo instead of outgoing This makes it possible to look the 'moving target' symbols up in the right repo. Using a revset with the right revisions also removes the need for pruning changesets that are outside the requested range. It will also not be confused by changesets that for some reason has been pulled to the repo but haven't been merged yet. They are going to be 'merged' by the 'pull' request and should thus be a part of what is reviewed.

marcink - - Load All Authors

File last commit:

r833:9753e090 beta


                r3303:ae5ac36c

beta

Download file

             migrate.cfg
        
                    20 lines
            
             | 1.0 KiB
            
                | text/x-ini
            
             |
                IniLexer
            
             / rhodecode / lib / dbmigrate / migrate / versioning / templates / repository / pylons / migrate.cfg
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      [db_settings]

      # Used to identify which repository this database is versioned under.

      # You can use the name of your project.

      repository_id={{ locals().pop('repository_id') }}

      # The name of the database table used to track the schema version.

      # This name shouldn't already be used by your project.

      # If this is changed once a database is under version control, you'll need to 

      # change the table name in each database too. 

      version_table={{ locals().pop('version_table') }}

      # When committing a change script, Migrate will attempt to generate the 

      # sql for all supported databases; normally, if one of them fails - probably

      # because you don't have that database installed - it is ignored and the 

      # commit continues, perhaps ending successfully. 

      # Databases in this list MUST compile successfully during a commit, or the 

      # entire commit will fail. List the databases your application will actually 

      # be using to ensure your updates to that database work properly.

      # This must be a list; example: ['postgres','sqlite']

      required_dbs={{ locals().pop('required_dbs') }}

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				[db_settings]
				# Used to identify which repository this database is versioned under.
				# You can use the name of your project.
				repository_id={{ locals().pop('repository_id') }}

				# The name of the database table used to track the schema version.
				# This name shouldn't already be used by your project.
				# If this is changed once a database is under version control, you'll need to
				# change the table name in each database too.
				version_table={{ locals().pop('version_table') }}

				# When committing a change script, Migrate will attempt to generate the
				# sql for all supported databases; normally, if one of them fails - probably
				# because you don't have that database installed - it is ignored and the
				# commit continues, perhaps ending successfully.
				# Databases in this list MUST compile successfully during a commit, or the
				# entire commit will fail. List the databases your application will actually
				# be using to ensure your updates to that database work properly.
				# This must be a list; example: ['postgres','sqlite']
				required_dbs={{ locals().pop('required_dbs') }}