@@ -76,14 +76,21 @@ To build this project you also need to have [GitLab Runner](https://docs.gitlab.
...
@@ -76,14 +76,21 @@ To build this project you also need to have [GitLab Runner](https://docs.gitlab.
You can use public runners available on `gitlab.com` or you can register your own:
You can use public runners available on `gitlab.com` or you can register your own:
```shell
```shell
cat> /tmp/test-config.template.toml <<EOF
[[runners]]
[runners.docker]
[[runners.docker.services]]
name = "postgres:latest"
EOF
gitlab-runner register \
gitlab-runner register \
--non-interactive\
--non-interactive\
--url"https://gitlab.com/"\
--url"https://gitlab.com/"\
--registration-token"PROJECT_REGISTRATION_TOKEN"\
--registration-token"PROJECT_REGISTRATION_TOKEN"\
--description"python-3.5"\
--description"python-3.5"\
--executor"docker"\
--executor"docker"\
--docker-image python:3.5\
--template-config /tmp/test-config.template.toml\
--docker-services postgres:latest
--docker-image python:3.5
```
```
With the command above, you create a runner that uses the [`python:3.5`](https://hub.docker.com/_/python) image and uses a [PostgreSQL](https://hub.docker.com/_/postgres) database.
With the command above, you create a runner that uses the [`python:3.5`](https://hub.docker.com/_/python) image and uses a [PostgreSQL](https://hub.docker.com/_/postgres) database.
@@ -64,7 +64,19 @@ You can do this through the [Heroku Dashboard](https://dashboard.heroku.com/).
...
@@ -64,7 +64,19 @@ You can do this through the [Heroku Dashboard](https://dashboard.heroku.com/).
First install [Docker Engine](https://docs.docker.com/installation/).
First install [Docker Engine](https://docs.docker.com/installation/).
To build this project you also need to have [GitLab Runner](https://docs.gitlab.com/runner/).
To build this project you also need to have [GitLab Runner](https://docs.gitlab.com/runner/).
You can use public runners available on `gitlab.com` or register your own:
You can use public runners available on `gitlab.com` or register your own. Start by
creating a template configuration file in order to pass complex configuration:
```shell
cat> /tmp/test-config.template.toml <<EOF
[[runners]]
[runners.docker]
[[runners.docker.services]]
name = "mysql:latest"
EOF
```
Finally, register the runner, passing the newly-created template configuration file:
```shell
```shell
gitlab-runner register \
gitlab-runner register \
...
@@ -73,8 +85,8 @@ gitlab-runner register \
...
@@ -73,8 +85,8 @@ gitlab-runner register \
--registration-token"PROJECT_REGISTRATION_TOKEN"\
--registration-token"PROJECT_REGISTRATION_TOKEN"\
--description"ruby:2.6"\
--description"ruby:2.6"\
--executor"docker"\
--executor"docker"\
--docker-image ruby:2.6\
--template-config /tmp/test-config.template.toml\
--docker-services latest
--docker-image ruby:2.6
```
```
With the command above, you create a Runner that uses the [`ruby:2.6`](https://hub.docker.com/_/ruby) image and uses a [PostgreSQL](https://hub.docker.com/_/postgres) database.
With the command above, you create a Runner that uses the [`ruby:2.6`](https://hub.docker.com/_/ruby) image and uses a [PostgreSQL](https://hub.docker.com/_/postgres) database.
Container Registry can use considerable amounts of disk space. To clear up
unused layers, the registry includes a [garbage collect command](../administration/packages/container_registry.md#container-registry-garbage-collection).
msgid "FeatureFlags|Enable features for specific users and specific environments by defining feature flag strategies. By default, features are available to all users in all environments."
msgid "FeatureFlags|Enable features for specific users and specific environments by defining feature flag strategies. By default, features are available to all users in all environments."
msgstr ""
msgstr ""
...
@@ -9139,9 +9133,6 @@ msgstr ""
...
@@ -9139,9 +9133,6 @@ msgstr ""
msgid "FeatureFlags|Feature Flag"
msgid "FeatureFlags|Feature Flag"
msgstr ""
msgstr ""
msgid "FeatureFlags|Feature Flag User List Details"
msgstr ""
msgid "FeatureFlags|Feature Flag behavior is built up by creating a set of rules to define the status of target environments. A default wildcard rule %{codeStart}*%{codeEnd} for %{boldStart}All Environments%{boldEnd} is set, and you are able to add as many rules as you need by choosing environment specs below. You can toggle the behavior for each of your rules to set them %{boldStart}Active%{boldEnd} or %{boldStart}Inactive%{boldEnd}."
msgid "FeatureFlags|Feature Flag behavior is built up by creating a set of rules to define the status of target environments. A default wildcard rule %{codeStart}*%{codeEnd} for %{boldStart}All Environments%{boldEnd} is set, and you are able to add as many rules as you need by choosing environment specs below. You can toggle the behavior for each of your rules to set them %{boldStart}Active%{boldEnd} or %{boldStart}Inactive%{boldEnd}."
msgstr ""
msgstr ""
...
@@ -9178,9 +9169,6 @@ msgstr ""
...
@@ -9178,9 +9169,6 @@ msgstr ""
msgid "FeatureFlags|Instance ID"
msgid "FeatureFlags|Instance ID"
msgstr ""
msgstr ""
msgid "FeatureFlags|List details"
msgstr ""
msgid "FeatureFlags|Loading feature flags"
msgid "FeatureFlags|Loading feature flags"
msgstr ""
msgstr ""
...
@@ -9196,15 +9184,9 @@ msgstr ""
...
@@ -9196,15 +9184,9 @@ msgstr ""
msgid "FeatureFlags|New Feature Flag"
msgid "FeatureFlags|New Feature Flag"
msgstr ""
msgstr ""
msgid "FeatureFlags|New Feature Flag User List"
msgstr ""
msgid "FeatureFlags|New feature flag"
msgid "FeatureFlags|New feature flag"
msgstr ""
msgstr ""
msgid "FeatureFlags|New list"
msgstr ""
msgid "FeatureFlags|Percent rollout (logged in users)"
msgid "FeatureFlags|Percent rollout (logged in users)"