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: README.MD
+7-4
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ make secret
82
82
83
83
<aname="footnote_fhs"></a>[1]: We recommend to use `/srv` folder instead `/var/www`. Create `/srv/apps` folder for your web apps. See [FHS](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s17.html).
84
84
85
-
### Launch
85
+
### Launch 🚀
86
86
87
87
1. Build the root `.env` file and run docker-compose:
88
88
@@ -102,12 +102,12 @@ make t=prod up
102
102
103
103
Do not edit the automatically concatenated root `.env` file. It will be overwritten every time the app run.
104
104
105
-
After the installation, you can add your custom secrets to `.env.secret`, but keep in mind that your secrets will not appear in the repository and will not be visible to other users. There is a `./sh/env/.env.secret.template` file for this. It has a template of secrets, without secret data.
105
+
After the installation, you can add your custom secrets 🔑 to `.env.secret`, but keep in mind that your secrets will not appear in the repository and will not be visible to other users. There is a `./sh/env/.env.secret.template` file for this. It has a template of secrets, without secret data.
106
106
107
107
You can add secret variables names there without secret data, just for structure. A password generator will replace the special word `generatethispass` with the real password when you run `make secret` (`bash sh/env/secret-gen.sh`).
108
108
109
109
110
-
:warning:**WARNING Do not define secrets (private keys, passwords, tokens, etc.) in committed files, it's not secure!**
110
+
⚠️**WARNING 📣 Do not define secrets (private keys, passwords, tokens, etc.) in committed files, it's not secure!**
111
111
112
112
### Production Launch with HTTPS
113
113
@@ -199,7 +199,7 @@ make pma-up
199
199
3. Open the `your-app-domain.com:PMA_EXT_PORT` URL in the browser to access phpMyadmin. For example, we use `PMA_EXT_PORT=8801`. Open `your-app-domain.com:8801`
200
200
201
201
202
-
:warning:**WARNING Do not use phpMyadmin on public (production or open stage), it's not secure!**
202
+
⚠️ **WARNING 📣 Do not use phpMyadmin on public (production or open stage), it's not secure!**
203
203
204
204
205
205
To stop the phpMyadmin container run command:
@@ -224,3 +224,6 @@ To activate backups:
224
224
225
225
Backups will appear in the `./backups` folder, logs in the docker cron container logs
226
226
227
+
## Contributing
228
+
229
+
Contributions are welcome from everyone. Developing with ❤️.
# Do not edit .conf file, it will override by script.
2
-
# Edit .template file to change settings
2
+
# Edit .conf.template file to change settings
3
3
4
4
location / {
5
5
# This is cool because no php is touched for static content.
6
6
# include the "?$args" part so non-default permalinks doesn't break when using query string
7
7
try_files $uri $uri/ /index.php?$args;
8
8
}
9
+
10
+
# Special directives for wp-admin area
11
+
# If you have media upload error:
12
+
# "Post-processing of the image failed likely because the server is busy or does not have enough resources. Uploading a smaller image may help. Suggested maximum size is 2500 pixels".
13
+
# Uncomment this rule. Generally, we are not recommend to upload large files. In most cases this is not necessary. Think twice
0 commit comments