- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 262 for migrations (0.15 sec)
-
manifests/charts/gateway/README.md
```yaml networkGateway: network-1 ``` ### Migrating from other installation methods Installations from other installation methods (such as istioctl, Istio Operator, other helm charts, etc) can be migrated to use the new Helm charts following the guidance below. If you are able to, a clean installation is simpler. However, this often requires an external IP migration which can be challenging.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 02 19:38:07 UTC 2024 - 6.6K bytes - Viewed (0) -
docs/fr/docs/project-generation.md
* Modèles **SQLAlchemy** (indépendants des extensions Flask, afin qu'ils puissent être utilisés directement avec des *workers* Celery). * Modèle de démarrages basiques pour les utilisateurs (à modifier et supprimer au besoin). * Migrations **Alembic**. * **CORS** (partage des ressources entre origines multiples, ou *Cross Origin Resource Sharing*). * *Worker* **Celery** pouvant importer et utiliser les modèles et le code du reste du backend.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Fri Jul 02 14:18:06 UTC 2021 - 6.7K bytes - Viewed (0) -
docs/en/docs/how-to/async-sql-encode-databases.md
## Create the tables In this case, we are creating the tables in the same Python file, but in production, you would probably want to create them with Alembic, integrated with migrations, etc. Here, this section would run directly, right before starting your **FastAPI** application. * Create an `engine`. * Create all the tables from the `metadata` object. ```Python hl_lines="25-28"
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 5.3K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
And it will work and will be useful **during development**. But if your connection to the server is lost, the **running process** will probably die. And if the server is restarted (for example after updates, or migrations from the cloud provider) you probably **won't notice it**. And because of that, you won't even know that you have to restart the process manually. So, your API will just stay dead. 😱 ### Run Automatically on Startup
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu May 02 22:37:31 UTC 2024 - 18K bytes - Viewed (0) -
pkg/security/security.go
FileRootSystemCACert = "file-root:system" ) // TODO: For 1.8, make sure MeshConfig is updated with those settings, // they should be dynamic to allow migrations without restart. // Both are critical. var ( // Require3PToken disables the use of K8S 1P tokens. Note that 1P tokens can be used to request
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Jun 13 17:48:28 UTC 2024 - 19.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/migrating/migrating_from_groovy_to_kotlin_dsl.adoc
Two approaches to migrations stand out: * Migrating the existing syntax of your build to Kotlin, bit by bit, while retaining the structure — what we call a _mechanical migration_ * Restructuring your build logic towards Gradle best practices and switching to Kotlin DSL as part of that effort Both approaches are viable. A mechanical migration will be enough for simple builds.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 26.9K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/migrating/migrating_from_ant.adoc
+ The main downside is the extra work required to perform the migration, particularly if the existing build is complex and has many inter-project dependencies. However, these builds often benefit the most from a switch to idiomatic Gradle. In addition, Gradle provides many features that can ease the migration, such as the ability to <<ant#sec:using_ant_tasks,use core and custom Ant tasks>> directly from a Gradle build.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 23 22:37:03 UTC 2024 - 37.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/migrating/migrating_from_maven.adoc
This may make migrating between the two seem intimidating, but migrations can be surprisingly easy because Gradle follows many of the same conventions as Maven -- such as the <<java_plugin#sec:java_project_layout,standard project structure>> -- and its dependency management works in a similar way. Here we lay out a series of steps for you to follow that will help facilitate the migration of any Maven build to Gradle:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 23 22:37:03 UTC 2024 - 40.6K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
If in your use case there's no problem in running those previous steps **multiple times in parallel** (for example if you are not running database migrations, but just checking if the database is ready yet), then you could also just put them in each container right before starting the main process. ### Single Container
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat May 18 23:43:13 UTC 2024 - 34K bytes - Viewed (0) -
MIGRATION.md
## Migration From Other Enterprise Search Systems ### Google Search Appliance (GSA) / Google Mini Fess provides a [Google Search Appliance](https://enterprise.google.com/search/products/gsa.html) (GSA) compatible API. To enable this API, set `web.api.gsa=true` to system.properties. This will enable an enpoint at `<Fess Server Name>:8080/gsa`. When a search query is sent to `<Fess Server Name>:8080/gsa/?q=QUERY`, a GSA compatible response will be returned
Registered: Wed Jun 12 13:08:18 UTC 2024 - Last Modified: Tue Mar 05 06:12:02 UTC 2019 - 1.6K bytes - Viewed (0)