OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Python-Dev] Get a running instance of the doc for a PR.


On 11/05, Chris Angelico wrote:
>On Mon, Nov 5, 2018 at 2:33 AM Stephane Wirtel <stephane at wirtel.be> wrote:
>>
>> On 11/05, Chris Angelico wrote:
>> >On Mon, Nov 5, 2018 at 2:11 AM Julien Palard via Python-Dev
>> ><python-dev at python.org> wrote:
>> >>
>> >> Considering feedback from Ned, what about building this as an independent service? We don't really need to interface with python.org at all, we just need some hardware, a domain, some code to interface with github API and... to start it's probably enough? It would be a usefull POC.
>> >>
>> >
>> >After running 'make html', the build directory is the entire site as a
>> >set of static files, right? Maybe the easiest solution is to tie in
>> >with GitHub Pages. I already have a script that will push a directory
>> >up as the gh-pages branch of the current repo; it'd just need a tweak
>> >so it can push to a specific repo, which you could create on GitHub
>> >for the purpose. Not 100% automatic, but also not too difficult to
>> >automate, if needed.
>> >
>> >https://github.com/Rosuav/shed/blob/master/git-deploy
>>
>> Nice idea, but I am not for that.
>>
>> 1. We will populate the git repository with a lot of gh-pages branches
>> and I am not for this solution
>> 2. This static doc is just temporary, once merged, we have to remove the
>> link and the content on the server, with the gh-pages, that will be a
>> commit where we drop the content, but it's a commit and we will consume
>> the storage of github.
>> 3. 1 repo has only one gh-pages, in our case, we need to have a lot of
>> gh-pages for a repo.
>>
>
>Yeah, understood. I was thinking of having the individual patch
>authors create temporary GitHub repositories to push to. It'd be an
>optional step; if you want to show people a preview of your PR, just
>create a repository and push to it (using a script something like
>that). That way, you don't have to worry about malicious content
>(since it'll be hosted under the author's name - I'm sure GitHub have
>measures in place to deal with that, and it wouldn't be Python.org's
>problem), nor having lots of gh-pages branches sitting around (they'd
>be the responsibility of the author).
>
>> But thank you for your idea.
>
>No probs, and I don't mind if it's not adopted. Just wanted to put it out there.
In fact, I was interested by your solution because we avoid the
maintenance of the server, but in our case, we would host many
Docs/build/html. 

Thanks again
>
>ChrisA
>_______________________________________________
>Python-Dev mailing list
>Python-Dev at python.org
>https://mail.python.org/mailman/listinfo/python-dev
>Unsubscribe: https://mail.python.org/mailman/options/python-dev/stephane%40wirtel.be

-- 
St?phane Wirtel - https://wirtel.be - @matrixise