Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Git Aggregator on Doodba
byI don't want to hijack the thread but, Do U have any example of git-autoshare in the context of git-aggregator in doodba? I check out several not merged PRs, I got the impression it was never incorporated to doodba? I'm missing that feature to save some bandwidth.
It just needs to be installed so it wraps git clone.
(in 3.0.0+ https://github.com/acsone/git-aggregator?tab=readme-ov-file#300-2022-09-20 )
Re: --filter=blob:none see also https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone/
Cheers,
Danny
On 11/3/24 23:33, Graeme Gellatly wrote:
The reason they are created outside is so features like debug work and you can develop. There is no duplication, they are mapped via a symlink at start time. This is a very, very common way of doing development for any system (and is how my own internal dev systems work as well), although that is changing. Also from memory Doodba can use git-autoshare which further reduces the disk space taken.
But it is docker and compose, if you want them in the image then just use the staging build, but it will be much harder to work with. The alternative is if you don't want to edit or see source for example some OCA modules is you can pip install using pip.txt in dependencies.
On Mon, Nov 4, 2024 at 11:32 AM Francesco Ballerini <notifications@odoo-community.org> wrote:
Hi, I am configuring an instance with Doodba, I am using the doodba copier template to set up the instanceI just find out how to use the git aggregator by launching these commands
export DOODBA_GITAGGREGATE_UID="$(id -u $USER)" DOODBA_GITAGGREGATE_GID="$(id -g $USER)" DOODBA_UMASK="$(umask)"docker-compose -f setup-devel.yaml run --rm odoo
which I found in setup-devel yaml file file.
I have a few questions:1 - is it actually the proper way to use it on the project ? (maybe it should automatically start when launching docker-compose, but it's not my case)2 - I see that by using the aggregator I still have repositories created in the host, so they are created outside the container as volumes then recreated in the container.Is there a way to avoid keeping remotes (source code, oca repos etc..) on the host and directly create them only inside the container at build time with the aggregator?
Really appreciate any kind of help.
Regards-- Francesco Ballerini
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
