David Boreham dboreham
0 Followers · 0 Following
  • Joined on 2022-12-08
Repositories
2
 Projects Packages Public Activity Starred Repositories
dboreham pushed tag v0.1.42 to cerc-io/test-progressive-web-app 2024-07-25 17:58:07 +00:00
dboreham pushed to main at cerc-io/test-progressive-web-app 2024-07-25 17:57:38 +00:00
49ed5166a9 Bump version for deployment
dboreham pushed to main at cerc-io/test-progressive-web-app 2024-07-25 17:56:35 +00:00
a4a139b420 Try pinning registry cli at a working older version
dboreham pushed tag v0.1.41 to cerc-io/test-progressive-web-app 2024-07-25 17:46:21 +00:00
dboreham pushed to main at cerc-io/test-progressive-web-app 2024-07-25 17:45:36 +00:00
116f0b30bf Bump version for deployment
dboreham pushed to main at cerc-io/webapp-service-api-stack 2024-07-25 17:27:25 +00:00
2b489f4b22 Initial commit
dboreham created repository cerc-io/webapp-service-api-stack 2024-07-25 17:21:36 +00:00
dboreham approved cerc-io/test-progressive-web-app#15 2024-07-25 17:15:21 +00:00
Switch to next.config.mjs
dboreham pushed to main at cerc-io/snowballtools-base-api-stack 2024-07-25 17:08:29 +00:00
720f748add Jumped the gun
dboreham pushed to main at cerc-io/snowballtools-base-api-stack 2024-07-25 17:07:14 +00:00
49e223b624 Pull from the forked snowball repo
dboreham commented on pull request cerc-io/test-progressive-web-app#14 2024-07-25 16:45:08 +00:00
upgrade to latest laconicd

Why does this need to be pinned?

dboreham commented on issue cerc-io/stack-orchestrator#892 2024-07-25 15:30:15 +00:00
laconic-so build-npms seems to be broken

Since this bug relates to a code path that doesn't work anyway, what's the priority for fixing? Is this blocking publishing npms to git.vdb.to for example?

dboreham commented on issue cerc-io/stack-orchestrator#892 2024-07-25 15:29:21 +00:00
laconic-so build-npms seems to be broken

After some investigation I found that the package-registry stack upon which this code path depends, is also broken. See cerc-io/stack-orchestrator#893

dboreham commented on issue cerc-io/stack-orchestrator#893 2024-07-25 15:28:37 +00:00
package-registry stack is broken

Non-deployment case:

stat /home/david/cerc/hosting/gitea/docker-compose-gitea.yml: no such file or directory
Traceback (most recent call last):
  File "/home/david/projects/cerc/stack-orc…
dboreham commented on issue cerc-io/stack-orchestrator#893 2024-07-25 15:27:41 +00:00
package-registry stack is broken

Deployment case:

[+] Running 0/2
 ⠏ server Pulling                                                                                                                                       …
dboreham opened issue cerc-io/stack-orchestrator#893 2024-07-25 15:27:24 +00:00
package-registry stack is broken
dboreham commented on issue cerc-io/stack-orchestrator#892 2024-07-25 14:56:46 +00:00
laconic-so build-npms seems to be broken

Actually this bug is much older. It only shows when you're trying to publish the npm to a local gitea, which we haven't done for a long time. Publishing to a remote npm service should still work.

dboreham commented on issue cerc-io/testnet-laconicd-stack#13 2024-07-25 14:52:59 +00:00
all the docker images used in this flow should be pre-built and the instruction should pull them from the gitea registry

I created a repo to host the laconicd stacks (no stack content there yet -- it seems to be spread around in various places and needs to be cleaned…

dboreham pushed to main at cerc-io/laconicd-stacks 2024-07-25 14:41:03 +00:00
b5dba33376 Trigger CI