From matti.picus at gmail.com Tue Feb 2 17:54:41 2021 From: matti.picus at gmail.com (Matti Picus) Date: Wed, 3 Feb 2021 00:54:41 +0200 Subject: [pypy-dev] moving blog posts to pypy.org Message-ID: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> An HTML attachment was scrubbed... URL: From hodgestar at gmail.com Wed Feb 3 01:48:43 2021 From: hodgestar at gmail.com (Simon Cross) Date: Wed, 3 Feb 2021 08:48:43 +0200 Subject: [pypy-dev] moving blog posts to pypy.org In-Reply-To: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> References: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> Message-ID: No specific thoughts, but this sounds like a good step and thank you for doing it. From anto.cuni at gmail.com Wed Feb 3 04:20:48 2021 From: anto.cuni at gmail.com (Antonio Cuni) Date: Wed, 3 Feb 2021 10:20:48 +0100 Subject: [pypy-dev] moving blog posts to pypy.org In-Reply-To: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> References: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> Message-ID: Hi Matti, +1 to everything for me. It sounds a big step forward, thank you for doing this. I think it would be nice to preserve the ability to comment, though. If the simplest way to do that is to move the repo to github, +1 for that as well. On Tue, Feb 2, 2021 at 11:55 PM Matti Picus wrote: > I imported the blog posts and comments to pypy/pypy.org on the blogposts > branch. If you want a preview, you can update to the branch, and run "make > build" which should create a nikola virtualenv, install the sidebar plugin, > build the site, and put a sidebar into the blog post pages. > > > The blogspot site served us well for 13 years, it is time to move on. > > The operative change will be that from now on blog posts become a merge > request to the pypy.org repo, using the nikola workflow: > > - nikola new_post > > - edit the post in RST or markdown or jupyter notebook or ... > > - add tags and a blurb > > - merge it to default > > > The repo has a CI job to build and push the site, so it is no longer > necessary to render locally and commit the pages to /public, they will be > rebuilt on a merge. > > > We may want to move this repo to github to get a nice preview in github > pages, and to use the utterances system for comments based on github issues. > > > Any thoughts? > > Matti > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matti.picus at gmail.com Sun Feb 28 03:51:58 2021 From: matti.picus at gmail.com (Matti Picus) Date: Sun, 28 Feb 2021 10:51:58 +0200 Subject: [pypy-dev] moving blog posts to pypy.org In-Reply-To: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> References: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> Message-ID: <63595332-b0f8-7b8b-5f3e-6b72750d69fa@gmail.com> On 2/3/21 12:54 AM, Matti Picus wrote: > > I imported the blog posts and comments to pypy/pypy.org on the > blogposts branch. If you want a preview, you can update to the branch, > and run "make build" which should create a nikola virtualenv, install > the sidebar plugin, build the site, and put a sidebar into the blog > post pages. > > > The blogspot site served us well for 13 years, it is time to move on. > > The operative change will be that from now on blog posts become a > merge request to the pypy.org repo, using the nikola workflow: > > - nikola new_post > > - edit the post in RST or markdown or jupyter notebook or ... > > - add tags and a blurb > > - merge it to default > > > The repo has a CI job to build and push the site, so it is no longer > necessary to render locally and commit the pages to /public, they will > be rebuilt on a merge. > > > We may want to move this repo to github to get a nice preview in > github pages, and to use the utterances system for comments based on > github issues. > > > Any thoughts? > > Matti > I opened a repo on https://github.com/pypy/pypy.org. It now completes the points at the end of my mail: preview for PRs via netlify, uses utterances for new blog posts. Please take a look at the deploy preview https://keen-mestorf-442210.netlify.app, especially the new Blog dropdown and links. Matti From matti.picus at gmail.com Sun Feb 28 05:37:42 2021 From: matti.picus at gmail.com (Matti Picus) Date: Sun, 28 Feb 2021 12:37:42 +0200 Subject: [pypy-dev] moving blog posts to pypy.org In-Reply-To: References: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> <63595332-b0f8-7b8b-5f3e-6b72750d69fa@gmail.com> Message-ID: <4293e020-0aea-ce82-8d82-5be35a19f00f@gmail.com> An HTML attachment was scrubbed... URL: From georges.racinet at octobus.net Sun Feb 28 06:09:07 2021 From: georges.racinet at octobus.net (Georges Racinet) Date: Sun, 28 Feb 2021 12:09:07 +0100 Subject: [pypy-dev] moving blog posts to pypy.org In-Reply-To: <4293e020-0aea-ce82-8d82-5be35a19f00f@gmail.com> References: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> <63595332-b0f8-7b8b-5f3e-6b72750d69fa@gmail.com> <4293e020-0aea-ce82-8d82-5be35a19f00f@gmail.com> Message-ID: <18c11b38-7ba3-c2ea-1f36-9b428e330c35@octobus.net> Hi there, On 2/28/21 11:37 AM, Matti Picus wrote: > > Heptapod does not support gitlab pages. > To be more precise, Heptapod, the software, does support GitLab Pages. But foss.heptapod.net, the instance where PyPY is hosted, does not. Basically it's a matter of GitLab pages being its own dynamic HTTPS virtual hosting system, which is hard to integrate with front load balancers and reverse proxies that want to do the same thing. We'll get to it some day, but we have lower hanging fruit to pick first. Best, -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics From hodgestar at gmail.com Sun Feb 28 07:17:48 2021 From: hodgestar at gmail.com (Simon Cross) Date: Sun, 28 Feb 2021 14:17:48 +0200 Subject: [pypy-dev] moving blog posts to pypy.org In-Reply-To: <63595332-b0f8-7b8b-5f3e-6b72750d69fa@gmail.com> References: <009345fb-f871-b2ff-5a48-8322dd9b91f1@gmail.com> <63595332-b0f8-7b8b-5f3e-6b72750d69fa@gmail.com> Message-ID: Thanks Matti, this looks great.