From b1345d92d2e933d94f2d03e3a866a8b82ed6feed Mon Sep 17 00:00:00 2001 From: luccioman Date: Wed, 13 Jul 2016 01:15:25 +0200 Subject: [PATCH] Fixed relative Markdown links --- Heroku.md | 12 ++++++------ README.md | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/Heroku.md b/Heroku.md index cf372f3cf..51fe30a8b 100755 --- a/Heroku.md +++ b/Heroku.md @@ -16,9 +16,9 @@ YaCy main git history is too large to be pushed on Heroku (more than 300MB Herok ## Deploy with the button -- Click on the 'Deploy to Heroku' button on the main YaCy [[README.md]]. +- Click on the 'Deploy to Heroku' button on the main YaCy [README.md](README.md). - Log in with your Heroku account or create one. -- A preconfigured deploy page is proposed (configuration comes from the [[app.json]] file). +- A preconfigured deploy page is proposed (configuration comes from the [app.json](app.json) file). - Enter the name of your application (don't let Heroku choose a default one). - Edit the environment variable `MAVEN_CUSTOM_OPTS` : insert ` -Dyacy.staticIP=your_app_name.herokuapp.com`, with `your_app_name` replaced with the name you choosed. If you ignore the two previous steps, YaCy will run, but in junior mode : it will not be able to be reached by other peers and will not contribute to the global indexing. @@ -69,15 +69,15 @@ Here are some brief instructions to deploy YaCy on Heroku from command line. Mor ### Heroku specific configuration files : -- [[app.json]] : used when deploying with the button -- [[.env]] : set up environment variables for local heroku run -- [[Procfile]] : contain main process description used to launch YaCy +- [app.json](app.json) : used when deploying with the button +- [.env](.env) : set up environment variables for local heroku run +- [Procfile](Procfile) : contain main process description used to launch YaCy ### Custom maven options With any of the deployment methods described, setting the option `-f libbuild/pom.xml -DskipTests=true` in the `MAVEN_CUSTOM_OPTS` environment variable is the minimum required for a successfull build and deploy. If not set, build will fail because missing dependent submodules from libbuild directory. -What'smore, the only way for other YaCy peers to reach a peer running on Heroku is to use the "dyno" public URL (in the form of your_app_name.herokuapp.com). This is why `-Dyacy.port=80` and `-Dyacy.staticIP=your_app_name.herokuapp.com` options have to be set in the `MAVEN_CUSTOM_OPTS` variable, or else your YaCy peer will run in "junior" mode. These options are used to customise `port` and `staticIP` initial properties in the [[defaults/yacy.init]] file at build. +What'smore, the only way for other YaCy peers to reach a peer running on Heroku is to use the "dyno" public URL (in the form of your_app_name.herokuapp.com). This is why `-Dyacy.port=80` and `-Dyacy.staticIP=your_app_name.herokuapp.com` options have to be set in the `MAVEN_CUSTOM_OPTS` variable, or else your YaCy peer will run in "junior" mode. These options are used to customise `port` and `staticIP` initial properties in the [yacy.init](defaults/yacy.init) file at build. ### HTTP local port diff --git a/README.md b/README.md index 45448495a..6db9ca5ad 100644 --- a/README.md +++ b/README.md @@ -123,13 +123,13 @@ These technologies can either be deployed locally, on remote machines you own, o Deploy easily YaCy on a Docker cloud provider of your choice (can be a machine you own) with the deploy button at the top of this page. -More details for YaCy with Docker in [[docker/Readme.md]]. +More details for YaCy with Docker in [docker/Readme.md](docker/Readme.md). ### Heroku Deploy easily on [Heroku](https://www.heroku.com/) PaaS (Platform as a service) provider using the deploy button at the top. -More details for YaCy on Heroku in [[Heroku.md]]. +More details for YaCy on Heroku in [Heroku.md](Heroku.md). ## Port 8090 is bad, people are not allowed to access that port