quarkus.io is now powered by Quarkus - what you need to do

[Holly Cummins]

Hi all, 

I’ve just pushed the button to switch quarkus.io from being a Jekyll site to a Roq site. That means it’s running on Quarkus. 🎉 There’s a community call about the change if you’re curious about the context: https://github.com/quarkusio/quarkus/discussions/55599

What do I need to do? 

Not much, hopefully! The ./serve.sh and ./serve-no-guides.sh scripts should continue working. You will need to have a JVM on your system, but you don’t need to install anything else. You can continue using the scripts, or you can also just run quarkus dev for local development. It should be a lot snappier than local development with Jekyll used to be.

If you were running Jekyll in a container, switch to using the scripts. 

I don’t make website changes, is there any action for me? 

We do need everyone’s eyeballs to spot issues. The external site is supposed to be exactly the same as it was before. If you spot any problems or changes in the site, please raise an issue or let me know. Before doing the move we wrapped everything in lots of tests, but it’s a complex site with thousands of pages, so it’s possible something snuck through both the tests and the manual checks

I do make website changes and I had a PR in progress, and now 40,000 files changed under me and I have the world’s worse merge conflict

Don’t worry, there’s an easy recovery path. 

Option 1: Manual migration for small changes

If you were just working on a blog or something else simple, a rebase will be ok, but your content will be orphaned in the old directory. Copy it from _posts to content/posts/. Assets would move from assets to public/assets/.

Option 2: Fully automated full conversion

If you had bigger changes, or if you can’t be bothered to try and figure out what to copy where, don’t try and do a normal rebase; the experience will be awful.  Instead, you can re-run the conversion process locally on your local Jekyll site. This should be reliable and straightforward, but it will take about twenty minutes for the script to run. 

1. Back up your branch.
2. Make sure your git knows about recent changes: git fetch upstream
3. Make sure all your changes are ‘loose’, rather than baked into commits: git reset 4c68cd4f439cf80215dff66742f191875543474e (this is resetting against a version of the site just before the conversion)
4. Convert, using Holly’s special haq-it script. Start in a temporary directory  

5. (

     git clone https://github.com/holly-cummins/quarkus-roq.git
     cd quarkus-roq
     git checkout wip/full-migration
     
     # 2. Build migration tools
     cd migration
     mvn clean install -DskipTests
   )
   
   # 3. Run migration
   ./quarkus-roq/migration/haq-it <path to your quarkusio repo>
   
   

6. Now you can run quarkus dev to check your work
7. Finally, you can rebase onto upstream main, and there shouldn't be any conflicts: git rebase upstream main

These instructions are also on the conversion PR: https://github.com/quarkusio/quarkusio.github.io/pull/2683

Known issues

I still need to merge PRs which remove references to Jekyll on our site, update the readmes and other docs, and fix some guides links just for dev mode. I want to send this email as soon as possible so I didn’t wait for those PRs to merge.

Best wishes, 

Holly

--
Holly Cummins
Partner Engineer, Senior Principal Quarkus Software Engineer, Sustainability Architect, Java Champion
Red Hat 

[Sergey Beryozkin]

Congratulations Holly, Andy and everyone else who was involved

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/94580FEA-EEA7-42DE-809F-A8B6748563E4%40redhat.com.

[Bruno Baptista]

Congrats!

It's just me or the site now feels waaaaay faster...

Cheers 

Bruno

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/94580FEA-EEA7-42DE-809F-A8B6748563E4%40redhat.com.

--

Bruno Baptista

@brunobat.bsky.social

[Georgios Andrianakis]

Excellent work folks!

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CADgv5WgCmo_oEW1SuXmQE38m%3DbDR2M9dBNSwQ47V36%3DQ5CxERg%40mail.gmail.com.

[Julien Ponge]

Awesome!

<redhat.png>

[James Perkins]

Nice work all!

James R. Perkins

Principal Software Engineer

[clement escoffier]

Awesome! 

What a journey from… :

Clement

<redhat.png>

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/94580FEA-EEA7-42DE-809F-A8B6748563E4%40redhat.com.

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CADGwLpixaHvdhg%3D3OecERgarORyj%3DrMc6yM9H86B9pJ4EKBSFg%40mail.gmail.com.

[Martin Bartos]

Nice work!

JFYI, the guide titles seem broken. 

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/E7CB6C00-4C3B-4D43-8D0C-C6D5F0F373C2%40gmail.com.