Next steps to turn on https://coretoolchain.dev?

Next steps to turn on https://coretoolchain.dev?

[Carlos O'Donell]

Konstantin,

I pushed an early sphinx-quickstart to gitolite.coretoolchain.dev.

I've got a lot of the next pass of content ready.

How do we turn on https://coretoolchain.dev?

-- 
Cheers,
Carlos.

Re: Next steps to turn on https://coretoolchain.dev?

[Konstantin Ryabitsev]

On Wed, Feb 28, 2024 at 08:26:42AM -0500, Carlos O'Donell wrote:
> Konstantin,
> 
> I pushed an early sphinx-quickstart to gitolite.coretoolchain.dev.
> 
> I've got a lot of the next pass of content ready.
> 
> How do we turn on https://coretoolchain.dev?

I will enable that in the next few days. However, I thought the site was
cti.coretoolchain.dev, not toplevel?

-K

Re: Next steps to turn on https://coretoolchain.dev?

[Carlos O'Donell]

On 2/28/24 10:23, Konstantin Ryabitsev wrote:
> On Wed, Feb 28, 2024 at 08:26:42AM -0500, Carlos O'Donell wrote:
>> Konstantin,
>>
>> I pushed an early sphinx-quickstart to gitolite.coretoolchain.dev.
>>
>> I've got a lot of the next pass of content ready.
>>
>> How do we turn on https://coretoolchain.dev?
> 
> I will enable that in the next few days. However, I thought the site was
> cti.coretoolchain.dev, not toplevel?

Let me check the CTI TAC notes...
~~~
 * Consensus is around "coretoolchain.dev" for "cti.coretoolchain.dev" documentation.
~~~
You are correct, "cti.coretoolchain.dev" was the final decision.

Thank you!

-- 
Cheers,
Carlos.

Re: Next steps to turn on https://coretoolchain.dev?

[Konstantin Ryabitsev]

On Wed, Feb 28, 2024 at 06:19:42PM -0500, Carlos O'Donell wrote:
> > I will enable that in the next few days. However, I thought the site was
> > cti.coretoolchain.dev, not toplevel?
> 
> Let me check the CTI TAC notes...
> ~~~
>  * Consensus is around "coretoolchain.dev" for "cti.coretoolchain.dev" documentation.
> ~~~
> You are correct, "cti.coretoolchain.dev" was the final decision.

This site is now available:

https://cti.coretoolchain.dev/

It's not auto-building yet, but it's a small thing to enable tomorrow. There
are a few small tweaks to be done, too, like redirecting 80 to 443, but I ran
out of daylight today.

-K

Re: Next steps to turn on https://coretoolchain.dev?

[Carlos O'Donell]

On 2/29/24 19:25, Konstantin Ryabitsev wrote:
> On Wed, Feb 28, 2024 at 06:19:42PM -0500, Carlos O'Donell wrote:
>>> I will enable that in the next few days. However, I thought the site was
>>> cti.coretoolchain.dev, not toplevel?
>>
>> Let me check the CTI TAC notes...
>> ~~~
>>  * Consensus is around "coretoolchain.dev" for "cti.coretoolchain.dev" documentation.
>> ~~~
>> You are correct, "cti.coretoolchain.dev" was the final decision.
> 
> This site is now available:
> 
> https://cti.coretoolchain.dev/

Woot! Thank you very much for getting this live!

If Joseph, Siddhesh and David are happy with the content then I'll promote it more widely.

In particular I want to point Paul Eggert at this to answer his questions.

> It's not auto-building yet, but it's a small thing to enable tomorrow. There
> are a few small tweaks to be done, too, like redirecting 80 to 443, but I ran
> out of daylight today.

-- 
Cheers,
Carlos.

Re: Next steps to turn on https://coretoolchain.dev?

[Carlos O'Donell]

On 2/29/24 21:01, Carlos O'Donell wrote:
> On 2/29/24 19:25, Konstantin Ryabitsev wrote:
>> It's not auto-building yet, but it's a small thing to enable tomorrow. There
>> are a few small tweaks to be done, too, like redirecting 80 to 443, but I ran
>> out of daylight today.
 
I can confirm that the updates do go live almost immediately as the remote side reubilds the
HTML. Thank you for that! It means the edits I'm making should be visible to readers.

-- 
Cheers,
Carlos.

Re: Next steps to turn on https://coretoolchain.dev?

[Konstantin Ryabitsev]

On Wed, Mar 06, 2024 at 03:33:59PM -0500, Carlos O'Donell wrote:
> I can confirm that the updates do go live almost immediately as the remote side reubilds the
> HTML. Thank you for that! It means the edits I'm making should be visible to readers.

Right, I forgot to follow up about that. It's built on replication to a
different user (because we don't want to invoke a build script as the same
user who has access to all the backend repositories), so there is up to 30
seconds delay between push and when the site is rebuilt.

-K