rakudo / rakudo.org Goto Github PK

View Code? Open in Web Editor NEW

8.0 8.0 18.0 721 KB

Code for rakudo.org website

Home Page: https://rakudo.org/

License: Artistic License 2.0

Perl 23.36% Shell 0.52% JavaScript 46.90% CSS 12.18% Raku 0.82% SCSS 16.22%

raku rakudo

rakudo.org's People

Contributors

Stargazers

Watchers

Forkers

interlab kensanata ryn1x jstuder-gh patrickbkr rba mryan nxadm ciavash titsuki juanfra684 xliff jdv m-dango seanpm2001 2colours tbrowder librasteve

rakudo.org's Issues

No explanation of running rakudo when installed by package manager on linux

I installed rakudo by using apt on Debian 10. There is no explanation of how to run it. A short type raku or try perl6 might be useful.

https://rakudo.org/dl/ is 404

>$ curl -s https://rakudo.org/dl/star/
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>403 Forbidden</title>
<style type="text/css"><!--
body { background-color: white; color: black; font-family: 'Comic Sans MS', 'Chalkboard SE', 'Comic Neue', sans-serif; }
hr { border: 0; border-bottom: 1px dashed; }
@media (prefers-color-scheme: dark) {
body { background-color: #1E1F21; color: #EEEFF1; }
a { color: #BAD7FF; }
}
--></style>
</head>
<body>
<h1>403 Forbidden</h1>
<hr>
<address>OpenBSD httpd</address>
</body>
</html>

>$ curl -s https://rakudo.org/dl/
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <meta property="og:image"
      content="https://rakudo.org/asset/logo.png">
    <meta name="twitter:image"
      content="https://rakudo.org/asset/logo.png">
    <title>404 - Page Not Found
      - Rakudo Compiler for Raku Programming Language</title>
    <link href="/asset/f74a9e05c3/app.css" rel="stylesheet">
    <link href="/favicon.ico" rel="shortcut icon" type="image/x-icon">
  </head>



  <body>
    <div class="cover-container d-flex h-100 p-3 mx-auto flex-column">
      <header class="masthead mb-auto">
        <div class="inner">
          <h3 class="masthead-brand">
            <a href="/"><img
              src="/asset/pics/logo-inverse.png" alt=""></a>
          </h3>
          <nav class="nav nav-masthead justify-content-center">
            <a class="nav-link"
              href="/news">News</a>
            <a class="nav-link"
              href="/downloads">Downloads</a>
            <a class="nav-link"
              href="/docs">Docs</a>
            <a class="nav-link"
              href="/star">Star Bundle</a>
            <a class="nav-link"
              href="/issue-trackers">Issue Tracker</a>
            <a class="nav-link"
              href="/community">Community</a>
          </nav>
        </div>

      </header>
      <div id="content"

      >
<h2 class="h1">404 - Page Not Found</h2>
<p>The page you tried to access does not exist.</p>
</div>

      <footer class="mastfoot mt-auto">
        <div class="inner">
          <p><a href="https://github.com/rakudo/rakudo">rakudo/rakudo</a>
            | <a href="https://twitter.com/search?q=%23rakulang"
              >#rakulang</a>
            | <a href="https://kiwiirc.com/client/irc.libera.chat/#raku"
              >#raku</a>
            | <a href="/feed">News RSS</a>
          </p>
        </div>
      </footer>
    </div>
    <script src="/asset/a69a4689ef/app.js"></script>
  </body>
</html>

https://rakudo.org/files/star/source instructions expansion non-obvious

I didn't find it very obvious that I had to click on the sections (eg. Debian/Ubuntu/WSL) in order to expand out the instructions and suspect some others might miss this too.

I'd suggest making this more obvious by adding something like an "expander" image (triangle or arrow) with the expanded content indented slightly and the "expander" image triangle rotating on clicking (basically similar to how wikipedia content is displayed on mobile).

Or just using a "mouseover" to expand content when the link is hovered over. Or something else like this.

404 error

https://rakudo.org/dl/rakudo

I got a 404 error from the fall-back server today.

rakudo.org is not showing the new uploaded 2023.11 Star release

Hi.

I've copied over the new 2023.11 Rakudo Star release files to rakudo.org/star.
I also logged in there and ran update-rakudo.org.sh.
Still the new release and files are neither shown on https://rakudo.org/star nor https://rakudo.org/downloads.

rakudo.org@lavm-perl6infra-1:~$ ls -la public_html/downloads/star/*2023*11*
-rw-r--r-- 1 rakudo.org rakudo.org 30218811 Nov 22 18:54 public_html/downloads/star/rakudo-star-2023.11-01.tar.gz
-rw-r--r-- 1 rakudo.org rakudo.org      228 Nov 22 18:54 public_html/downloads/star/rakudo-star-2023.11-01.tar.gz.asc
-rw-r--r-- 1 rakudo.org rakudo.org      922 Nov 22 18:54 public_html/downloads/star/rakudo-star-2023.11-01.tar.gz.checksums.txt
-rw-r--r-- 1 rakudo.org rakudo.org 38425454 Nov 22 18:54 public_html/downloads/star/rakudo-star-2023.11-01-win-x86_64-msvc.msi
-rw-r--r-- 1 rakudo.org rakudo.org      228 Nov 22 18:54 public_html/downloads/star/rakudo-star-2023.11-01-win-x86_64-msvc.msi.asc
-rw-r--r-- 1 rakudo.org rakudo.org      897 Nov 22 18:54 public_html/downloads/star/rakudo-star-2023.11-01-win-x86_64-msvc.msi.checksums.txt

Can someone look into rakudo.org and check why the website is not showing updated releases anymore? Thanks!

https://rakudo.org/news not showing latest release

Need an entry for 2020.05.01

https://rakudo.org/files/ has all star options in light blue on android phone

https://rakudo.org/files/ has all star options in highlighted in light blue (with the yellow text line) on an android phone (chrome) wheres I'd expect the source option to be selected only.

I find it really complicated and confusing for beginners to install Raku on the system.

The website (https://rakudo.org/) raises false expectations in the download section.
For example, it says "Archives and installers contain a precompiled Rakudo and the Zef module manager."

But this is not true. The zef module manager is not included in the binary releases. Or do I understand something wrong?

In the Rakudo Star Bundle zef seems to be included. But aren't the Star Bundles a bit outdated and don't include the latest versions of the rakudo VM?
I had the Star Bundle installed for Windows only.

I then installed zef (and raku) under Ubuntu (WSL) via this Gihub page.
https://github.com/ugexe/zef
I found the project page via google. Can't this be included in the description for the https://rakudo.org/ website?

But even there the description for the installation is a bit faulty.
Instead of the following commands:
$ git clone https://github.com/ugexe/zef.git
$ cd zef
$ raku -I. bin/zef install .

I had to use the following command to install zef with raku.
$ raku -Ilib bin/zef install .

Can't you make it all a little more understandable. I think many other beginners will give up faster.

readme links to old infrastructure docs

p6c.org has been gone over a year. Need to inline or link to updated docs.

https://rakudo.org/files/rakudo

This page gives a 500 error.

morbo doesn't work locally

When I try to run morbo locally, I get this failure:

Can't load application from file "/Volumes/BUKKIT/Users/coke/sandbox/rakudo.org/app.pl": run(/bin/sass) failed: No such file or directory at /Volumes/BUKKIT/Users/coke/perl5/perlbrew/perls/perl-5.28.0/lib/site_perl/5.28.0/Mojolicious/Plugin/AssetPack/Pipe.pm line 27.
 ($?=-1, $!=2, PATH=/Volumes/BUKKIT/Users/coke/perl5/perlbrew/bin:/Volumes/BUKKIT/Users/coke/perl5/perlbrew/perls/default/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Volumes/BUKKIT/Users/coke/bin:/Volumes/BUKKIT/Users/coke/usr/bin:/Volumes/BUKKIT/Users/coke/bird/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Volumes/BUKKIT/Users/coke/sandbox/scripts:/Users/coke/sandbox/util/bin:/Volumes/BUKKIT/Users/coke/p6/bin:/Volumes/BUKKIT/Users/coke/p6/share/perl6/site/bin) at /Volumes/BUKKIT/Users/coke/perl5/perlbrew/perls/perl-5.28.0/lib/site_perl/5.28.0/Mojolicious/Plugin/AssetPack/Pipe.pm line 30.
Compilation failed in require at (eval 95) line 1.

Windows from-sauce instructions aren't exact

The prerequisites section should list the need for a .tar.gz archive unpacker, like 7-zip
The unpacking step should mention that 7-zip requires two stages of unpacking, because first it only unpacks the .gz portion, leaving the user with just the .tar file, which also needs to be unpacked before the rest of the instructions can be executed.
The shown command to run after unpacking is cd C:\Temp\rakudo-star yet, the unpacked star dir has a version number in it
During installation (possibly during spectest) firewall warning comes up (RT#130358). It's a bit scary-looking when totally unexpected, so might be nice to mention its possibility in the install guide.

It's also a bit convoluted: Chrome downloaded the file into my Downloads folder and I unpacked the stuff there, but now—per instructions—I need to figure out how to move that directory to \Temp. Would running the build in Downloads dir work? Would it still work in dirs that have spaces in them?

link to collection of modules is broken

The 'collection of modules' link on this page: https://rakudo.org/star goes to a github 404 page.

Upgrade to new Mojolicious

New major release of Mojolicious is out. We need to upgrade to it and de-bitrot anything that breaks.

500 - server error at https://rakudo.org/latest/star/source

went to Linux link under https://github.com/rakudo/star#get-rakudo-star

browser: Firefox 75.0 (64-bit)

move up visibility of rakudo-pkg

moving thread to here from PR 98

@nxadm says:
While I share the worries about outdated packages, I don't think that compiling the compiler --what rakubrew does-- is what programmers new to the language expect or, more importantly, will accept.

@bazzaar says:
I agree with @nxadm, and it's a point I specifically raised in my 'more Focus' issue to the Steering Council.

Raku/Raku-Steering-Council#56 (comment)

The general advice for new users to use their Linux distro's package installer is sound enough, so long as the additional step of pointing the package installer to a well-trusted repo which supplies an up-to-date version of Rakudo is taken.

nxadm's excellent rakudo-pkg repo, details all the instructions for users to add the repo to the list of package repositories on their system.

I don't see why this seems such a difficult mechanism to advertise. Other specialised software products follow such a route. Users don't want software that is 9-months out of date, so they will clamour for the repo to be added if they work for a larger organisation. Me now retired, it was a 5 minute job to add the repo in OpenSuSe Leap. Been using the rakudo-pkg service now for maybe 5years, it installs the software in /opt, and there's a script to run to set it up so that a user can install additional modules (distributions) in a user-specified directory on their $PATH. Pretty straightforward. The latest release of Rakudo is installed by the distro's package manager automatically from then on, as soon as it appears on the rakudo-pkg repo site.

I could draw an analogy with the Comma situation. An excellent 3rd party initiative, well maintained, and providing a reliable up-to-date service, yet sadly not given the backing it deserves on the Raku/Rakudo web site.

As I alluded to in the 'more Focus' thread, the Rakudo download options page is very confusing for new users, IMHO.

@librasteve says:
@nxadm, @bazzaar - yep I agree with all that, let me try rakudo-pkg myself and then revert with a proposal
@raiph - yep that's good, will adapt text to your version - thanks!

@nxadm, @bazzaar - I just tried the instructions at https://cloudsmith.io/~nxadm-pkgs/repos/rakudo-pkg/setup/#formats-deb and the vanilla AWS ubuntu image

the curl script worked fine

BUT, there are two issues:

nowhere does it say what to do after you setup the rakudo-pkg repo

when I do go sudo apt-get install rakudo, I get

ubuntu@ip-172-31-31-39:~$ raku -v
Welcome to Rakudo™ v2022.02.
Implementing the Raku® Programming Language v6.d.
Built on MoarVM version 2022.02.
Please put me straight if I have misconstrued anything.

Therefore, while I agree in principle that rakudo.org should promote actively maintained repo such as rakudo-pkg, I would look to you to resolve these two issues before we move up its visibility please.

In the meantime, I will fix @raiph s comment and resubmit this PR, and move this "where to place rakudo-pkg" thread to an Issue.
I have in mind that rakudo-pkg and rakubrew would have "equal billing" at the top of the Linux tab if we can get this resolved.

https://rakudo.org/files/star/source libssl listed as dependency.

Maybe nitpicking on my part but technically neither libssl/libssl-dev nor git are needed as a build or runtime dependencies for Rakudo Star.

But probably anyone building from source on Linux is likely to have to add openssl quite quickly so that dependency is probably useful to them. zef probably installs some modules without git but really its likely to be useful anyway.

404 on https://rakudo.org/star/windows

on https://rakudo.org/star/windows :
pre-built 3rd party packages and both build from source links are ending at "404 - Page Not Found" :(

Updating the news site to show rakudo builds as well

Feature request:

On the news site should be the rakudo builds visible as well. Maybe linked to the release information on github. E.g. https://github.com/rakudo/rakudo/releases/tag/2020.01

Release Checklist

Build.PL
app conf

Binaries model

Suggested edits to rakudo.org

I really like the new website, however I've tried to take a subjective/objective look at it from a user perspective, and I have some comments as listed below:

Rationale : purely to make the website as user-friendly and internally consistent as possible, whilst pushing Rakudo Star to the fore, and limiting mentions of the "Compiler".

The suggested edits should be viewed as a whole, hopefully together they would prove beneficial.

I'll work through the pages in order, it'll help the reader to understand comments, if the webpages are visible at the same time.

Menu Bar

Insert "Rakudo Perl6" after the japanese symbol in the menu bar, that way it's in the heading of each page.
Change "Posts" to "News", "Files" to "Download", "Bugs" to "Feedback", "People" to "Community" - thereby instilling purpose to web page clicks, and ensuring consistency with page body text.

Home page body

Remove the word "Compiler" - The main purpose of the site is to make available Rakudo Star. (But no need to use "Rakudo Star" until the Files [Downloads] page). "Rakudo Perl 6" is fine for the Home Page body.

Posts (News) page body

Change "Posts" to "News" in page body - news is what it is, not everyone knows what "Posts" is.
In the release announcement docs, the first paragraph has a link that takes the reader to the old files/downloads page, maybe change the link in those docs so the reader stays in the new webpages.

Files (Downloads) page body

Title already consistent with [edited] menu bar.
Change "Rakudo Star Collection" title to "Rakudo (Star Edition)" - simply because "collection" seems "wooly", need something more "official/punchy", the brackets provide the link between Rakudo and Star, to me at least.
Change "a collection of modules from the Perl6 ecosystem" to a "specific set of ...", that way the reader is not under any illusion he/she might be able to do the selecting of modules for Star.
Compiler Only Installation box : use the phrase "Install the most up-to-date components" or such like.
Compiler Only Installation box : "View Options" button, at a different level, and inconsistent size, it ought to be aligned and consistent with the "pre-built packages" button.
Add Feature : on a level with the "Downloads" title, across the page, insert a counter till the next Rakudo Star release, why? because I'd be slightly disappointed to install Perl6 and then find I could have waited a day. Something along the lines of "next official Rakudo Star release [20##.##] - (2 months [or] 3 weeks [or] 5 days) from now".

Docs page body

To be honest, the "text file"-like layout of the Documentation section, spoils the otherwise excellent look of the pages. It's a bit wordy, and I want to emphasise Rakudo Star and Perl6 documentation, so here goes :

1a. First sentence should point to Perl6 docs
1b. Second sentence should be "Rakudo Compiler-specific docs .. link"
1c. That's it
1d. words about #IRC channel - it's on the People (Community) page already

Bugs (Feedback) page body

Change "Bugs" title to "Feedback" in page body - cos it's not just bugs we're reporting

People (Community) page body

Change "People" title to "Community" in page body - cos "People" sounds like I should be getting a list of the folks who have built Rakudo / Perl6, "Community" gives me a sense that I'm involved too.
The "#Perl6 IRC" button should spawn another tab in the browser, rather than taking me away from the rakudo.org site

Anyhow, that's my 6pennysworth. Like I say, this is purely meant to help the overall Perl6 effort.

bazzaar

link to open tickets in this website

The issue tracker takes you immediately to open a new ticket. It should instead take you to just .../issues, so you can search first.

Accordeon knobs are misrendered on Firefox

They're meant to be to the left of titles; not under them

sometimes https://rakudo.org/dl/rakudo does not include version 2023.11

https://github.com/Raku/setup-raku is fetching the latest binary URLs of Raku from https://rakudo.org/dl/rakudo.

However, it appears that sometimes https://rakudo.org/dl/rakudo returns a JSON that does not include version 2023.11 binary URLs. As a result, setup-raku occasionally identifies version 2023.10 as the latest.

From my investigation, https://rakudo.org/dl/rakudo typically returns a response with:

Last-Modified: Mon, 27 Nov 2023 02:27:46 GMT  // today

But occasionally, it returns an older response with:

Last-Modified: Tue, 21 Nov 2023 19:20:12 GMT  // some time in the past

During these times, it seems that version 2023.11 binary URLs are not included.

I would like to request a check to ensure that https://rakudo.org/dl/rakudo is functioning correctly.

Compiler-only build instructions build in a version-specific dir

The idea was the instructions would build in ~/rakudo/, but they actually build in ~/rakudo/rakudo-*/.

Also, is there a point in curling and untarring an archive rather than just git-ting from a repo (and doing git checkout $(git describe --abbrev=0 --tags) to checkout last release) , since NQP/MoarVM are fetched from a repo anyway?

SSL cert error

unzip rakudo-moar-2020.02.1-01-win-x86_64.zip exits with non zero code

(Sorry if this is not the right place to report this kind of issues)

unzip https://rakudo.org/dl/rakudo/rakudo-moar-2020.02.1-01-win-x86_64.zip emits a warning and exits with non-zero code 1.

❯ wget -q  https://rakudo.org/dl/rakudo/rakudo-moar-2020.02.1-01-win-x86_64.zip

❯ unzip -q rakudo-moar-2020.02.1-01-win-x86_64.zip
warning:  rakudo-moar-2020.02.1-01-win-x86_64.zip appears to use backslashes as path separators

❯ echo $?
1

Note that, even in windows OS and powershell environment,
unzip rakudo-moar-2020.02.1-01-win-x86_64.zip emits a warning and exits with non-zero code.

Rakudo upgrade impossible

Hi,

I tried to upgrade my Rakudo* install, but got the following error on the HTTP server:

500 - Server Error

This shouldn't happen. Please report this problem, explaining what you were trying to do when it occured.
Backup-server running

Currently, rakudo.org is being served off of a fall-back server because the network the original server is on is unreachable.

We expect the original server to be available again on the 22nd or 23rd of april 2019.

It is very possible that you're getting the 404 error because the fall-back server is not set up like the original server.

Cheers,
Laurent R. ([email protected]).

Cards should have identical height (maybe)

See this screenshot:

I think it should be like this:

Move this repo to Raku group

Likely would have to coordinate with a site infrastructure update to pull from the new remote (even though a redirect will be available for a while)

All the new "Downloads" => "Verifying" additions end in a "404 - Page Not Found"

seems like #78 doesn't work as is should... maybe rakudo.org was never visited / reviewed after the change was implemented?

@patrickbkr - I've no clue about the Perl Webframework, hosing rakudo.org. So can you please check end fix? Thanks

https://rakudo.org/star/source links to 404 https://rakudo.org/star/issue-trackers

Tested on Chrome 80.0.3987.149 (Official Build) snap (64-bit) on Ubuntu 18.04 x64

Repro:

Visit https://rakudo.org/star/source
Click the "Issue tracker" link at the top of the page

Expected: issue-tracker list

Observed: 404 - Page Not Found. The URL is https://rakudo.org/star/issue-trackers, which does not exist. https://rakudo.org/issue-trackers does exist.

Thanks!

Add link to RSS feed

Blog posts have an RSS feed at /feed endpoint, but that's not advertised anywhere.

#rakulang twitter tag

Suggestion: add a footer element that links to twitter and #rakulang

/issue-trackers links to https://alerts.perl6.org/ which is broken

The page /issue-trackers links to https://alerts.perl6.org/ in the text We maintain alerts.perl6.org service where we publish information on critical issues.

alerts.perl6.org first gave me a certificate warning (the certificate was for a completely different site). It's now a 502 error from nginx

It's not clear to me whether that site is supposed to work, whether it's now supposed to be a redirect to something on raku.org, or whether the link and text should be removed. Hence I don't know what fix to suggest.

Should decommission all the /rt/ aliases

... since we don't use rt anymore.

Could replace them all with a link to github issues for rakudo

Files page does not automatically show latest release

Basically, this change needs to be done automatically: e6e7f9c driven by the same system that knows what binary to serve for the latest release

moarvm fatal: not in a git directory (Rakudo.org instructions change request)

get an error on the make command on macOS Monterey
I propose to add the line noted below to the build from source instructions

The exact steps required may differ, depending on your operating system:

mkdir ~/rakudo && cd $_
git init <====== this fixes the error
curl -LJO https://rakudo.org/latest/rakudo/src
tar -xvzf rakudo-.tar.gz
cd rakudo-

perl Configure.pl --backend=moar --gen-moar
make <====== here

# If you wish, you can run the tests # Depending on your machine, they could take over half an hour to run
make test
make spectest

make install

echo "export PATH=$(pwd)/install/bin:$(pwd)/install/share/perl6/site/bin:$PATH"
>> ~/.bashrc
source ~/.bashrc

rakudo.org website install from source instruction broken

This page:

https://rakudo.org/star/source

States:

echo "export PATH=$(pwd)/bin/:$(pwd)/share/perl6/site/bin:$(pwd)/share/perl6/vendor/bin:$(pwd)/share/perl6/core/bin:\$PATH" >> ~/.bashrc

But:
$(pwd)/bin/: <= this has a TRAILING SLASH
That gives this:
which raku => /root/rakudo/bin//raku <= this has TWO SLASHES

May trip up unsuspecting users...

On a related note, when using Dockerfile one is in /bin/sh and this seems to choke on mkdir ~/rakudo && cd $_ so perhaps mkdir ~/rakudo && cd ~/rakudo would be more helpful

Rakudo.org is down.

Rakudo org

Shouldn't this repo be under the rakudo org (https://github.com/rakudo) instead of the perl6 org?

If not please close this ticket.

https://rakudo.org/bugs is 404

README.md in https://rakudo.org/dl/rakudo/rakudo-moar-2020.02.1-01-win-x86_64.zip says

Reporting bugs
==============

See https://rakudo.org/bugs

but, https://rakudo.org/bugs is 404

The binary download's top-level README needs specific OS info

The README should identify the OS, release date, and other data pertinent to finding the original binary bundle. Something like:

$ cat README
Source: https://github.com/rakudo/dl/rakudo/rakudo-moar-2023.09-01-linux-x86_64-gcc.tar.gz

Е500 on the download page

I'm excited about perl6 and I'm trying to install Rakudo, though I seem to be unable to get it on my computer.

The download button for Rakudo for Linux on http://rakudo.perl6.org/files leads to http://rakudo.perl6.org/latest/star/source, which gives Error 500 and asks to report the behaviour here. This is what I've been getting for the last few days.

The instructions to install from source on http://perl6.org/downloads/ make use of wget with http://rakudo.perl6.org/downloads/star/rakudo-star-2019.03.tar.gz as an address, which gives Error 404.

Are there some official mirrors from which I could get the tarball? I'm thinking of building directly from the rakudo github repo, though I'm unsure of which branch to use. I'd love to get any hints of this!