You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/topics/configuration.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,23 @@
2
2
3
3
The server comes well configured but the configuration can be tweaked. You should set your private recipes repo, all other options are optional.
4
4
5
-
In order to change the configuration, alter the file `/config/parameters.yaml`. Some of the values can be provided in a .env-file, take a look at the contained `.env.dist` for helpful hints.
5
+
In order to change the configuration, alter the file `/config/parameters.yaml`. Some of the values can be provided in environment variables or via .env-file, take a look at the contained `.env.dist` for helpful hints.
6
6
7
7
### Private recipes repo
8
8
9
9
Your private recipes repo must be a git repo. It must be available via git, so it should be either a public repo or you should ensure that your server has access to it, probably by setting up some sort of SSH keys. In order to make the server use your repo, set this parameter:
10
10
11
-
recipe_repo_private: The url to your private recipe repo
11
+
env(FLEX_RECIPE_REPO_PRIVATE): The url to your private recipe repo
12
12
13
-
The url provided must be a *https* url. Make sure to provide the right url structure, here are two examples:
13
+
The url provided should be a *https* url, but most valid git-urls will work. Make sure to provide the right url structure, here are some examples:
There have been reports regarding private bitbucket repos, where people needed to use the git url (`[email protected]:<user>/<repo>.git`), feel free to try that out in case you run into problems.
21
+
Github has proven to be quite good in resolving git requests, other providers or git servers may be pickier. If you run into problems, try to play with '.git', the protocol prefix or the type of url provided.
19
22
20
23
After changing the configuration, you'll need to update the repos. Whenever you change the repo entirely, it is recommended to completely reset the private repo by executing the command `php bin/console recipes:reset private`.
21
24
@@ -25,7 +28,7 @@ Read more about these commands [here](commands.md).
25
28
26
29
* If you want your server instance to **not** act as a proxy for the official endpoint, set `proxy_official_endpoint` to false. The default behaviour is to do so, because otherwise, Symfony probably won't work properly. You should have good reasons in order to disable it.
27
30
* If you don´t want the server to cache requests it makes to the official endpoint, set `cache_official_endpoint` to false. You won't notice any changes until network fails to load the official endpoint.
28
-
* If (for some reason) you want to have any other official endpoint than symfony.sh, change `official_endpoint`. You could setup a working endpoint chain by providing the url to a second instance of this server.
31
+
* If (for some reason) you want to have any other official endpoint than symfony.sh, change `env(FLEX_OFFICIAL_ENDPOINT)`. You could setup a working endpoint chain by providing the url to a second instance of this server.
29
32
30
33
### Mirroring the official recipe repos
31
34
@@ -36,8 +39,8 @@ Having a local copy of the official repos might be something you consider. You c
36
39
37
40
Also, you might want to use your own forks of the official repos, you could use them by changing two options:
38
41
39
-
recipe_repo_official: The url to the official recipe repo
40
-
recipe_repo_contrib: The url to the contrib recipe repo
42
+
env(FLEX_RECIPE_REPO_OFFICIAL): The url to the official recipe repo
43
+
env(FLEX_RECIPE_REPO_CONTRIB): The url to the contrib recipe repo
41
44
42
45
If you use both the proxy functionality **and** custom official repos, the official endpoint responses will be used only for recipes that are not available in your repos.
Copy file name to clipboardExpand all lines: docs/topics/setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Setting up the server should be quick and easy. These are the necessary steps:
4
4
5
5
1.[Download](https://github.com/moay/symfony-flex-server/releases) the project from Github (or `git clone https://github.com/moay/symfony-flex-server`)
6
6
2. Navigate to the project folder and run `composer install`.
7
-
3. Open the file `config/services.yaml` and enter the url to your private recipes repo.
7
+
3. Open the file `config/parameters.yaml` and enter the url to your private recipes repo (or provide appropriate environment variables).
8
8
4. Setup the `APP_ENV` properly. This can be done in the `.env` file (create if needed) or on the hosting. Setting it to `prod` is recommended.
9
9
5. Run `php bin/console recipes:initialize` in order to download your recipes.
10
10
@@ -37,4 +37,4 @@ Make sure to allow connections over http to composer (if using localhost) by add
37
37
}
38
38
}
39
39
40
-
*It is not recommended to run the server locally. The best setup would be a private server behind a firewall.*
40
+
*It is not recommended to run the server locally. The best setup would be a private server behind a firewall.*
0 commit comments