Re: [OSGeoLive] All OSGeoLive Docs versions online
+1 Good idea. On 16/12/19 9:02 pm, Angelos Tzotsos wrote: Excellent work Seth! Thanks for making the archive. Lets plan on setting the archive repo and the subdomain during the meeting tomorrow. Best, Angelos On 12/15/19 6:29 PM, Seth G wrote: Hi Cameron, Some answers in the email below. If you are able to find out how we can make a new https://github.com/OSGeo/OSGeoLive-archive repository and a new subdomain at osgeo.org I can hopefully take care of the rest. Seth -- web:http://geographika.co.uk twitter: @geographika On Sat, Dec 14, 2019, at 8:59 PM, Cameron Shorter wrote: Hi Seth, I was wondering why we don't have a symlink problem for images with the latest few releases? Looking at https://live.osgeo.org/de/index.html it appears that Vicky's new doc build script is smart enough to not create duplicate images for different languages (which as the case before). If you look at the old archive directory for say release 10.5, you see that we have duplicates of images. Eg: English version of docs points to: https://live.osgeo.org/archive/10.5/_images/osgeolive_menu6.png German version points to: https://live.osgeo.org/archive/10.5/_images/osgeolive_menu2.png To save space from images, Hamish Bowman wrote a script to create symlinks. I have a few ideas in moving forward: 0. To work out the broken symlink problem for images, you could: * Try and work out how to fix the symlink problem as you suggest. You might be able to find Hamish's old symlink generation script in the bin/ directory somewhere to help with that. (This sounds like a lot of work). * Copy the HTML from our archive web pages (which uses duplicate images). This will create a large repository due to duplicate images, which isn't perfect, but we will be rarely working on the archive repository, so it is probably acceptable. I've written a small Python script to change the symlinks to copies of the images. See https://github.com/geographika/OSGeoLive-doc/blob/gh-pages/scripts/symlinks.py It does create a larger repo, but probably simpler to manage across different OSs than symlinks in the long-term. All images should now be visible in the archive URL. 1. I think this historical archive of past releases you have created is really valuable. Thanks! 2. I think it should be findable from the main docs, probably as a small link at the bottom of https://live.osgeo.org : Prior releases and docs can be found in our archive/. This archive would be the jump page you have created. Sounds good. I guess we need to decide where the archive will be hosted (which URL/subdomain). Maybe https://archive.osgeo.org/ or Maybe https://livearchive.osgeo.org/ ? Who would be contact with regards to setting up a domain name? 3. While the archive jump page can be stored in our master docs, I don't think we should store each releases' archive in there. We can either keep it on a directory, as was previously done for prior releases. Or put into git, as you have done (which I like). I think that it deserves its own repository, something like OSGeoLive-doc-archive Currently the archive is in a branch so shouldn't increase size of git clone downloads etc. but moving to its own archive may make things clearer. Who would we contact with regards to creating a new repo at https://github.com/OSGeo/ ? 4. We should capture information about the latest doc release, and information about the archive in our build process documentation wiki: https://trac.osgeo.org/osgeolive/wiki. Would you like to update this? (You deserve the credit in the wiki history.) The build information is already linked to on https://trac.osgeo.org/osgeolive/wiki I've updated the link to the development build to point to OSGeoLive home page (development version). 5. Felicity has a bunch of pull requests for quickstarts. https://github.com/OSGeo/OSGeoLive-doc/pulls which are to be processed for the 13.1 doc release early next year. I'll try and get at least one of two reviewed within the week in order to check your publishing of the master docs pipeline. I don't think these pull requests have the Appveyor CI merged into them so they don't currently trigger builds. If we add a link to the archives we can see if this process works on a new pull request. Cheers, Cameron On 15/12/19 4:47 am, Seth G wrote: Thanks for the feedback and kind words Cameron! I got the docs from the ISOs - see https://github.com/geographika/OSGeoLive-doc/tree/gh-pages#extraction-process After further investigation the missing images are due to the files being symlinks. I'm currently looking to see how these could be saved in git. They currently just have the text of the file they link to e.g. https://github.com/geographika/OSGeoLive-doc/blob/gh-pages/6.0/_images/1spatial_sml1.jpg I didn't know about the current archive on the main site. So there is some duplication of effort, but adding them to a repo hopely has a long term benefit. It also triggered Angelos tracking do
Re: [OSGeoLive] All OSGeoLive Docs versions online
Excellent work Seth! Thanks for making the archive. Lets plan on setting the archive repo and the subdomain during the meeting tomorrow. Best, Angelos On 12/15/19 6:29 PM, Seth G wrote: Hi Cameron, Some answers in the email below. If you are able to find out how we can make a new https://github.com/OSGeo/OSGeoLive-archive repository and a new subdomain at osgeo.org I can hopefully take care of the rest. Seth -- web:http://geographika.co.uk twitter: @geographika On Sat, Dec 14, 2019, at 8:59 PM, Cameron Shorter wrote: Hi Seth, I was wondering why we don't have a symlink problem for images with the latest few releases? Looking at https://live.osgeo.org/de/index.html it appears that Vicky's new doc build script is smart enough to not create duplicate images for different languages (which as the case before). If you look at the old archive directory for say release 10.5, you see that we have duplicates of images. Eg: English version of docs points to: https://live.osgeo.org/archive/10.5/_images/osgeolive_menu6.png German version points to: https://live.osgeo.org/archive/10.5/_images/osgeolive_menu2.png To save space from images, Hamish Bowman wrote a script to create symlinks. I have a few ideas in moving forward: 0. To work out the broken symlink problem for images, you could: * Try and work out how to fix the symlink problem as you suggest. You might be able to find Hamish's old symlink generation script in the bin/ directory somewhere to help with that. (This sounds like a lot of work). * Copy the HTML from our archive web pages (which uses duplicate images). This will create a large repository due to duplicate images, which isn't perfect, but we will be rarely working on the archive repository, so it is probably acceptable. I've written a small Python script to change the symlinks to copies of the images. See https://github.com/geographika/OSGeoLive-doc/blob/gh-pages/scripts/symlinks.py It does create a larger repo, but probably simpler to manage across different OSs than symlinks in the long-term. All images should now be visible in the archive URL. 1. I think this historical archive of past releases you have created is really valuable. Thanks! 2. I think it should be findable from the main docs, probably as a small link at the bottom of https://live.osgeo.org : Prior releases and docs can be found in our archive/. This archive would be the jump page you have created. Sounds good. I guess we need to decide where the archive will be hosted (which URL/subdomain). Maybe https://archive.osgeo.org/ or Maybe https://livearchive.osgeo.org/ ? Who would be contact with regards to setting up a domain name? 3. While the archive jump page can be stored in our master docs, I don't think we should store each releases' archive in there. We can either keep it on a directory, as was previously done for prior releases. Or put into git, as you have done (which I like). I think that it deserves its own repository, something like OSGeoLive-doc-archive Currently the archive is in a branch so shouldn't increase size of git clone downloads etc. but moving to its own archive may make things clearer. Who would we contact with regards to creating a new repo at https://github.com/OSGeo/ ? 4. We should capture information about the latest doc release, and information about the archive in our build process documentation wiki: https://trac.osgeo.org/osgeolive/wiki. Would you like to update this? (You deserve the credit in the wiki history.) The build information is already linked to on https://trac.osgeo.org/osgeolive/wiki I've updated the link to the development build to point to OSGeoLive home page (development version). 5. Felicity has a bunch of pull requests for quickstarts. https://github.com/OSGeo/OSGeoLive-doc/pulls which are to be processed for the 13.1 doc release early next year. I'll try and get at least one of two reviewed within the week in order to check your publishing of the master docs pipeline. I don't think these pull requests have the Appveyor CI merged into them so they don't currently trigger builds. If we add a link to the archives we can see if this process works on a new pull request. Cheers, Cameron On 15/12/19 4:47 am, Seth G wrote: Thanks for the feedback and kind words Cameron! I got the docs from the ISOs - see https://github.com/geographika/OSGeoLive-doc/tree/gh-pages#extraction-process After further investigation the missing images are due to the files being symlinks. I'm currently looking to see how these could be saved in git. They currently just have the text of the file they link to e.g. https://github.com/geographika/OSGeoLive-doc/blob/gh-pages/6.0/_images/1spatial_sml1.jpg I didn't know about the current archive on the main site. So there is some duplication of effort, but adding them to a repo hopely has a long term benefit. It also triggered Angelos tracking down the missing full ISOs. The latest master docs are already published at
