Simplified Heroku variables configuration

- Having well defined variables is more readable than configuring
everything in MAVEN_CUSTOM_OPTS
- Do not provide a default admin password value : people deploying on
Heroku for testing or demonstration purpose would likely forget to
customize this password, which would be a security flaw
- reduce Heroku specific impacts on existing pom.xml

1 files changed, 10 insertions, 2 deletions

diff --git a/app.json b/app.json
index 42f4c7f50..61a35de86 100755
--- a/app.json
+++ b/app.json
@@ -12,9 +12,17 @@
 	"repository": "https://github.com/yacy/yacy_search_server",
 	"logo": "http://yacy.net/material/YaCyLogo2011.svg",
 	"env": {
+		"YACY_INIT_ADMIN_PASSWORD": {
+			"description": "Administrator initial password : please fill with a Base64 MD5 value",
+			"required": false
+		},
+		"YACY_PUBLIC_URL": {
+			"description": "External URL used by other peers to reach yours, required to run in 'Senior' mode. You chouls set it with [your_app_name].herokuapp.com`.",
+			"required": false
+		},
 		"MAVEN_CUSTOM_OPTS": {
-			"description": "Custom options required for maven build on Heroku. To run YaCy in senior mode, you MUST set -Dyacy.staticIP=your_app_name.herokuapp.com. Default admin password is 'heroku', passed encoded to -Dyacy.admin.passwd. You should replace it with your own custom password.",
-			"value": "-f libbuild/pom.xml -DskipTests=true -Dyacy.port=80 -Dyacy.admin.passwd=MD5:1029a0355adffb6378ceed9936ca9be4"
+			"description": "Custom options required for maven build on Heroku.",
+			"value": "-f libbuild/pom.xml -DskipTests=true"
 		}
 	}
 }
\ No newline at end of file