-#
-# A client is immediately disconnected once the hard limit is reached, or if
-# the soft limit is reached and remains reached for the specified number of
-# seconds (continuously).
-# So for instance if the hard limit is 32 megabytes and the soft limit is
-# 16 megabytes / 10 seconds, the client will get disconnected immediately
-# if the size of the output buffers reach 32 megabytes, but will also get
-# disconnected if the client reaches 16 megabytes and continuously overcomes
-# the limit for 10 seconds.
-#
-# By default normal clients are not limited because they don't receive data
-# without asking (in a push way), but just after a request, so only
-# asynchronous clients may create a scenario where data is requested faster
-# than it can read.
-#
-# Instead there is a default limit for pubsub and replica clients, since
-# subscribers and replicas receive data in a push fashion.
-#
-# Note that it doesn't make sense to set the replica clients output buffer
-# limit lower than the repl-backlog-size config (partial sync will succeed
-# and then replica will get disconnected).
-# Such a configuration is ignored (the size of repl-backlog-size will be used).
-# This doesn't have memory consumption implications since the replica client
-# will share the backlog buffers memory.
-#
-# Both the hard or the soft limit can be disabled by setting them to zero.
-client-output-buffer-limit normal 0 0 0
-client-output-buffer-limit replica 256mb 64mb 60
-client-output-buffer-limit pubsub 32mb 8mb 60
-
-# Client query buffers accumulate new commands. They are limited to a fixed
-# amount by default in order to avoid that a protocol desynchronization (for
-# instance due to a bug in the client) will lead to unbound memory usage in
-# the query buffer. However you can configure it here if you have very special
-# needs, such us huge multi/exec requests or alike.
-#
-# client-query-buffer-limit 1gb
-
-# In some scenarios client connections can hog up memory leading to OOM
-# errors or data eviction. To avoid this we can cap the accumulated memory
-# used by all client connections (all pubsub and normal clients). Once we
-# reach that limit connections will be dropped by the server freeing up
-# memory. The server will attempt to drop the connections using the most
-# memory first. We call this mechanism "client eviction".
-#
-# Client eviction is configured using the maxmemory-clients setting as follows:
-# 0 - client eviction is disabled (default)
-#
-# A memory value can be used for the client eviction threshold,
-# for example:
-# maxmemory-clients 1g
-#
-# A percentage value (between 1% and 100%) means the client eviction threshold
-# is based on a percentage of the maxmemory setting. For example to set client
-# eviction at 5% of maxmemory:
-# maxmemory-clients 5%
-
-# In the Redis protocol, bulk requests, that are, elements representing single
-# strings, are normally limited to 512 mb. However you can change this limit
-# here, but must be 1mb or greater
-#
-# proto-max-bulk-len 512mb
-
-# Redis calls an internal function to perform many background tasks, like
-# closing connections of clients in timeout, purging expired keys that are
-# never requested, and so forth.
-#
-# Not all tasks are performed with the same frequency, but Redis checks for
-# tasks to perform according to the specified "hz" value.
-#
-# By default "hz" is set to 10. Raising the value will use more CPU when
-# Redis is idle, but at the same time will make Redis more responsive when
-# there are many keys expiring at the same time, and timeouts may be
-# handled with more precision.
-#
-# The range is between 1 and 500, however a value over 100 is usually not
-# a good idea. Most users should use the default of 10 and raise this up to
-# 100 only in environments where very low latency is required.
-hz 10
-
-# Normally it is useful to have an HZ value which is proportional to the
-# number of clients connected. This is useful in order, for instance, to
-# avoid too many clients are processed for each background task invocation
-# in order to avoid latency spikes.
-#
-# Since the default HZ value by default is conservatively set to 10, Redis
-# offers, and enables by default, the ability to use an adaptive HZ value
-# which will temporarily raise when there are many connected clients.
-#
-# When dynamic HZ is enabled, the actual configured HZ will be used
-# as a baseline, but multiples of the configured HZ value will be actually
-# used as needed once more clients are connected. In this way an idle
-# instance will use very little CPU time while a busy instance will be
-# more responsive.
-dynamic-hz yes
-
-# When a child rewrites the AOF file, if the following option is enabled
-# the file will be fsync-ed every 4 MB of data generated. This is useful
-# in order to commit the file to the disk more incrementally and avoid
-# big latency spikes.
-aof-rewrite-incremental-fsync yes
-
-# When redis saves RDB file, if the following option is enabled
-# the file will be fsync-ed every 4 MB of data generated. This is useful
-# in order to commit the file to the disk more incrementally and avoid
-# big latency spikes.
-rdb-save-incremental-fsync yes
-
-# Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good
-# idea to start with the default settings and only change them after investigating
-# how to improve the performances and how the keys LFU change over time, which
-# is possible to inspect via the OBJECT FREQ command.
-#
-# There are two tunable parameters in the Redis LFU implementation: the
-# counter logarithm factor and the counter decay time. It is important to
-# understand what the two parameters mean before changing them.
-#
-# The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis
-# uses a probabilistic increment with logarithmic behavior. Given the value
-# of the old counter, when a key is accessed, the counter is incremented in
-# this way:
-#
-# 1. A random number R between 0 and 1 is extracted.
-# 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1).
-# 3. The counter is incremented only if R < P.
-#
-# The default lfu-log-factor is 10. This is a table of how the frequency
-# counter changes with a different number of accesses with different
-# logarithmic factors:
-#
-# +--------+------------+------------+------------+------------+------------+
-# | factor | 100 hits | 1000 hits | 100K hits | 1M hits | 10M hits |
-# +--------+------------+------------+------------+------------+------------+
-# | 0 | 104 | 255 | 255 | 255 | 255 |
-# +--------+------------+------------+------------+------------+------------+
-# | 1 | 18 | 49 | 255 | 255 | 255 |
-# +--------+------------+------------+------------+------------+------------+
-# | 10 | 10 | 18 | 142 | 255 | 255 |
-# +--------+------------+------------+------------+------------+------------+
-# | 100 | 8 | 11 | 49 | 143 | 255 |
-# +--------+------------+------------+------------+------------+------------+
-#
-# NOTE: The above table was obtained by running the following commands:
-#
-# redis-benchmark -n 1000000 incr foo
-# redis-cli object freq foo
-#
-# NOTE 2: The counter initial value is 5 in order to give new objects a chance
-# to accumulate hits.
-#
-# The counter decay time is the time, in minutes, that must elapse in order
-# for the key counter to be divided by two (or decremented if it has a value
-# less <= 10).
-#
-# The default value for the lfu-decay-time is 1. A special value of 0 means to
-# decay the counter every time it happens to be scanned.
-#
-# lfu-log-factor 10
-# lfu-decay-time 1
-
-########################### ACTIVE DEFRAGMENTATION #######################
-#
-# What is active defragmentation?
-# -------------------------------
-#
-# Active (online) defragmentation allows a Redis server to compact the
-# spaces left between small allocations and deallocations of data in memory,
-# thus allowing to reclaim back memory.
-#
-# Fragmentation is a natural process that happens with every allocator (but
-# less so with Jemalloc, fortunately) and certain workloads. Normally a server
-# restart is needed in order to lower the fragmentation, or at least to flush
-# away all the data and create it again. However thanks to this feature
-# implemented by Oran Agra for Redis 4.0 this process can happen at runtime
-# in a "hot" way, while the server is running.
-#
-# Basically when the fragmentation is over a certain level (see the
-# configuration options below) Redis will start to create new copies of the
-# values in contiguous memory regions by exploiting certain specific Jemalloc
-# features (in order to understand if an allocation is causing fragmentation
-# and to allocate it in a better place), and at the same time, will release the
-# old copies of the data. This process, repeated incrementally for all the keys
-# will cause the fragmentation to drop back to normal values.
-#
-# Important things to understand:
-#
-# 1. This feature is disabled by default, and only works if you compiled Redis
-# to use the copy of Jemalloc we ship with the source code of Redis.
-# This is the default with Linux builds.
-#
-# 2. You never need to enable this feature if you don't have fragmentation
-# issues.
-#
-# 3. Once you experience fragmentation, you can enable this feature when
-# needed with the command "CONFIG SET activedefrag yes".
-#
-# The configuration parameters are able to fine tune the behavior of the
-# defragmentation process. If you are not sure about what they mean it is
-# a good idea to leave the defaults untouched.
-
-# Active defragmentation is disabled by default
-# activedefrag no
-
-# Minimum amount of fragmentation waste to start active defrag
-# active-defrag-ignore-bytes 100mb
-
-# Minimum percentage of fragmentation to start active defrag
-# active-defrag-threshold-lower 10
-
-# Maximum percentage of fragmentation at which we use maximum effort
-# active-defrag-threshold-upper 100
-
-# Minimal effort for defrag in CPU percentage, to be used when the lower
-# threshold is reached
-# active-defrag-cycle-min 1
-
-# Maximal effort for defrag in CPU percentage, to be used when the upper
-# threshold is reached
-# active-defrag-cycle-max 25
-
-# Maximum number of set/hash/zset/list fields that will be processed from
-# the main dictionary scan
-# active-defrag-max-scan-fields 1000
-
-# Jemalloc background thread for purging will be enabled by default
-jemalloc-bg-thread yes
-
-# It is possible to pin different threads and processes of Redis to specific
-# CPUs in your system, in order to maximize the performances of the server.
-# This is useful both in order to pin different Redis threads in different
-# CPUs, but also in order to make sure that multiple Redis instances running
-# in the same host will be pinned to different CPUs.
-#
-# Normally you can do this using the "taskset" command, however it is also
-# possible to this via Redis configuration directly, both in Linux and FreeBSD.
-#
-# You can pin the server/IO threads, bio threads, aof rewrite child process, and
-# the bgsave child process. The syntax to specify the cpu list is the same as
-# the taskset command:
-#
-# Set redis server/io threads to cpu affinity 0,2,4,6:
-# server_cpulist 0-7:2
-#
-# Set bio threads to cpu affinity 1,3:
-# bio_cpulist 1,3
-#
-# Set aof rewrite child process to cpu affinity 8,9,10,11:
-# aof_rewrite_cpulist 8-11
-#
-# Set bgsave child process to cpu affinity 1,10,11
-# bgsave_cpulist 1,10-11
-
-# In some cases redis will emit warnings and even refuse to start if it detects
-# that the system is in bad state, it is possible to suppress these warnings
-# by setting the following config which takes a space delimited list of warnings
-# to suppress
-#
-# ignore-warnings ARM64-COW-BUG
diff --git a/apps/redis/versions/7.0.5/config.json b/apps/redis/versions/7.0.5/config.json
deleted file mode 100644
index f39c23697..000000000
--- a/apps/redis/versions/7.0.5/config.json
+++ /dev/null
@@ -1,20 +0,0 @@
-{
- "formFields": [
- {
- "type": "password",
- "labelZh": "密码",
- "labelEn": "Password",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_ROOT_PASSWORD"
- },
- {
- "type": "number",
- "labelZh": "端口",
- "labelEn": "Port",
- "required": true,
- "default": 6379,
- "envKey": "PANEL_APP_PORT_HTTP"
- }
- ]
-}
\ No newline at end of file
diff --git a/apps/redis/versions/7.0.5/docker-compose.yml b/apps/redis/versions/7.0.5/docker-compose.yml
deleted file mode 100644
index e67775969..000000000
--- a/apps/redis/versions/7.0.5/docker-compose.yml
+++ /dev/null
@@ -1,20 +0,0 @@
-version: '3'
-services:
- redis-7.0.5:
- image: redis:7.0.5
- restart: always
- networks:
- - 1panel
- ports:
- - ${PANEL_APP_PORT_HTTP}:6379
- command: redis-server /etc/redis/redis.conf --requirepass ${PANEL_DB_ROOT_PASSWORD}
- volumes:
- - ./data:/data
- - ./conf/redis.conf:/etc/redis/redis.conf
- - ./logs:/logs
- labels:
- createdBy: "Apps"
-
-networks:
- 1panel:
- external: true
\ No newline at end of file
diff --git a/apps/wordpress/metadata/logo.png b/apps/wordpress/metadata/logo.png
deleted file mode 100644
index 2cae20c7d..000000000
Binary files a/apps/wordpress/metadata/logo.png and /dev/null differ
diff --git a/apps/wordpress/versions/6.0.1/README.md b/apps/wordpress/versions/6.0.1/README.md
deleted file mode 100644
index c62eb7090..000000000
--- a/apps/wordpress/versions/6.0.1/README.md
+++ /dev/null
@@ -1,84 +0,0 @@
-Semantic Personal Publishing Platform
-
-First Things First
-Welcome. WordPress is a very special project to me. Every developer and contributor adds something unique to the mix, and together we create something beautiful that I am proud to be a part of. Thousands of hours have gone into WordPress, and we are dedicated to making it better every day. Thank you for making it part of your world.
-— Matt Mullenweg
-
-Installation: Famous 5-minute install
-
- - Unzip the package in an empty directory and upload everything.
- - Open wp-admin/install.php in your browser. It will take you through the process to set up a
wp-config.php file with your database connection details.
-
- - If for some reason this does not work, do not worry. It may not work on all web hosts. Open up
wp-config-sample.php with a text editor like WordPad or similar and fill in your database connection details.
- - Save the file as
wp-config.php and upload it.
- - Open wp-admin/install.php in your browser.
-
-
- - Once the configuration file is set up, the installer will set up the tables needed for your site. If there is an error, double check your
wp-config.php file, and try again. If it fails again, please go to the WordPress support forums with as much data as you can gather.
- - If you did not enter a password, note the password given to you. If you did not provide a username, it will be
admin.
- - The installer should then send you to the login page. Sign in with the username and password you chose during the installation. If a password was generated for you, you can then click on “Profile” to change the password.
-
-
-Updating
-Using the Automatic Updater
-
- - Open wp-admin/update-core.php in your browser and follow the instructions.
- - You wanted more, perhaps? That’s it!
-
-
-Updating Manually
-
- - Before you update anything, make sure you have backup copies of any files you may have modified such as
index.php.
- - Delete your old WordPress files, saving ones you’ve modified.
- - Upload the new files.
- - Point your browser to /wp-admin/upgrade.php.
-
-
-Migrating from other systems
-WordPress can import from a number of systems. First you need to get WordPress installed and working as described above, before using our import tools.
-
-System Requirements
-
- - PHP version 5.6.20 or greater.
- - MySQL version 5.0 or greater.
-
-
-Recommendations
-
-
-Online Resources
-If you have any questions that are not addressed in this document, please take advantage of WordPress’ numerous online resources:
-
- - HelpHub
- - HelpHub is the encyclopedia of all things WordPress. It is the most comprehensive source of information for WordPress available.
- - The WordPress Blog
- - This is where you’ll find the latest updates and news related to WordPress. Recent WordPress news appears in your administrative dashboard by default.
- - WordPress Planet
- - The WordPress Planet is a news aggregator that brings together posts from WordPress blogs around the web.
- - WordPress Support Forums
- - If you’ve looked everywhere and still cannot find an answer, the support forums are very active and have a large community ready to help. To help them help you be sure to use a descriptive thread title and describe your question in as much detail as possible.
- - WordPress IRC (Internet Relay Chat) Channel
- - There is an online chat channel that is used for discussion among people who use WordPress and occasionally support topics. The above wiki page should point you in the right direction. (irc.libera.chat #wordpress)
-
-
-Final Notes
-
- - If you have any suggestions, ideas, or comments, or if you (gasp!) found a bug, join us in the Support Forums.
- - WordPress has a robust plugin API (Application Programming Interface) that makes extending the code easy. If you are a developer interested in utilizing this, see the Plugin Developer Handbook. You shouldn’t modify any of the core code.
-
-
-Share the Love
-WordPress has no multi-million dollar marketing campaign or celebrity sponsors, but we do have something even better—you. If you enjoy WordPress please consider telling a friend, setting it up for someone less knowledgeable than yourself, or writing the author of a media article that overlooks us.
-
-WordPress is the official continuation of b2/cafélog, which came from Michel V. The work has been continued by the WordPress developers. If you would like to support WordPress, please consider donating.
-
-License
-WordPress is free software, and is released under the terms of the GPL (GNU General Public License) version 2 or (at your option) any later version. See license.txt.
-
-
diff --git a/apps/wordpress/versions/6.0.1/config.json b/apps/wordpress/versions/6.0.1/config.json
deleted file mode 100644
index 3b80651c0..000000000
--- a/apps/wordpress/versions/6.0.1/config.json
+++ /dev/null
@@ -1,45 +0,0 @@
-{
- "formFields": [
- {
- "type": "service",
- "key": "mysql",
- "labelZh": "数据库服务",
- "labelEn": "Database Service",
- "required": true,
- "default": "",
- "envKey": "PANEL_DB_HOST"
- },
- {
- "type": "text",
- "labelZh": "数据库名",
- "labelEn": "Database",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_NAME"
- },
- {
- "type": "text",
- "labelZh": "数据库用户",
- "labelEn": "User",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_USER"
- },
- {
- "type": "password",
- "labelZh": "数据库用户密码",
- "labelEn": "Password",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_USER_PASSWORD"
- },
- {
- "type": "number",
- "labelZh": "应用端口",
- "labelEn": "Port",
- "required": true,
- "default": 8080,
- "envKey": "PANEL_APP_PORT_HTTP"
- }
- ]
-}
\ No newline at end of file
diff --git a/apps/wordpress/versions/6.0.1/docker-compose.yml b/apps/wordpress/versions/6.0.1/docker-compose.yml
deleted file mode 100644
index e61dc4062..000000000
--- a/apps/wordpress/versions/6.0.1/docker-compose.yml
+++ /dev/null
@@ -1,24 +0,0 @@
-version: '3'
-services:
- 1panel_wordpress:
- image: wordpress:6.0.1
- container_name: ${CONTAINER_NAME}
- ports:
- - ${PANEL_APP_PORT_HTTP}:80
- restart: always
- networks:
- - 1panel
- volumes:
- - ./data:/var/www/html
- environment:
- WORDPRESS_DB_HOST: ${PANEL_DB_HOST}
- WORDPRESS_DB_NAME: ${PANEL_DB_NAME}
- WORDPRESS_DB_USER: ${PANEL_DB_USER}
- WORDPRESS_DB_PASSWORD: ${PANEL_DB_USER_PASSWORD}
- WORDPRESS_DEBUG: 1
- labels:
- createdBy: "Apps"
-
-networks:
- 1panel:
- external: true
\ No newline at end of file
diff --git a/apps/wordpress/versions/6.0.2/README.md b/apps/wordpress/versions/6.0.2/README.md
deleted file mode 100644
index 6fbd4427f..000000000
--- a/apps/wordpress/versions/6.0.2/README.md
+++ /dev/null
@@ -1,82 +0,0 @@
-Semantic Personal Publishing Platform
-
-First Things First
-Welcome. WordPress is a very special project to me. Every developer and contributor adds something unique to the mix, and together we create something beautiful that I am proud to be a part of. Thousands of hours have gone into WordPress, and we are dedicated to making it better every day. Thank you for making it part of your world.
-— Matt Mullenweg
-
-Installation: Famous 5-minute install
-
- - Unzip the package in an empty directory and upload everything.
- - Open wp-admin/install.php in your browser. It will take you through the process to set up a
wp-config.php file with your database connection details.
-
- - If for some reason this does not work, do not worry. It may not work on all web hosts. Open up
wp-config-sample.php with a text editor like WordPad or similar and fill in your database connection details.
- - Save the file as
wp-config.php and upload it.
- - Open wp-admin/install.php in your browser.
-
-
- - Once the configuration file is set up, the installer will set up the tables needed for your site. If there is an error, double check your
wp-config.php file, and try again. If it fails again, please go to the WordPress support forums with as much data as you can gather.
- - If you did not enter a password, note the password given to you. If you did not provide a username, it will be
admin.
- - The installer should then send you to the login page. Sign in with the username and password you chose during the installation. If a password was generated for you, you can then click on “Profile” to change the password.
-
-
-Updating
-Using the Automatic Updater
-
- - Open wp-admin/update-core.php in your browser and follow the instructions.
- - You wanted more, perhaps? That’s it!
-
-
-Updating Manually
-
- - Before you update anything, make sure you have backup copies of any files you may have modified such as
index.php.
- - Delete your old WordPress files, saving ones you’ve modified.
- - Upload the new files.
- - Point your browser to /wp-admin/upgrade.php.
-
-
-Migrating from other systems
-WordPress can import from a number of systems. First you need to get WordPress installed and working as described above, before using our import tools.
-
-System Requirements
-
- - PHP version 5.6.20 or greater.
- - MySQL version 5.0 or greater.
-
-
-Recommendations
-
-
-Online Resources
-If you have any questions that are not addressed in this document, please take advantage of WordPress’ numerous online resources:
-
- - HelpHub
- - HelpHub is the encyclopedia of all things WordPress. It is the most comprehensive source of information for WordPress available.
- - The WordPress Blog
- - This is where you’ll find the latest updates and news related to WordPress. Recent WordPress news appears in your administrative dashboard by default.
- - WordPress Planet
- - The WordPress Planet is a news aggregator that brings together posts from WordPress blogs around the web.
- - WordPress Support Forums
- - If you’ve looked everywhere and still cannot find an answer, the support forums are very active and have a large community ready to help. To help them help you be sure to use a descriptive thread title and describe your question in as much detail as possible.
- - WordPress IRC (Internet Relay Chat) Channel
- - There is an online chat channel that is used for discussion among people who use WordPress and occasionally support topics. The above wiki page should point you in the right direction. (irc.libera.chat #wordpress)
-
-
-Final Notes
-
- - If you have any suggestions, ideas, or comments, or if you (gasp!) found a bug, join us in the Support Forums.
- - WordPress has a robust plugin API (Application Programming Interface) that makes extending the code easy. If you are a developer interested in utilizing this, see the Plugin Developer Handbook. You shouldn’t modify any of the core code.
-
-
-Share the Love
-WordPress has no multi-million dollar marketing campaign or celebrity sponsors, but we do have something even better—you. If you enjoy WordPress please consider telling a friend, setting it up for someone less knowledgeable than yourself, or writing the author of a media article that overlooks us.
-
-WordPress is the official continuation of b2/cafélog, which came from Michel V. The work has been continued by the WordPress developers. If you would like to support WordPress, please consider donating.
-
-License
-WordPress is free software, and is released under the terms of the GPL (GNU General Public License) version 2 or (at your option) any later version. See license.txt.
diff --git a/apps/wordpress/versions/6.0.2/config.json b/apps/wordpress/versions/6.0.2/config.json
deleted file mode 100644
index 3b80651c0..000000000
--- a/apps/wordpress/versions/6.0.2/config.json
+++ /dev/null
@@ -1,45 +0,0 @@
-{
- "formFields": [
- {
- "type": "service",
- "key": "mysql",
- "labelZh": "数据库服务",
- "labelEn": "Database Service",
- "required": true,
- "default": "",
- "envKey": "PANEL_DB_HOST"
- },
- {
- "type": "text",
- "labelZh": "数据库名",
- "labelEn": "Database",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_NAME"
- },
- {
- "type": "text",
- "labelZh": "数据库用户",
- "labelEn": "User",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_USER"
- },
- {
- "type": "password",
- "labelZh": "数据库用户密码",
- "labelEn": "Password",
- "required": true,
- "default": "random",
- "envKey": "PANEL_DB_USER_PASSWORD"
- },
- {
- "type": "number",
- "labelZh": "应用端口",
- "labelEn": "Port",
- "required": true,
- "default": 8080,
- "envKey": "PANEL_APP_PORT_HTTP"
- }
- ]
-}
\ No newline at end of file
diff --git a/apps/wordpress/versions/6.0.2/docker-compose.yml b/apps/wordpress/versions/6.0.2/docker-compose.yml
deleted file mode 100644
index 40d10aba8..000000000
--- a/apps/wordpress/versions/6.0.2/docker-compose.yml
+++ /dev/null
@@ -1,24 +0,0 @@
-version: '3'
-services:
- 1panel_wordpress:
- image: wordpress:6.0.2
- container_name: ${CONTAINER_NAME}
- ports:
- - ${PANEL_APP_PORT_HTTP}:80
- restart: always
- networks:
- - 1panel
- volumes:
- - ./data:/var/www/html
- environment:
- WORDPRESS_DB_HOST: ${PANEL_DB_HOST}
- WORDPRESS_DB_NAME: ${PANEL_DB_NAME}
- WORDPRESS_DB_USER: ${PANEL_DB_USER}
- WORDPRESS_DB_PASSWORD: ${PANEL_DB_USER_PASSWORD}
- WORDPRESS_DEBUG: 1
- labels:
- createdBy: "Apps"
-
-networks:
- 1panel:
- external: true
\ No newline at end of file
-
-
-