Listing some resource around codeberg page #34

defuneste commented 2026年01月01日 20:57:39 +01:00

I am not aware of tools that allow discussion, hence I am going to use an issue and probably edit it later. The goal is listing blog posts or other resources mentioning using codeberg for some R related stuff.

More generic advice from https://codeberg.org/ropensci (@ropensci): Code Hosting Options Beyond GitHub

To publish `pages on your domain: grebedoc.dev

Using codeberg page with Quarto:

• Quarto websites and Codeberg pages from @nxskok
  • part 1
  • part 2
• Migrating my Quarto site from GitHub to Codeberg from @ericrscott

I am not aware of tools that allow discussion, hence I am going to use an issue and probably edit it later. The goal is listing blog posts or other resources mentioning using codeberg for some R related stuff. More generic advice from https://codeberg.org/ropensci (@ropensci): [Code Hosting Options Beyond GitHub](https://ropensci.org/blog/2025/12/17/beyond-github/) To publish `pages on your domain: [grebedoc.dev](http://grebedoc.dev) ## Using codeberg page with Quarto: - Quarto websites and Codeberg pages from @nxskok - [part 1](https://blog.ritsokiguess.site/posts/quarto-codeberg/) - [part 2](https://blog.ritsokiguess.site/posts/quarto-codeberg-part-2/) - [Migrating my Quarto site from GitHub to Codeberg](https://ericrscott.com/posts/2025-09-20-migrating-to-codeberg/) from @ericrscott

defuneste commented 2026年01月17日 15:59:24 +01:00

I am also adding that discussion related to grebedoc.dev : Codeberg-e.V./Discussion#160 will see when we have documentation!

I am also adding that discussion related to grebedoc.dev : https://codeberg.org/Codeberg-e.V./Discussion/issues/160 will see when we have documentation!

whitequark commented 2026年01月27日 16:47:18 +01:00

grebedoc.dev already has documentation (it is on the domain itself) though; only Codeberg Pages is missing docs.

grebedoc.dev already has documentation (it is on the domain itself) though; only Codeberg Pages is missing docs.

defuneste commented 2026年02月10日 15:00:58 +01:00

Hi @whitequark yeah thanks a lot for the service, the documentation and the clarification!

To give you a bit of context R users are usually not "computer science people" and stuff like DNS, custom header and core web functionalities are not always fully understood (at-least that is the case for me! ). So experience like the one done with @nxskok are really valuable to us.

Hi @whitequark yeah thanks a lot for the service, the documentation and the clarification! To give you a bit of context R users are usually not "computer science people" and stuff like DNS, custom header and core web functionalities are not always fully understood (at-least that is the case for me! ). So experience like the one done with @nxskok are really valuable to us.

whitequark commented 2026年02月10日 15:09:18 +01:00

You're welcome! I now understand where the slow but steady trickle of academic deployments on grebedoc.dev come from.

To give you a bit of context R users are usually not "computer science people" and stuff like DNS, custom header and core web functionalities are not always fully understood (at-least that is the case for me! ). So experience like the one done with @nxskok are really valuable to us.

Yes, this makes perfect sense to me and I expected this. Without knowing the target audience it is difficult to write good documentation, due to a natural tendency to assume that others will know the same things you know (even if you correct for it, it will still bite you!) So I think @nxskok's guide is probably better than what I could have produced even if I tried due to that difference in context (e.g. the workflow of deploying from R Studio is completely foreign to me even if I can understand why it's used and how). Grebedoc does need some more verbose documentation but I think it's great that users are writing guides tailored to their needs, context, and environment.

While we're here, @nxskok, there's one thing I think your guide could improvement on: using an ALIAS pseudo-record in DNS instead of an A/AAAA pair. This is because, if I ever have to change IPs of grebedoc.dev (due to unforeseen circumstances, I wouldn't do this on purpose as it would be too disruptive), an ALIAS record would pick the changes up without manual intervention.

You're welcome! I now understand where the slow but steady trickle of academic deployments on grebedoc.dev come from. > To give you a bit of context R users are usually not "computer science people" and stuff like DNS, custom header and core web functionalities are not always fully understood (at-least that is the case for me! ). So experience like the one done with @nxskok are really valuable to us. Yes, this makes perfect sense to me and I expected this. Without knowing the target audience it is difficult to write good documentation, due to a natural tendency to assume that others will know the same things you know (even if you correct for it, it will still bite you!) So I think @nxskok's guide is probably better than what I could have produced even if I tried due to that difference in context (e.g. the workflow of deploying from R Studio is completely foreign to me even if I can understand why it's used and how). Grebedoc *does* need some more verbose documentation but I think it's great that users are writing guides tailored to their needs, context, and environment. While we're here, @nxskok, there's one thing I think your guide could improvement on: using an `ALIAS` pseudo-record in DNS instead of an `A`/`AAAA` pair. This is because, if I ever have to change IPs of grebedoc.dev (due to unforeseen circumstances, I wouldn't do this on purpose as it would be too disruptive), an `ALIAS` record would pick the changes up without manual intervention.

defuneste commented 2026年02月11日 01:58:56 +01:00

Rstudio is a really good IDE for R but sadly some of it functionalities and other parts of the R ecosystem had a strong focus on GitHub (see here and here as examples) and we are slowly trying to reevaluate and update our practices.

Rstudio is a really good IDE for R but sadly some of it functionalities and other parts of the R ecosystem had a strong focus on GitHub (see [here](https://usethis.r-lib.org/articles/git-credentials.html) and [here](https://quarto.org/docs/publishing/github-pages.html) as examples) and we are slowly trying to reevaluate and update our practices.

nxskok commented 2026年02月11日 22:44:13 +01:00

A/AAAA vs ALIAS is entirely fair. Because my CS is self-taught and because I had A/AAAA working with a modicum of understanding (IPv4 and IPv6), I didn't want to mess with it. I will need to have a play on my other domain to build some confidence myself that I can make it work.

A/AAAA vs ALIAS is entirely fair. Because my CS is self-taught and because I had A/AAAA working with a modicum of understanding (IPv4 and IPv6), I didn't want to mess with it. I will need to have a play on my other domain to build some confidence myself that I can make it work.

nxskok commented 2026年02月11日 22:46:25 +01:00

@defuneste wrote in #34 (comment):

Rstudio is a really good IDE for R but sadly some of it functionalities and other parts of the R ecosystem had a strong focus on GitHub (see here and here as examples) and we are slowly trying to reevaluate and update our practices.

for a long time (relatively speaking), github and a github pages workflow was what there was and what pretty much everybody was using, so I don't blame R Studio for developing things that worked with that.

@defuneste wrote in https://codeberg.org/r-codeberg/migration-guide/issues/34#issuecomment-10506826: > Rstudio is a really good IDE for R but sadly some of it functionalities and other parts of the R ecosystem had a strong focus on GitHub (see [here](https://usethis.r-lib.org/articles/git-credentials.html) and [here](https://quarto.org/docs/publishing/github-pages.html) as examples) and we are slowly trying to reevaluate and update our practices. for a long time (relatively speaking), github and a github pages workflow was what there was and what pretty much everybody was using, so I don't blame R Studio for developing things that worked with that.