You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stormcrawler.apache.org by Richard Zowalla <rz...@apache.org> on 2025/05/02 18:42:32 UTC
Website Updates -> Automatic Deployment
Hi all,
I have updated our Storm website to be build automatically via GitHub
actions on push to "main".
You have the possbility to either push to "main" and wait for a deploy
_or_ you create a branch in the site repo and do a staging deploy via a
manually triggered action. The website is than available via
https://storm.staged.apache.org/
That should make it easier to deal with the website (no need to install
ruby and stuff on your local machine ...)
Gruß
Richard
Re: Website Updates -> Automatic Deployment
Posted by Richard Zowalla <ri...@zowalla.com>.
Oh s*** :) you are right. Thanks, Dave.
For Stormcrawler we already have it :)
Am Freitag, dem 02.05.2025 um 11:48 -0700 schrieb Dave Fisher:
> Did you mean to send this to dev@storm.apache.org?
>
> > On May 2, 2025, at 11:42 AM, Richard Zowalla <rz...@apache.org>
> > wrote:
> >
> > Hi all,
> >
> > I have updated our Storm website to be build automatically via
> > GitHub
> > actions on push to "main".
> >
> > You have the possbility to either push to "main" and wait for a
> > deploy
> > _or_ you create a branch in the site repo and do a staging deploy
> > via a
> > manually triggered action. The website is than available via
> > https://storm.staged.apache.org/
> >
> > That should make it easier to deal with the website (no need to
> > install
> > ruby and stuff on your local machine ...)
> >
> > Gruß
> > Richard
>
Re: Website Updates -> Automatic Deployment
Posted by Dave Fisher <wa...@apache.org>.
Did you mean to send this to dev@storm.apache.org?
> On May 2, 2025, at 11:42 AM, Richard Zowalla <rz...@apache.org> wrote:
>
> Hi all,
>
> I have updated our Storm website to be build automatically via GitHub
> actions on push to "main".
>
> You have the possbility to either push to "main" and wait for a deploy
> _or_ you create a branch in the site repo and do a staging deploy via a
> manually triggered action. The website is than available via
> https://storm.staged.apache.org/
>
> That should make it easier to deal with the website (no need to install
> ruby and stuff on your local machine ...)
>
> Gruß
> Richard