Automate pushing `hello-world` to Replit

[dglazkov]

Currently, to update the Breadboard Starter Project from packages/hello-world, we need to do a bit of a dance at the end of publishing the packages.

It would be amazing to automate this somehow. Replit doesn't seem to have an API for this, but it does support importing form Github. Maybe that would work?

[Mearman]

I have a semi-solution.

the hello world package would need to be migrated to its own repo. And then I could migrate it to a submodule and set the main repo to sync it?

[dglazkov]

What does it do?

[Mearman]

I should have put the naked link as well https://replit.com/new/github/Mearman/hello-world

It doesn't appear to be possible from a subdirectory or branch though

[Mearman]

silver lining. I could use that as a base for a lot of the other environment templates I want to create

[dglazkov]

being able to roll back also seems important.

[dglazkov]

so the basic idea would be to create a hello-world repository in breadboard-ai org, and then use that repository as the source of truth for replit?

[Mearman]

Yup. I can't see an alternative. I can set up that hello world repo to keep up to date with changes from the main repo, though.

[Mearman]

@dglazkov what did you want to do regarding this? I'm happy to set up the repo and syncing. but would need permission.

[PaulKinlan]

Could we use the run command in the .replit configuration file?

Idly musing, Could we have a npm init breadboard x on first run, and if we detect a special file/folder, run breadboard debug

[Mearman]

possibly, but that wouldn't stop the preview of the template and the template in the repo diverging

[PaulKinlan]

It solves the issue of "the dance" at the end of publishing, which I think is what's needed. i.e, we're asking devs to use the public versions of the repo.

[Mearman]

sorry I mean the actual contents of the template actually up on replit. as that wouldn't be updated by release, the result of the command in the .replit config could be entirely different to what was actually in the template. Using the replit/new URL will always be initialised from the head of that repo

[PaulKinlan]

It's pretty hard for us to set up new repos (it's a process thing).

The init @google-labs/breadboard has a dependency on hello-world so any updates once published will go to this... It's definately not as up to date as the replit/new, but it does mean that the published hello-world is tied to published breadboard lib (which I think is the correct way of working).

https://replit.com/@paulkinlan/RevolvingCruelWordprocessing < is a POC (it's certainly not the best solution because it requires a subdirectory, but it is deployable too poc-2)

[Mearman]

oooooh ok. I didn't expect the config would give you that much scope. I shall experiment further.

[Mearman]

as the create package doesn't currently support merging into an existing directory I've done this inspired by your POC. what do you think?

[dglazkov]

HOLY MOLY. I like it.

[Mearman]

Thanks to @PaulKinlan for putting me on the right track. Though using it as a fork from a replit instance would still result in different content. So I'm not 100% happy with it yet. https://github.com/ExaDev-io/breadboard-replit/blob/main/init.sh

[dglazkov]

Shall we land this in main repo?

[Mearman]

I still feel like it's missing a piece. As for it to work properly the init replit config would still have to be at the root.