#5973 New publishing source for budget.fp.o
Closed: Fixed 7 years ago Opened 7 years ago by bex.

The new site is generated pushed as HTML to https://pagure.io/fedora-budget-site

The stg branch should go to stage and the prod branch should go to production.

You can preview the site at http://209.132.179.16:3000/

There are some display challenges, but I'd like to get this at least in stage as soon as possible.

Image update: https://pagure.io/design/issue/509
Design/CSS Assistance: https://pagure.io/fedora-bootstrap/issue/6
Websites Acknowledgement: https://pagure.io/fedora-websites/issue/651


ok, you are live in stg now...

can you take a look and if it looks ok, I can push to production?

https://budget.stg.fedoraproject.org/

:currency_exchange:

@ryanlerch can you help me figure out why the social media icons aren't working?

You are missing probably font-awesome, or the path is wrong.

You are missing probably font-awesome, or the path is wrong.

I figured it was font-awesome. I just didn't initially see where that was included incorrectly.

ok, you are live in stg now...
can you take a look and if it looks ok, I can push to production?
https://budget.stg.fedoraproject.org/
💱

@kevin What is the update process? When I push something to the stg branch how does the stage site get updated? To push to production do I just push to the prod branch? I want to make sure I know the process. Also, do you want me to push html as new commits or to keep the repo at a single commit per branch?

As you can see above we are troubleshooting a font-awesome issues (generous use of "we" I know). I am actually ok with going live with that borked. prod is updated.

@kevin What is the update process? When I push something to the stg branch how does the stage site get updated? To push to production do I just push to the prod branch? I want to make sure I know the process.

There is a script on our internal sundries01 box (the same script that builds the fedora-websites) that runs once an hour and will pull from https://pagure.io/fedora-budget-site. Then, also once an hour (at :25 after I think) all our proxies rsync this content to themselves. Then, end users get that static content from the "closest" proxies to them.

To update staging, just push commits to the stg branch, to update prod just push to the prod branch.

Also, do you want me to push html as new commits or to keep the repo at a single commit per branch?

New commits are fine and good.

As you can see above we are troubleshooting a font-awesome issues (generous use of "we" I know). I am actually ok with going live with that borked. prod is updated.

ok. Will go update prod now...

ok. prod is now live as well.

Let us know if you need anything further.

:cake:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Adding a comment here that it would be awesome if we could more "on-demand" or more frequent publishing. Conversation about that can continue in #5747 as it is related.

https://pagure.io/fedora-infrastructure/issue/5747

Log in to comment on this ticket.

Metadata