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
* redesign the website like figma
* well balanced and responsive
* satisfied with look of landing page
* fix color scheme changing by default. add user email sign up back end
;; For development purpose only. It makes Gitea handle sub-path ("/sub-path/owner/repo/...") directly when debugging without a reverse proxy.
84
+
;; For development purpose only. It makes Bindersnap handle sub-path ("/sub-path/owner/repo/...") directly when debugging without a reverse proxy.
85
85
;; DO NOT USE IT IN PRODUCTION!!!
86
86
;USE_SUB_URL_PATH = false
87
87
;;
@@ -124,7 +124,7 @@ RUN_USER = ; git
124
124
;; Permission for unix socket
125
125
;UNIX_SOCKET_PERMISSION = 666
126
126
;;
127
-
;; Local (DMZ) URL for Gitea workers (such as SSH update) accessing web service. In
127
+
;; Local (DMZ) URL for Bindersnap workers (such as SSH update) accessing web service. In
128
128
;; most cases you do not need to change the default value. Alter it only if
129
129
;; your SSH server node is not the same as HTTP node. For different protocol, the default
130
130
;; values are different. If `PROTOCOL` is `http+unix`, the default value is `http://unix/`.
@@ -166,11 +166,11 @@ RUN_USER = ; git
166
166
;; Root path of SSH directory, default is '~/.ssh', but you have to use '/home/git/.ssh'.
167
167
;SSH_ROOT_PATH =
168
168
;;
169
-
;; Gitea will create a authorized_keys file by default when it is not using the internal ssh server
169
+
;; Bindersnap will create a authorized_keys file by default when it is not using the internal ssh server
170
170
;; If you intend to use the AuthorizedKeysCommand functionality then you should turn this off.
171
171
;SSH_CREATE_AUTHORIZED_KEYS_FILE = true
172
172
;;
173
-
;; Gitea will create a authorized_principals file by default when it is not using the internal ssh server
173
+
;; Bindersnap will create a authorized_principals file by default when it is not using the internal ssh server
174
174
;; If you intend to use the AuthorizedPrincipalsCommand functionality then you should turn this off.
175
175
;SSH_CREATE_AUTHORIZED_PRINCIPALS_FILE = true
176
176
;;
@@ -195,7 +195,7 @@ RUN_USER = ; git
195
195
;; default is the system temporary directory.
196
196
;SSH_KEY_TEST_PATH =
197
197
;;
198
-
;; Use `ssh-keygen` to parse public SSH keys. The value is passed to the shell. By default, Gitea does the parsing itself.
198
+
;; Use `ssh-keygen` to parse public SSH keys. The value is passed to the shell. By default, Bindersnap does the parsing itself.
199
199
;SSH_KEYGEN_PATH =
200
200
;;
201
201
;; Enable SSH Authorized Key Backup when rewriting all keys, default is false
@@ -282,7 +282,7 @@ RUN_USER = ; git
282
282
;KEY_FILE = https/key.pem
283
283
;;
284
284
;; Root directory containing templates and static files.
285
-
;; default is the path where Gitea is executed
285
+
;; default is the path where Bindersnap is executed
286
286
;STATIC_ROOT_PATH = ; Will default to the built-in value _`StaticRootPath`_
287
287
;;
288
288
;; Default path for App data
@@ -361,7 +361,7 @@ NAME = gitea
361
361
USER = root
362
362
;PASSWD = ;Use PASSWD = `your password` for quoting if you use special characters in the password.
363
363
;SSL_MODE = false ; either "false" (default), "true", or "skip-verify"
364
-
;CHARSET_COLLATION = ; Empty as default, Gitea will try to find a case-sensitive collation. Don't change it unless you clearly know what you need.
364
+
;CHARSET_COLLATION = ; Empty as default, Bindersnap will try to find a case-sensitive collation. Don't change it unless you clearly know what you need.
365
365
;;
366
366
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
367
367
;;
@@ -393,7 +393,7 @@ USER = root
393
393
;NAME = gitea
394
394
;USER = SA
395
395
;PASSWD = MwantsaSecurePassword1
396
-
;CHARSET_COLLATION = ; Empty as default, Gitea will try to find a case-sensitive collation. Don't change it unless you clearly know what you need.
396
+
;CHARSET_COLLATION = ; Empty as default, Bindersnap will try to find a case-sensitive collation. Don't change it unless you clearly know what you need.
397
397
;;
398
398
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
399
399
;;
@@ -444,7 +444,7 @@ SECRET_KEY =
444
444
;; This key is VERY IMPORTANT. If you lose it, the data encrypted by it (like 2FA secret) can't be decrypted anymore.
445
445
;SECRET_KEY_URI = file:/etc/gitea/secret_key
446
446
;;
447
-
;; Secret used to validate communication within Gitea binary.
447
+
;; Secret used to validate communication within Bindersnap binary.
448
448
INTERNAL_TOKEN =
449
449
;;
450
450
;; Alternative location to specify internal token, instead of this file; you cannot specify both this and INTERNAL_TOKEN, and must pick one
@@ -478,9 +478,9 @@ INTERNAL_TOKEN =
478
478
;;
479
479
;; Set to false to allow users with git hook privileges to create custom git hooks.
480
480
;; Custom git hooks can be used to perform arbitrary code execution on the host operating system.
481
-
;; This enables the users to access and modify this config file and the Gitea database and interrupt the Gitea service.
482
-
;; By modifying the Gitea database, users can gain Gitea administrator privileges.
483
-
;; It also enables them to access other resources available to the user on the operating system that is running the Gitea instance and perform arbitrary actions in the name of the Gitea OS user.
481
+
;; This enables the users to access and modify this config file and the Bindersnap database and interrupt the Bindersnap service.
482
+
;; By modifying the Bindersnap database, users can gain Bindersnap administrator privileges.
483
+
;; It also enables them to access other resources available to the user on the operating system that is running the Bindersnap instance and perform arbitrary actions in the name of the Bindersnap OS user.
484
484
;; WARNING: This maybe harmful to you website or your operating system.
485
485
;; WARNING: Setting this to true does not change existing hooks in git repos; adjust it before if necessary.
0 commit comments