Host DocC on Github pages

SPI will be up soon, but we have to fix the dead links currently published on the master branch

SwiftPackageIndex/SwiftPackageIndex-Server#2120

Author: groue

Documentation/FullTextSearch.md

@@ -304,7 +304,7 @@ let pattern = FTS3Pattern(matchingAnyTokenIn: "")  // nil
 let pattern = FTS3Pattern(matchingAnyTokenIn: "*") // nil
 ```
 
-FTS3Pattern are regular [values](../README.md#values). You can use them as query [arguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments):
+FTS3Pattern are regular [values](../README.md#values). You can use them as query [arguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments):
 
 ```swift
 let documents = try Document.fetchAll(db,
@@ -587,7 +587,7 @@ let pattern = FTS5Pattern(matchingAnyTokenIn: "")  // nil
 let pattern = FTS5Pattern(matchingAnyTokenIn: "*") // nil
 ```
 
-FTS5Pattern are regular [values](../README.md#values). You can use them as query [arguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments):
+FTS5Pattern are regular [values](../README.md#values). You can use them as query [arguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments):
 
 ```swift
 let documents = try Document.fetchAll(db,

Documentation/Migrations.md

@@ -77,7 +77,7 @@ try dbQueue.read { db in
 }
 ```
 
-See the [DatabaseMigrator reference](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasemigrator) for more migrator methods.
+See the [DatabaseMigrator reference](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasemigrator) for more migrator methods.
 
 
 ## The `eraseDatabaseOnSchemaChange` Option

README.md

@@ -322,7 +322,7 @@ Documentation
 
 #### Reference
 
-- [GRDB Reference](https://swiftpackageindex.com/groue/grdb/documentation/grdb/)
+- [GRDB Reference](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/)
 
 #### Getting Started
 
@@ -616,7 +616,7 @@ do {
 
 > **Warning**: It is your responsibility to prevent sensitive information from leaking in unexpected locations, so you should not set the `publicStatementArguments` flag in release builds (think about GDPR and other privacy-related rules).
 
-See [Configuration](https://swiftpackageindex.com/groue/grdb/documentation/grdb/configuration) for more details and configuration options.
+See [Configuration](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/configuration) for more details and configuration options.
 
 
 SQLite API
@@ -673,7 +673,7 @@ try dbQueue.write { db in
 }
 ```
 
-The `?` and colon-prefixed keys like `:score` in the SQL query are the **statements arguments**. You pass arguments with arrays or dictionaries, as in the example above. See [Values](#values) for more information on supported arguments types (Bool, Int, String, Date, Swift enums, etc.), and [StatementArguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments) for a detailed documentation of SQLite arguments.
+The `?` and colon-prefixed keys like `:score` in the SQL query are the **statements arguments**. You pass arguments with arrays or dictionaries, as in the example above. See [Values](#values) for more information on supported arguments types (Bool, Int, String, Date, Swift enums, etc.), and [StatementArguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments) for a detailed documentation of SQLite arguments.
 
 You can also embed query arguments right into your SQL queries, with the `literal` argument label, as in the example below. See [SQL Interpolation] for more details.
 
@@ -931,7 +931,7 @@ try dbQueue.read { db in
     let dictionary = try Dictionary(uniqueKeysWithValues: cursor)
     ```
 
-- **Cursors adopt the [Cursor](https://swiftpackageindex.com/groue/grdb/documentation/grdb/cursor) protocol, which looks a lot like standard [lazy sequences](https://developer.apple.com/reference/swift/lazysequenceprotocol) of Swift.** As such, cursors come with many convenience methods: `compactMap`, `contains`, `dropFirst`, `dropLast`, `drop(while:)`, `enumerated`, `filter`, `first`, `flatMap`, `forEach`, `joined`, `joined(separator:)`, `max`, `max(by:)`, `min`, `min(by:)`, `map`, `prefix`, `prefix(while:)`, `reduce`, `reduce(into:)`, `suffix`:
+- **Cursors adopt the [Cursor](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/cursor) protocol, which looks a lot like standard [lazy sequences](https://developer.apple.com/reference/swift/lazysequenceprotocol) of Swift.** As such, cursors come with many convenience methods: `compactMap`, `contains`, `dropFirst`, `dropLast`, `drop(while:)`, `enumerated`, `filter`, `first`, `flatMap`, `forEach`, `joined`, `joined(separator:)`, `max`, `max(by:)`, `min`, `min(by:)`, `map`, `prefix`, `prefix(while:)`, `reduce`, `reduce(into:)`, `suffix`:
 
     ```swift
     // Prints all Github links
@@ -1010,7 +1010,7 @@ let rows = try Row.fetchAll(db,
     arguments: ["name": "Arthur"])
 ```
 
-See [Values](#values) for more information on supported arguments types (Bool, Int, String, Date, Swift enums, etc.), and [StatementArguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments) for a detailed documentation of SQLite arguments.
+See [Values](#values) for more information on supported arguments types (Bool, Int, String, Date, Swift enums, etc.), and [StatementArguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments) for a detailed documentation of SQLite arguments.
 
 Unlike row arrays that contain copies of the database rows, row cursors are close to the SQLite metal, and require a little care:
 
@@ -1318,7 +1318,7 @@ GRDB ships with built-in support for the following value types:
 
 - Generally speaking, all types that adopt the [DatabaseValueConvertible](#custom-value-types) protocol.
 
-Values can be used as [statement arguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments):
+Values can be used as [statement arguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments):
 
 ```swift
 let url: URL = ...
@@ -1791,7 +1791,7 @@ try dbQueue.inDatabase { db in  // or dbPool.writeWithoutTransaction
 }
 ```
 
-Transactions can't be left opened unless you set the [allowsUnsafeTransactions](https://swiftpackageindex.com/groue/grdb/documentation/grdb/configuration/allowsunsafetransactions) configuration flag:
+Transactions can't be left opened unless you set the [allowsUnsafeTransactions](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/configuration/allowsunsafetransactions) configuration flag:
 
 ```swift
 // fatal error: A transaction has been left opened at the end of a database access
@@ -1903,7 +1903,7 @@ try dbQueue.write { db in
 }
 ```
 
-The `?` and colon-prefixed keys like `:name` in the SQL query are the statement arguments. You set them with arrays or dictionaries (arguments are actually of type [StatementArguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments), which happens to adopt the ExpressibleByArrayLiteral and ExpressibleByDictionaryLiteral protocols).
+The `?` and colon-prefixed keys like `:name` in the SQL query are the statement arguments. You set them with arrays or dictionaries (arguments are actually of type [StatementArguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments), which happens to adopt the ExpressibleByArrayLiteral and ExpressibleByDictionaryLiteral protocols).
 
 ```swift
 insertStatement.arguments = ["name": "Arthur", "score": 1000]
@@ -1986,7 +1986,7 @@ See also `Database.execute(sql:)` in the [Executing Updates](#executing-updates)
 
 > **Note**: it is a programmer error to reuse a prepared statement that has failed: GRDB may crash if you do so.
 
-For more information about prepared statements, see the [Statement reference](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statement).
+For more information about prepared statements, see the [Statement reference](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statement).
 
 
 ### Prepared Statements Cache
@@ -2730,7 +2730,7 @@ try Place.fetchSet(db, sql: "SELECT ...", arguments:...)    // Set<Place>
 try Place.fetchOne(db, sql: "SELECT ...", arguments:...)    // Place?
 ```
 
-See [fetching methods](#fetching-methods) for information about the `fetchCursor`, `fetchAll`, `fetchSet` and `fetchOne` methods. See [StatementArguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments) for more information about the query arguments.
+See [fetching methods](#fetching-methods) for information about the `fetchCursor`, `fetchAll`, `fetchSet` and `fetchOne` methods. See [StatementArguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments) for more information about the query arguments.
 
 > **Note**: for performance reasons, the same row argument to `init(row:)` is reused during the iteration of a fetch query. If you want to keep the row for later use, make sure to store a copy: `self.row = row.copy()`.
 
@@ -3240,7 +3240,7 @@ Here is a list with all the available [persistence callbacks], listed in the sam
     - `aroundDelete`
     - `didDelete`
 
-For detailed information about each callback, check the [reference](https://swiftpackageindex.com/groue/grdb/documentation/grdb/mutablepersistablerecord/).
+For detailed information about each callback, check the [reference](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/mutablepersistablerecord/).
 
 In the `MutablePersistableRecord` protocol, `willInsert` and `didInsert` are mutating methods. In `PersistableRecord`, they are not mutating.
 
@@ -3433,7 +3433,7 @@ protocol EncodableRecord {
 }
 ```
 
-See [DatabaseColumnDecodingStrategy](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasecolumndecodingstrategy) and [DatabaseColumnEncodingStrategy](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasecolumnencodingstrategy/) to learn about all available strategies.
+See [DatabaseColumnDecodingStrategy](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasecolumndecodingstrategy) and [DatabaseColumnEncodingStrategy](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasecolumnencodingstrategy/) to learn about all available strategies.
 
 
 ### Date and UUID Coding Strategies
@@ -3455,7 +3455,7 @@ protocol EncodableRecord {
 }
 ```
 
-See [DatabaseDateDecodingStrategy](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasedatedecodingstrategy/), [DatabaseDateEncodingStrategy](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasedateencodingstrategy/), and [DatabaseUUIDEncodingStrategy](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databaseuuidencodingstrategy/) to learn about all available strategies.
+See [DatabaseDateDecodingStrategy](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasedatedecodingstrategy/), [DatabaseDateEncodingStrategy](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasedateencodingstrategy/), and [DatabaseUUIDEncodingStrategy](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databaseuuidencodingstrategy/) to learn about all available strategies.
 
 There is no customization of uuid decoding, because UUID can already decode all its encoded variants (16-bytes blobs and uuid strings, both uppercase and lowercase).
 
@@ -5015,7 +5015,7 @@ Player                          // SELECT * FROM player
 ```
 
 
-Raw SQL snippets are also accepted, with eventual [arguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments):
+Raw SQL snippets are also accepted, with eventual [arguments](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/statementarguments):
 
 ```swift
 // SELECT DATE(creationDate), COUNT(*) FROM player WHERE name = 'Arthur' GROUP BY date(creationDate)
@@ -7252,7 +7252,7 @@ DatabaseRegion helps [ValueObservation] and [DatabaseRegionObservation] track ch
 
 For example, if you observe the region of `Player.select(max(Column("score")))`, then you'll get be notified of all changes performed on the `score` column of the `player` table (updates, insertions and deletions), even if they do not modify the value of the maximum score. However, you will not get any notification for changes performed on other database tables, or updates to other columns of the player table.
 
-For more details, see the [reference](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databaseregion/).
+For more details, see the [reference](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databaseregion/).
 
 
 #### The DatabaseRegionConvertible Protocol
@@ -8616,7 +8616,7 @@ When this is the case, there are two possible explanations:
     try db.execute(sql: "UPDATE player SET name = ?", arguments: [name])
     ```
     
-For more information, see [Double-quoted String Literals Are Accepted](https://sqlite.org/quirks.html#dblquote), and [Configuration.acceptsDoubleQuotedStringLiterals](https://swiftpackageindex.com/groue/grdb/documentation/grdb/configuration/acceptsdoublequotedstringliterals).
+For more information, see [Double-quoted String Literals Are Accepted](https://sqlite.org/quirks.html#dblquote), and [Configuration.acceptsDoubleQuotedStringLiterals](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/configuration/acceptsdoublequotedstringliterals).
     
 
 
@@ -8765,7 +8765,7 @@ This chapter has [moved](Documentation/Concurrency.md#database-snapshots).
 
 #### DatabaseWriter and DatabaseReader Protocols
 
-This chapter was removed. See the references of [DatabaseReader](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasereader) and [DatabaseWriter](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasewriter).
+This chapter was removed. See the references of [DatabaseReader](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasereader) and [DatabaseWriter](http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/databasewriter).
 
 #### Asynchronous APIs
 
@@ -8819,7 +8819,7 @@ This chapter was renamed to [Embedding SQL in Query Interface Requests].
 [Sharing a Database]: Documentation/SharingADatabase.md
 [FAQ]: #faq
 [Database Observation]: #database-changes-observation
-[SQLRequest]: https://swiftpackageindex.com/groue/grdb/documentation/grdb/sqlrequest
+[SQLRequest]: http://groue.github.io/GRDB.swift/docs/6.3/documentation/grdb/sqlrequest
 [SQL literal]: Documentation/SQLInterpolation.md#sql-literal
 [Identifiable]: https://developer.apple.com/documentation/swift/identifiable
 [Query Interface Organization]: Documentation/QueryInterfaceOrganization.md