GratefulGamer9398233 wrote:

(#637)
Also, show me he file that contains the loading messages, I want to see for myself

AmpElectrecuted wrote:

GratefulGamer9398233 wrote:

(#637)
Also, show me he file that contains the loading messages, I want to see for myself

line 48 of loader.jsx

AmpElectrecuted wrote:

I'm re-deploying the website, hopefully it should work

50-scratch-tabs, rebuild your mirror please

50_scratch_tabs wrote:

(#644)

AmpElectrecuted wrote:

I'm re-deploying the website, hopefully it should work

50-scratch-tabs, rebuild your mirror please

Still isn't working

Where is the codeberg workflow? Does it use npm i or ci?

Amp, try rebuilding now. I rebuilt the package-lock, which will matter if you use npm i instead of npm ci

Also could u pls invite me to the codeberg organization? (Username 50_scratch_tabs) I'll still commit primarily from github but this will help for stuff like pages.

My mirror works.

play sound (meow v) until done with restart [off v] :: sound
start sound (meow v) with restart [on v] :: sound

AmpElectrecuted wrote:

(#645)

50_scratch_tabs wrote:

(#644)

AmpElectrecuted wrote:

I'm re-deploying the website, hopefully it should work

50-scratch-tabs, rebuild your mirror please

Still isn't working

Where is the codeberg workflow? Does it use npm i or ci?

Amp, try rebuilding now. I rebuilt the package-lock, which will matter if you use npm i instead of npm ci

Also could u pls invite me to the codeberg organization? (Username 50_scratch_tabs) I'll still commit primarily from github but this will help for stuff like pages.

My mirror works.

the workflow is in .woodpecker.yml
you should fill this out to get access to the ci

i invited you

also ah i think i got hit by the cache, it works now

50_scratch_tabs wrote:

(#647)

AmpElectrecuted wrote:

(#645)

50_scratch_tabs wrote:

(#644)

AmpElectrecuted wrote:

I'm re-deploying the website, hopefully it should work

50-scratch-tabs, rebuild your mirror please

Still isn't working

Where is the codeberg workflow? Does it use npm i or ci?

Amp, try rebuilding now. I rebuilt the package-lock, which will matter if you use npm i instead of npm ci

Also could u pls invite me to the codeberg organization? (Username 50_scratch_tabs) I'll still commit primarily from github but this will help for stuff like pages.

My mirror works.

the workflow is in .woodpecker.yml
you should fill this out to get access to the ci

i invited you

also ah i think i got hit by the cache, it works now

Lesson learned: run the package-lock workflow on GitHub after updating blocks or VM.

AvidOsirianGuy wrote:

(#648)
Array blocks are still red and unusable

50_scratch_tabs wrote:

(#649)

AvidOsirianGuy wrote:

(#648)
Array blocks are still red and unusable

Use https://50-scratch-tabs.github.io/AmpMirror

AvidOsirianGuy wrote:

50_scratch_tabs wrote:

(#649)

AvidOsirianGuy wrote:

(#648)
Array blocks are still red and unusable

Use https://50-scratch-tabs.github.io/AmpMirror

Every time I try and get to the editor via the header link it gives me a 404.

50_scratch_tabs wrote:

(#651)
or only have a 1 way mirror from GitHub to codeberg.

Codeberg FAQ wrote:

Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.

A detailed explanation can be found in this blog post.

If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror. Pull requests, issues, as well as other repository units can be disabled in your repository's settings. Using this option will skip the deletion of internal references.

50_scratch_tabs wrote:

(#651)
I think we should switch back to GitHub. Having it in two places has been a nightmare, because sometimes it works or doesn't work based on where you commit, or gets fixed or not based on who does it. I'm not opposed to having the mod accessible from multiple locations (mostly js.org and my github.io, but possibly also codeberg.page), but I believe the source code should be in one place.

Plus workflows that run or don't run, and have to be rewritten, this thing is built here, that thing is built there, etc.

If nothing else, remember to run the GitHub workflow after you commit to codeberg. But I think we should not use codeberg, or only have a 1 way mirror from GitHub to codeberg.

AmpElectrecuted wrote:

(#653)

50_scratch_tabs wrote:

(#651)
or only have a 1 way mirror from GitHub to codeberg.

i dont think so

Codeberg FAQ wrote:

Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.

A detailed explanation can be found in this blog post.

If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror. Pull requests, issues, as well as other repository units can be disabled in your repository's settings. Using this option will skip the deletion of internal references.

AvidOsirianGuy wrote:

50_scratch_tabs wrote:

(#649)

AvidOsirianGuy wrote:

(#648)
Array blocks are still red and unusable

Use https://50-scratch-tabs.github.io/AmpMirror

Every time I try and get to the editor via the header link it gives me a 404.

50_scratch_tabs wrote:

AvidOsirianGuy wrote:

50_scratch_tabs wrote:

(#649)

AvidOsirianGuy wrote:

(#648)
Array blocks are still red and unusable

Use https://50-scratch-tabs.github.io/AmpMirror

Every time I try and get to the editor via the header link it gives me a 404.

Use the try now link, the homepage gets confused when it's not in the root of the web server.

scratchcode1_2_3 wrote:

AmpElectrecuted wrote:

(#653)

50_scratch_tabs wrote:

(#651)
or only have a 1 way mirror from GitHub to codeberg.

i dont think so

Codeberg FAQ wrote:

Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.

A detailed explanation can be found in this blog post.

If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror. Pull requests, issues, as well as other repository units can be disabled in your repository's settings. Using this option will skip the deletion of internal references.

so switch back to github cuz codebreg mid

50_scratch_tabs wrote:

I think we should switch back to GitHub. Having it in two places has been a nightmare, because sometimes it works or doesn't work based on where you commit, or gets fixed or not based on who does it. I'm not opposed to having the mod accessible from multiple locations (mostly js.org and my github.io, but possibly also codeberg.page), but I believe the source code should be in one place.

Plus workflows that run or don't run, and have to be rewritten, this thing is built here, that thing is built there, etc.

If nothing else, remember to run the GitHub workflow after you commit to codeberg. But I think we should not use codeberg, or only have a 1 way mirror from GitHub to codeberg.