Denis Magda commented on IGNITE-4345:


The documentation is still hard coded to specific versions. For instance, I see 
the following in the shell commands.

# Pull ignite version 1.7.0
sudo docker pull apacheignite/ignite:1.7.0

# Run ignite version 1.4.0
sudo docker run -it --net=host 

Let's use something like {ignite-version} instead of 1.4.0 or 1.7.0 to avoid 
documentation updates every time a new version gets released.

Next, as for AWS and GCE, I would move it to its own documentation pages and 
clean on out outdated reference to the images. As an example, GCE section 
refers to this old image 
which even doesn't exist any longer.

I would modify both AWS and GCE in such a way when there is no need to paste 
the links to images but rather would provide instruction on how to look for a 
gridgain image on a cloud environment using its internal search capabilities.

> incorrect/outdated info on site
> -------------------------------
>                 Key: IGNITE-4345
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4345
>             Project: Ignite
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Sergey Korzhevsky
>            Assignee: Nikolay Tikhonov
>            Priority: Critical
>             Fix For: 1.8
> Old/icorrect info on the site.
> 1) http://ignite.apache.org/download.cgi#docker
>    a) "guide" link points to 1.5 version
>    b) "docker repository" is a broken link, should be 
> https://hub.docker.com/u/apacheignite/
> i guess.
> 2) https://apacheignite.readme.io/v1.7/docs/docker-deployment
> IGNITE_CONFIG "example url"'s file (https://raw.githubusercontent.com/
> bob/master/ignite-cfg.xml) does not exists.
> I think, it may be pointed to the some file in the current github repo. 

This message was sent by Atlassian JIRA

Reply via email to