feat(dev): add Hound development env #7

yoctozepto commented 2023年09月09日 12:50:27 +02:00

No description provided.

👍 1

yoctozepto commented 2023年09月09日 18:58:22 +02:00

EDIT: I have created the Codeberg-Search "organization" on Codeberg and forked hound there as well https://codeberg.org/Codeberg-Search/hound

I start feeling uneasy when you come up with the same ideas I have after leaving my desk and driving to family. 😅 Kidding aside, it also makes me happy to have a similar-minded folk around.

> EDIT: I have created the Codeberg-Search "organization" on Codeberg and forked `hound` there as well https://codeberg.org/Codeberg-Search/hound I start feeling uneasy when you come up with the same ideas I have after leaving my desk and driving to family. 😅 Kidding aside, it also makes me happy to have a similar-minded folk around.

yoctozepto commented 2023年09月09日 18:59:49 +02:00

It would also be worth pointing out how to connect this docker-compose to the forgejo deployment (network specifically) that we create under /dev/docker-compose.yml

That's some later step. For playground this is enough.

I am going to "fix" the two inline comments and say it's gtg.

> It would also be worth pointing out how to connect this docker-compose to the forgejo deployment (network specifically) that we create under /dev/docker-compose.yml That's some later step. For playground this is enough. I am going to "fix" the two inline comments and say it's gtg.

fourstepper commented 2023年09月09日 19:01:54 +02:00

It would also be worth pointing out how to connect this docker-compose to the forgejo deployment (network specifically) that we create under /dev/docker-compose.yml

That's some later step. For playground this is enough.

I am going to "fix" the two inline comments and say it's gtg.

I guess alright - at the same time I would appreciate it if we actually built some simple docker build+push pipeline for the hound repo fork so we don't have to build the image every time we want to use it - either that or we can submodule the entire hound fork and build right from the compose.

My point is: why not do it right the first time around

> > It would also be worth pointing out how to connect this docker-compose to the forgejo deployment (network specifically) that we create under /dev/docker-compose.yml > > That's some later step. For playground this is enough. > > I am going to "fix" the two inline comments and say it's gtg. I guess alright - at the same time I would appreciate it if we actually built some simple docker build+push pipeline for the hound repo fork so we don't have to build the image every time we want to use it - either that or we can `submodule` the entire hound fork and `build` right from the compose. My point is: why not do it _right_ the first time around

yoctozepto commented 2023年09月09日 19:25:40 +02:00

It would also be worth pointing out how to connect this docker-compose to the forgejo deployment (network specifically) that we create under /dev/docker-compose.yml

That's some later step. For playground this is enough.

I am going to "fix" the two inline comments and say it's gtg.

I guess alright - at the same time I would appreciate it if we actually built some simple docker build+push pipeline for the hound repo fork so we don't have to build the image every time we want to use it - either that or we can submodule the entire hound fork and build right from the compose.

My point is: why not do it right the first time around

As said in the chat - let's do it in steps. I also want it better but this is good enough (TM) for now.

> > > It would also be worth pointing out how to connect this docker-compose to the forgejo deployment (network specifically) that we create under /dev/docker-compose.yml > > > > That's some later step. For playground this is enough. > > > > I am going to "fix" the two inline comments and say it's gtg. > > I guess alright - at the same time I would appreciate it if we actually built some simple docker build+push pipeline for the hound repo fork so we don't have to build the image every time we want to use it - either that or we can `submodule` the entire hound fork and `build` right from the compose. > > My point is: why not do it _right_ the first time around As said in the chat - let's do it in steps. I also want it better but this is good enough (TM) for now.