u/pc/rhodecode-enterprise-ce-fork-pc Files · rhodecode/lib/dbmigrate/migrate.cfg

shadow-repos: use safer way to destroy shadow repositories....

shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.

marcink - - Load All Authors

File last commit:

r1:854a839a default


                r2791:27d869d5

stable

Download file

             migrate.cfg
        
                    20 lines
            
             | 1017 B
            
                | text/x-ini
            
             |
                IniLexer
            
             / rhodecode / lib / dbmigrate / migrate.cfg
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      [db_settings]

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

      # You can use the name of your project.

      repository_id=rhodecode_db_migrations

      # 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=db_migrate_version

      # 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=['sqlite']

	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

marcink project: added all source files and assets	r1	[db_settings]
		# Used to identify which repository this database is versioned under.
		# You can use the name of your project.
		repository_id=rhodecode_db_migrations

		# 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=db_migrate_version

		# 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=['sqlite']