rocketdoo 1.0__tar.gz

rocketdoo-1.0/LICENSE

@@ -0,0 +1,63 @@
+GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+                       Copyright (C) 2024 Horacio Montaño
+
+
+Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
+
+0. Additional Definitions.
+As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
+
+“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
+
+An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
+
+A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
+
+The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
+
+The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
+
+1. Exception to Section 3 of the GNU GPL.
+You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
+
+2. Conveying Modified Versions.
+If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
+  a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
+  b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
+
+3. Object Code Incorporating Material from Library Header Files.
+The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts, and accessors, small macros, and small inline functions (ten lines or less in length), you do both of the following:
+  a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
+  b) Accompany the object code with a copy of the GNU GPL and this license document.
+
+4. Combined Works.
+You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
+  a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
+  b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
+  c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
+  d) Do one of the following:
+      0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
+      1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
+
+5. Combined Libraries.
+You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
+  a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
+  b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
+
+6. Revised Versions of the GNU Lesser General Public License.
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+Each version is given a distinguishing version number. If the Library specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library does not specify a version number of the GNU Lesser General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
+
+<div Rocketdoo=""></div>
+
+Licencia: LGPL-3.0+
+Versión: "1.0"
+Autor: Horacio Montaño, Elias Braceras
+Fecha: 16/10/2024
+Descripción: Framework to development Odoo

rocketdoo-1.0/PKG-INFO

@@ -0,0 +1,133 @@
+Metadata-Version: 2.1
+Name: rocketdoo
+Version: 1.0
+Summary: This library allows you to build an automated local development environment for Odoo EE and CE.
+Home-page: https://github.com/HDM-soft/rocketdoo.git
+Author: Horacio Montaño and Elias Braceras
+Author-email: horaciomontano@hdmsoft.com.ar
+Description-Content-Type: text/markdown
+License-File: LICENSE
+
+# HDMsoft
+[visit our page](https://odoo.hdmsoft.com.ar)
+
+## ROCKETDOO
+
+Base repository for Odoo development.
+
+## Developed by:
+
+   - "Elias Braceras"
+   - "Horacio Montaño"
+
+## Version: 
+   - "1.0"
+
+----------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Simple Description:
+
+  This repository should be used as a template for any Odoo development. It comes equipped with a set of tools to streamline work during the development preparation process. This development environment is designed as a Python library, so it’s important to install it as such.
+
+  - This development environment is intended for those developing on Linux operating systems, such as Ubuntu, Debian, etc. However, for those who prefer to develop on Windows, we suggest installing **WSL2**, the Windows Subsystem for Linux.
+  
+  - This version includes a CLI project launcher designed to make setting up your development project easier.
+  
+  - Docker is used to create Odoo instances, and Docker Compose is used to spin them up along with a database.
+
+  - A set of configurations is provided for use in VSCode, including debugging and container launch configurations.
+
+  - Gitman is used for downloading and installing external repositories.
+  
+  - Make sure you have **Docker** and **Docker Compose** installed on your computer. If not, you can follow the official Docker installation guide, [Docker Installation Guide](https://docs.docker.com/engine/install/ubuntu/).
+
+  - This environment allows for working with private repositories. For this, the developer user needs to copy their private key and corresponding public key—those used for their GitHub repo configuration—into the **.ssh** folder in this directory.
+ 
+------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### INSTRUCTIONS:
+
+ 1. The first step is to use the HDMSOFT repository, our **rocketdoo** template, by creating a repository from it using the green **use this template** button at the top right corner.
+ 
+ 2. Decide on a name for your development repository.
+ 
+ 3. Once your repository is created, clone it:
+
+    ```git clone "your_repo_url"``` 
+    
+
+ 4. Before running the launcher, navigate to your repository directory and install the dependencies using the command:
+ 
+    ```sudo pip3 install -r requirements.txt```
+ 
+ 5. Now you can run ROCKETDOO with the command: 
+ 
+    ```rocketdoo```
+
+ 6. Follow the steps provided by the launch software.
+
+ 7. The second stage of the LAUNCHER offers you the option to use **GITMAN** for third-party repositories. If you say yes, you’ll need to answer some questions.
+
+ 8. Our launcher will modify the odoo.conf file in the "addons_path" line with the new repositories.
+
+ 9. Once your project is ready, you can bring up your local instance with: 
+    
+    ```docker compose up```
+
+ 11. RocketDoo will start building the environment image and then launch the system. Once successfully completed, you can check by entering the following URL in your web browser: **localhost:port**
+ 
+ 12. If your project has launched successfully, you can run the command:
+    
+    ```code .```
+    
+    NOW YOU CAN START DEVELOPING WITH "VISUAL STUDIO CODE"! 
+
+ ------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Suggestions and Considerations:
+
+ - We recommend using Visual Studio Code Extensions, such as **Docker**, **Dev Container**, and any others you find useful for working in VSCode.
+
+ - If you wish to develop in the Enterprise edition, Rocketdoo will ask you, and will make the necessary configurations. However, you should ensure that you have the "enterprise" folder with all the modules and place it in the root of this project.
+ 
+### HOW TO ADD MORE MODULES TO GITMAN IF YOU DID NOT DO IT WITH THE LAUNCHER?
+
+  - If you need to use third-party addons after setting up your development environment with our launcher, you’ll need to manually edit the **gitman.yml** file and also add lines to the **odoo.conf** addons_path using:
+
+      ```sudo nano gitman.yml``` 
+  
+  and complete each line, starting with the repository URL and version, according to your development deployment version. You’ll need to replicate the set of lines to add more third-party repositories.
+  
+  If you need help, you can refer to the [gitman official guide](https://gitman.readthedocs.io/en/latest/).
+
+  - In this example, you can see how to add your new module package paths.
+  
+  Example:
+      ```addons_path: usr/lib/python/dist-packages/odoo/extra_addons/,usr/lib/python/dist-packages/odoo/external_addons/account-financial-tools```
+    
+  - Gitman creates a folder containing all declared modules under **external_addons**, which can be found inside your Odoo web container at the path declared in **odoo.conf**.
+
+  - All paths should be separated by a comma ","
+  - Once third-party modules are declared in "gitman," you’ll need to rebuild your image, keeping the same image name as initially created, using the command:
+
+      ```docker build . -t my-image-name```
+  
+  - Then restart the Odoo service or container with the command:
+    
+      ```docker compose restart```
+  
+  and once in your Odoo instance, refresh the application list in "developer" mode to see the new modules.
+
+If you modify your **gitman.yml** file before building with the "build" command, it will be sufficient to see the modules without needing to restart your containers.
+
+  - For simpler third-party modules, as well as the module you’re developing, we recommend placing them in the **addons** folder within your working directory.
+
+------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Technical Support
+
+- If you have any questions or issues with our development environment, you can contact us and submit your inquiry or support ticket by clicking on the link below.
+
+ - [Support Link](https://odoo.hdmsoft.com.ar/contactus)
+
+

rocketdoo-1.0/README.md

@@ -0,0 +1,123 @@
+# HDMsoft
+[visit our page](https://odoo.hdmsoft.com.ar)
+
+## ROCKETDOO
+
+Base repository for Odoo development.
+
+## Developed by:
+
+   - "Elias Braceras"
+   - "Horacio Montaño"
+
+## Version: 
+   - "1.0"
+
+----------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Simple Description:
+
+  This repository should be used as a template for any Odoo development. It comes equipped with a set of tools to streamline work during the development preparation process. This development environment is designed as a Python library, so it’s important to install it as such.
+
+  - This development environment is intended for those developing on Linux operating systems, such as Ubuntu, Debian, etc. However, for those who prefer to develop on Windows, we suggest installing **WSL2**, the Windows Subsystem for Linux.
+  
+  - This version includes a CLI project launcher designed to make setting up your development project easier.
+  
+  - Docker is used to create Odoo instances, and Docker Compose is used to spin them up along with a database.
+
+  - A set of configurations is provided for use in VSCode, including debugging and container launch configurations.
+
+  - Gitman is used for downloading and installing external repositories.
+  
+  - Make sure you have **Docker** and **Docker Compose** installed on your computer. If not, you can follow the official Docker installation guide, [Docker Installation Guide](https://docs.docker.com/engine/install/ubuntu/).
+
+  - This environment allows for working with private repositories. For this, the developer user needs to copy their private key and corresponding public key—those used for their GitHub repo configuration—into the **.ssh** folder in this directory.
+ 
+------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### INSTRUCTIONS:
+
+ 1. The first step is to use the HDMSOFT repository, our **rocketdoo** template, by creating a repository from it using the green **use this template** button at the top right corner.
+ 
+ 2. Decide on a name for your development repository.
+ 
+ 3. Once your repository is created, clone it:
+
+    ```git clone "your_repo_url"``` 
+    
+
+ 4. Before running the launcher, navigate to your repository directory and install the dependencies using the command:
+ 
+    ```sudo pip3 install -r requirements.txt```
+ 
+ 5. Now you can run ROCKETDOO with the command: 
+ 
+    ```rocketdoo```
+
+ 6. Follow the steps provided by the launch software.
+
+ 7. The second stage of the LAUNCHER offers you the option to use **GITMAN** for third-party repositories. If you say yes, you’ll need to answer some questions.
+
+ 8. Our launcher will modify the odoo.conf file in the "addons_path" line with the new repositories.
+
+ 9. Once your project is ready, you can bring up your local instance with: 
+    
+    ```docker compose up```
+
+ 11. RocketDoo will start building the environment image and then launch the system. Once successfully completed, you can check by entering the following URL in your web browser: **localhost:port**
+ 
+ 12. If your project has launched successfully, you can run the command:
+    
+    ```code .```
+    
+    NOW YOU CAN START DEVELOPING WITH "VISUAL STUDIO CODE"! 
+
+ ------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Suggestions and Considerations:
+
+ - We recommend using Visual Studio Code Extensions, such as **Docker**, **Dev Container**, and any others you find useful for working in VSCode.
+
+ - If you wish to develop in the Enterprise edition, Rocketdoo will ask you, and will make the necessary configurations. However, you should ensure that you have the "enterprise" folder with all the modules and place it in the root of this project.
+ 
+### HOW TO ADD MORE MODULES TO GITMAN IF YOU DID NOT DO IT WITH THE LAUNCHER?
+
+  - If you need to use third-party addons after setting up your development environment with our launcher, you’ll need to manually edit the **gitman.yml** file and also add lines to the **odoo.conf** addons_path using:
+
+      ```sudo nano gitman.yml``` 
+  
+  and complete each line, starting with the repository URL and version, according to your development deployment version. You’ll need to replicate the set of lines to add more third-party repositories.
+  
+  If you need help, you can refer to the [gitman official guide](https://gitman.readthedocs.io/en/latest/).
+
+  - In this example, you can see how to add your new module package paths.
+  
+  Example:
+      ```addons_path: usr/lib/python/dist-packages/odoo/extra_addons/,usr/lib/python/dist-packages/odoo/external_addons/account-financial-tools```
+    
+  - Gitman creates a folder containing all declared modules under **external_addons**, which can be found inside your Odoo web container at the path declared in **odoo.conf**.
+
+  - All paths should be separated by a comma ","
+  - Once third-party modules are declared in "gitman," you’ll need to rebuild your image, keeping the same image name as initially created, using the command:
+
+      ```docker build . -t my-image-name```
+  
+  - Then restart the Odoo service or container with the command:
+    
+      ```docker compose restart```
+  
+  and once in your Odoo instance, refresh the application list in "developer" mode to see the new modules.
+
+If you modify your **gitman.yml** file before building with the "build" command, it will be sufficient to see the modules without needing to restart your containers.
+
+  - For simpler third-party modules, as well as the module you’re developing, we recommend placing them in the **addons** folder within your working directory.
+
+------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Technical Support
+
+- If you have any questions or issues with our development environment, you can contact us and submit your inquiry or support ticket by clicking on the link below.
+
+ - [Support Link](https://odoo.hdmsoft.com.ar/contactus)
+
+

rocketdoo-1.0/rocketdoo/__init__.py

@@ -0,0 +1,2 @@
+# __init__.py
+from .rocketdoo import main

rocketdoo-1.0/rocketdoo/config.py

@@ -0,0 +1,396 @@
+
+import sys
+import os
+import re
+import yaml
+
+
+docker_compose_path = "docker-compose.yml"
+dockerfile_path = "Dockerfile"
+
+# Function to modify docker-compose.yml
+
+def modificar_docker_compose(edicion):
+    if edicion.lower() == 'ee':
+        try:
+            # Read docker compose at first
+            with open(docker_compose_path, 'r') as file:
+                contenido = file.readlines()
+
+            # Modify content memory
+            contenido_modificado = []
+            for linea in contenido:
+                # Check if the line has the specific pattern
+                if linea.lstrip().startswith('#- ./enterprise:/usr/lib/python3/dist-packages/odoo/enterprise'):
+                    # Remove only the '#' symbol that appears after the spaces, without affecting the indentation.
+                    indentacion = len(linea) - len(linea.lstrip())
+                    linea = ' ' * indentacion + linea.lstrip().lstrip('#').lstrip()
+                    contenido_modificado.append(linea)
+                else:
+                    contenido_modificado.append(linea)
+
+            # Writes the modified content back to the file
+            with open(docker_compose_path, 'w') as file:
+                file.writelines(contenido_modificado)
+
+            print("Ambiente preparado para la edición Enterprise. Asegurese de subir a la raiz del proyecto su carpeta Enterprise.")
+        except FileNotFoundError:
+            print(f"El archivo {docker_compose_path} no se encontró.")
+        except Exception as e:
+            print(f"Error al modificar {docker_compose_path}: {e}")
+
+# Function to modify the odoo.conf file
+def modificar_odoo_conf(edicion):
+    odoo_conf_path = os.path.join("config", "odoo.conf")
+    
+    if edicion.lower() == 'ee':
+        # Ensure that the file exists
+        if not os.path.exists(odoo_conf_path):
+            print(f"El archivo {odoo_conf_path} no existe.")
+            return
+
+        with open(odoo_conf_path, 'r') as file:
+            contenido = file.read()
+
+        # Add enterprise path to addons_path
+        addons_path = "/usr/lib/python3/dist-packages/odoo/enterprise"
+        contenido_modificado = re.sub(r'(addons_path\s*=\s*)(.*)', r'\1\2,{}'.format(addons_path), contenido)
+
+        with open(odoo_conf_path, 'w') as file:
+            file.write(contenido_modificado)
+
+        print("Archivo odoo.conf modificado para incluir el path de Enterprise.")
+
+# Ask for the odoo edition
+edicion = input("¿En qué edición de Odoo va a desarrollar? Community o Enterprise (ce/ee): ").strip().lower()
+
+# Apply modifications if Enterprise edition
+if edicion == 'ee':
+    modificar_docker_compose(edicion)
+    modificar_odoo_conf(edicion)
+else:
+    print("Edición Community seleccionada")
+    
+# SSH lines to be searched and uncommented/commented as needed
+ssh_lines = [
+    "#RUN mkdir -p /root/.ssh\n",
+    "#COPY ./.ssh/rsa /root/.ssh/id_rsa\n",  # The “rsa” will be replaced with the correct key name.
+    "#RUN chmod 700 /root/.ssh/id_rsa\n",
+    '#RUN echo "StrictHostKeyChecking no" >> /root/.ssh/config\n',
+]
+
+
+def get_input(prompt, required=True):
+    """Function that receives an input from the user, with the option of not being mandatory."""
+    value = input(prompt)
+    while required and not value:
+        value = input("Este campo no puede estar vacío. " + prompt)
+    return value
+
+
+def manejar_ssh(repos_privados, dockerfile_path):
+    """Uncomment or comment out the SSH-related lines in the Dockerfile, and replace 'rsa' with the correct private key."""
+    if usar_repos_privados == 's':
+        manejar_claves_ssh
+    else:
+        return
+    
+    # Search for the private key in the ./.ssh folder.
+    ssh_folder = "./.ssh"
+    try:
+        ssh_keys = [
+            f
+            for f in os.listdir(ssh_folder)
+            if os.path.isfile(os.path.join(ssh_folder, f))
+        ]
+        if not ssh_keys:
+            print(f"No se encontraron claves privadas en {ssh_folder}.")
+            return
+
+        # Ask the user which password to use if there is more than one.
+        ssh_key = ssh_keys[0]
+        if len(ssh_keys) > 1:
+            print("Se encontraron las siguientes claves privadas en ./.ssh:")
+            for i, key in enumerate(ssh_keys):
+                print(f"{i + 1}. {key}")
+            key_index = (
+                int(get_input("Selecciona el número de la clave que deseas usar: ")) - 1
+            )
+            ssh_key = ssh_keys[key_index]
+
+        # Modify Dockerfile
+        with open(dockerfile_path, "r") as file:
+            lines = file.readlines()
+
+        with open(dockerfile_path, "w") as file:
+            for line in lines:
+                # If the user wants to use private repos, we uncomment the lines related to SSH
+                if repos_privados and any(
+                    ssh_line.strip().lstrip("# ") in line for ssh_line in ssh_lines
+                ):
+                    # Just uncomment commented lines and modify “rsa” to the correct key name.
+                    if line.startswith("#RUN mkdir -p /root/.ssh"):
+                        file.write(line.lstrip("# "))  # Descomentar
+                    elif "COPY ./.ssh/rsa" in line:
+                        file.write(
+                            line.replace("rsa", ssh_key).lstrip("# ")
+                        )  # Uncomment and replace
+                    elif "RUN chmod 700 /root/.ssh/id_rsa" in line:
+                        file.write(
+                            line.replace("id_rsa", ssh_key).lstrip("# ")
+                        )  # Uncomment and replace
+                    elif '#RUN echo "StrictHostKeyChecking no"' in line:
+                        file.write(line.lstrip("# "))  # Uncomment
+                        file.write(line)
+                # If you don't want to use private repos, keep or add comments
+                elif not repos_privados and any(
+                    ssh_line.strip().lstrip("# ") in line for ssh_line in ssh_lines
+                ):
+                    file.write(f"# {line.lstrip('# ')}")  # Ensure to be commented
+                else:
+                    file.write(line)
+
+        print(
+            f"Líneas relacionadas con SSH {'descomentadas' if repos_privados else 'comentadas'} en {dockerfile_path}."
+        )
+
+    except Exception as e:
+        print(f"Error al manejar las claves SSH: {e}")
+
+
+def comentar_lineas():
+    """Comment out specific lines in the Dockerfile."""
+    copy_line = "COPY ./gitman.yml /usr/lib/python3/dist-packages/odoo/\n"
+    gitman_line = "RUN gitman install -r /usr/lib/python3/dist-packages/odoo/\n"
+
+    try:
+        with open(dockerfile_path, "r") as file:
+            lines = file.readlines()
+
+        with open(dockerfile_path, "w") as file:
+            for line in lines:
+                if line == copy_line or line == gitman_line:
+                    file.write(f"# {line}")
+                else:
+                    file.write(line)
+
+        print("Líneas comentadas correctamente en el Dockerfile.")
+
+    except FileNotFoundError:
+        print(f"El archivo {dockerfile_path} no se encontró.")
+    except Exception as e:
+        print(f"Error inesperado: {e}")
+
+
+def manejar_claves_ssh():
+    
+    "Manejar claves SSH solo si se desean utilizar repositorios privados."
+    try:
+        # Get the name of the private key in the folder ./.ssh
+        ssh_folder = "./.ssh"
+        private_key_name = ""
+
+        # Check for files in the folder ./.ssh
+        if os.path.exists(ssh_folder) and os.path.isdir(ssh_folder):
+            files = os.listdir(ssh_folder)
+            private_key_name = next(
+                (f for f in files if not f.startswith(".")), None
+            )  # Send hidden folders
+
+        if not private_key_name:
+            print("No se encontró ninguna clave privada en la carpeta ./.ssh")
+            return
+
+        # Modify Dockefile
+        dockerfile_path = "Dockerfile"
+        copy_ssh_line = (
+            f"COPY ./.ssh/{private_key_name} /root/.ssh/id_{private_key_name}\n"
+        )
+        chmod_ssh_line = f"RUN chmod 700 /root/.ssh/id_{private_key_name}\n"
+
+        with open(dockerfile_path, "r") as file:
+            lines = file.readlines()
+
+        # Check if the lines already exist, and uncomment if necessary.
+        new_lines = []
+        for line in lines:
+            if line.strip() == "#RUN mkdir -p /root/.ssh":
+                new_lines.append("RUN mkdir -p /root/.ssh\n")
+            elif line.strip() == "#COPY ./.ssh/rsa /root/.ssh/id_rsa":
+                new_lines.append(copy_ssh_line)
+            elif line.strip() == "#RUN chmod 700 /root/.ssh/id_rsa":
+                new_lines.append(chmod_ssh_line)
+            else:
+                new_lines.append(line)
+
+        with open(dockerfile_path, "w") as file:
+            file.writelines(new_lines)
+
+        print("Se ha actualizado el Dockerfile con las claves SSH privadas.")
+    except Exception as e:
+        print(f"Error al manejar las claves SSH: {e}")
+
+# Function to validate user input
+def obtener_respuesta_si_no(mensaje):
+    while True:
+        respuesta = input(mensaje).strip().lower()
+        if respuesta in ["s", "n"]:
+            return respuesta
+        else:
+            print("Por favor, ingrese 's' para sí o 'n' para no.")
+    
+    
+# Ask if the user wants to use private repositories
+usar_repos_privados = input("¿Desea utilizar repositorios privados? (s/n): ").strip().lower()
+
+
+# Handle SSH in the Dockerfile based on user response
+manejar_ssh(usar_repos_privados == "s", dockerfile_path)
+
+# Ask if the user wants to user gitman with public repositorie
+usar_gitman = input("¿Desea utilizar gitman, con repositorios de terceros? (s/n): ").strip().lower()
+
+if usar_gitman != "s":
+    if os.path.exists("gitman.yml"):
+        os.remove("gitman.yml")
+
+    print("Sin cambios en gitman. Comentando líneas del Dockerfile...")
+    comentar_lineas()
+    sys.exit(0)
+
+
+# Here I would follow the rest of your code to configure Gitman and modify odoo.conf...
+
+# Define the initial structure of the configuration file
+config = {
+    "location": "external_addons",
+    "sources": [],
+    "default_group": "",
+    "groups": [],
+}
+
+
+def agregar_repositorio():
+    """Functions to add new repositories"""
+    repo_info = {
+        "repo": get_input("Ingresa el repositorio (repo): "),
+        "name": get_input("Ingresa el nombre (name): "),
+        "rev": get_input("Ingresa la revisión (branch): "),
+        "type": "git",  # keeping fixed,
+        "scripts": [
+            "sh /usr/lib/python3/dist-packages/odoo/install_dependencies.sh"
+        ],  # keeping fixed
+    }
+
+    # Add the repository information to the source list
+    config["sources"].append(repo_info)
+
+
+# Function to modify the odoo.conf file in the config folder
+def modificar_odoo_conf():
+    """Modify the addons_path line in config/odoo.conf by adding the new repositories"""
+    try:
+        # Path to the odoo.conf file in the config folder
+        odoo_conf_path = os.path.join("config", "odoo.conf")
+
+        # Verifying the existence of the odoo.conf file
+        if not os.path.exists(odoo_conf_path):
+            raise FileNotFoundError(f"El archivo {odoo_conf_path} no existe.")
+
+        # We check if we have read and write permissions
+        if not os.access(odoo_conf_path, os.R_OK):
+            raise PermissionError(
+                f"No se puede leer el archivo {odoo_conf_path}. Verifica los permisos."
+            )
+        if not os.access(odoo_conf_path, os.W_OK):
+            raise PermissionError(
+                f"No se puede escribir en el archivo {odoo_conf_path}. Verifica los permisos."
+            )
+
+        print(f"Modificando el archivo {odoo_conf_path}...")
+
+        # We read the gitman.yml file to obtain the names
+        with open("gitman.yml", "r") as file:
+            gitman_data = yaml.safe_load(file)
+
+        # We extract the values of 'name' from each repository in sources, making sure not to include empty ones.
+        nombres_repositorios = [
+            repo["name"] for repo in gitman_data["sources"] if repo["name"]
+        ]
+        print(f"Repositorios extraídos: {nombres_repositorios}")
+
+        # If there are no repository names, we do nothing.
+        if not nombres_repositorios:
+            print("No se encontraron repositorios para agregar.")
+            return
+
+        # We create the new string for addons_path with the new paths
+        nuevas_rutas = ",".join(
+            [
+                f"/usr/lib/python3/dist-packages/odoo/external_addons/{nombre}"
+                for nombre in nombres_repositorios
+            ]
+        )
+
+        # Read the odoo.conf file
+        with open(odoo_conf_path, "r") as file:
+            lines = file.readlines()
+
+        # We look for the line containing addons_path
+        addons_path_encontrado = False
+        for i, line in enumerate(lines):
+            if line.startswith("addons_path ="):
+                # We add the new routes to the existing line, if they are not already there.
+                linea_actual = line.strip().split(" = ")[1]
+                lineas_rutas_existentes = linea_actual.split(",")
+
+                # We add the new routes to the existing ones, if they are not already there.
+                rutas_actualizadas = lineas_rutas_existentes + [
+                    ruta
+                    for ruta in nuevas_rutas.split(",")
+                    if ruta not in lineas_rutas_existentes
+                ]
+                lines[i] = f"addons_path = {','.join(rutas_actualizadas)}\n"
+                addons_path_encontrado = True
+                print(f"Línea addons_path modificada: {lines[i]}")
+                break
+
+        # If addons_path is not found, we add it at the end
+        if not addons_path_encontrado:
+            lines.append(f"addons_path = {nuevas_rutas}\n")
+            print("Se agregó una nueva línea addons_path.")
+
+        # Save the changes in the odoo.conf file.
+        with open(odoo_conf_path, "w") as file:
+            file.writelines(lines)
+
+        print("Archivo odoo.conf actualizado exitosamente.")
+
+    except FileNotFoundError as fnf_error:
+        print(fnf_error)
+    except PermissionError as perm_error:
+        print(perm_error)
+    except Exception as e:
+        print(f"Error inesperado al modificar odoo.conf: {e}")
+
+
+# Main to add repositories
+while True:
+    agregar_repositorio()
+
+    # We ask if the user wants to add more repositories
+    agregar_mas = input("¿Deseas agregar otro repositorio? (s/n): ").strip().lower()
+
+    # Validating answer
+    if agregar_mas != "s":
+        print("Finalizó la configuración de gitman.")
+        break
+
+# Save the gitman files and their configurations on a YAML format
+with open("gitman.yml", "w") as file:
+    yaml.dump(config, file, default_flow_style=False, sort_keys=False)
+
+print("Archivo gitman.yml generado exitosamente.")
+
+# Calling function to modify odoo.conf
+modificar_odoo_conf()

rocketdoo-1.0/rocketdoo/rocketdoo.py

@@ -0,0 +1,44 @@
+import argparse
+import subprocess
+import signal
+import sys
+
+# Define la versión del paquete
+VERSION = "1.0"
+
+# Maneja la interrupción con Ctrl+C
+def signal_handler(sig, frame):
+    print("\nRocketdoo ha sido cancelado por el usuario.")
+    sys.exit(0)
+
+# Registra el manejador de señal para SIGINT (Ctrl+C)
+signal.signal(signal.SIGINT, signal_handler)
+
+def main():
+    # Configura el analizador de argumentos
+    parser = argparse.ArgumentParser(description="Rocketdoo CLI")
+    parser.add_argument(
+        '--version', action='store_true', help="Muestra la versión de Rocketdoo"
+    )
+    
+    # Parsea los argumentos
+    args = parser.parse_args()
+
+    # Si se pasa el argumento --version, muestra la versión y sale
+    if args.version:
+        print(f"Rocketdoo version {VERSION}")
+        return
+
+    # Ejecuta Copier si no se pasa --version
+    try:
+        subprocess.run(["copier", "copy", "./", "./", "--trust"])
+    except KeyboardInterrupt:
+        # Este bloque captura el Ctrl+C y permite salir limpiamente
+        print("\nRocketdoo ha sido cancelado por el usuario.")
+    except Exception as e:
+        # Captura cualquier otro error, sin mostrar traceback detallado
+        print(f"\nError inesperado: {e}")
+    finally:
+        sys.exit(0)
+
+

rocketdoo-1.0/rocketdoo.egg-info/PKG-INFO

@@ -0,0 +1,133 @@
+Metadata-Version: 2.1
+Name: rocketdoo
+Version: 1.0
+Summary: This library allows you to build an automated local development environment for Odoo EE and CE.
+Home-page: https://github.com/HDM-soft/rocketdoo.git
+Author: Horacio Montaño and Elias Braceras
+Author-email: horaciomontano@hdmsoft.com.ar
+Description-Content-Type: text/markdown
+License-File: LICENSE
+
+# HDMsoft
+[visit our page](https://odoo.hdmsoft.com.ar)
+
+## ROCKETDOO
+
+Base repository for Odoo development.
+
+## Developed by:
+
+   - "Elias Braceras"
+   - "Horacio Montaño"
+
+## Version: 
+   - "1.0"
+
+----------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Simple Description:
+
+  This repository should be used as a template for any Odoo development. It comes equipped with a set of tools to streamline work during the development preparation process. This development environment is designed as a Python library, so it’s important to install it as such.
+
+  - This development environment is intended for those developing on Linux operating systems, such as Ubuntu, Debian, etc. However, for those who prefer to develop on Windows, we suggest installing **WSL2**, the Windows Subsystem for Linux.
+  
+  - This version includes a CLI project launcher designed to make setting up your development project easier.
+  
+  - Docker is used to create Odoo instances, and Docker Compose is used to spin them up along with a database.
+
+  - A set of configurations is provided for use in VSCode, including debugging and container launch configurations.
+
+  - Gitman is used for downloading and installing external repositories.
+  
+  - Make sure you have **Docker** and **Docker Compose** installed on your computer. If not, you can follow the official Docker installation guide, [Docker Installation Guide](https://docs.docker.com/engine/install/ubuntu/).
+
+  - This environment allows for working with private repositories. For this, the developer user needs to copy their private key and corresponding public key—those used for their GitHub repo configuration—into the **.ssh** folder in this directory.
+ 
+------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### INSTRUCTIONS:
+
+ 1. The first step is to use the HDMSOFT repository, our **rocketdoo** template, by creating a repository from it using the green **use this template** button at the top right corner.
+ 
+ 2. Decide on a name for your development repository.
+ 
+ 3. Once your repository is created, clone it:
+
+    ```git clone "your_repo_url"``` 
+    
+
+ 4. Before running the launcher, navigate to your repository directory and install the dependencies using the command:
+ 
+    ```sudo pip3 install -r requirements.txt```
+ 
+ 5. Now you can run ROCKETDOO with the command: 
+ 
+    ```rocketdoo```
+
+ 6. Follow the steps provided by the launch software.
+
+ 7. The second stage of the LAUNCHER offers you the option to use **GITMAN** for third-party repositories. If you say yes, you’ll need to answer some questions.
+
+ 8. Our launcher will modify the odoo.conf file in the "addons_path" line with the new repositories.
+
+ 9. Once your project is ready, you can bring up your local instance with: 
+    
+    ```docker compose up```
+
+ 11. RocketDoo will start building the environment image and then launch the system. Once successfully completed, you can check by entering the following URL in your web browser: **localhost:port**
+ 
+ 12. If your project has launched successfully, you can run the command:
+    
+    ```code .```
+    
+    NOW YOU CAN START DEVELOPING WITH "VISUAL STUDIO CODE"! 
+
+ ------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Suggestions and Considerations:
+
+ - We recommend using Visual Studio Code Extensions, such as **Docker**, **Dev Container**, and any others you find useful for working in VSCode.
+
+ - If you wish to develop in the Enterprise edition, Rocketdoo will ask you, and will make the necessary configurations. However, you should ensure that you have the "enterprise" folder with all the modules and place it in the root of this project.
+ 
+### HOW TO ADD MORE MODULES TO GITMAN IF YOU DID NOT DO IT WITH THE LAUNCHER?
+
+  - If you need to use third-party addons after setting up your development environment with our launcher, you’ll need to manually edit the **gitman.yml** file and also add lines to the **odoo.conf** addons_path using:
+
+      ```sudo nano gitman.yml``` 
+  
+  and complete each line, starting with the repository URL and version, according to your development deployment version. You’ll need to replicate the set of lines to add more third-party repositories.
+  
+  If you need help, you can refer to the [gitman official guide](https://gitman.readthedocs.io/en/latest/).
+
+  - In this example, you can see how to add your new module package paths.
+  
+  Example:
+      ```addons_path: usr/lib/python/dist-packages/odoo/extra_addons/,usr/lib/python/dist-packages/odoo/external_addons/account-financial-tools```
+    
+  - Gitman creates a folder containing all declared modules under **external_addons**, which can be found inside your Odoo web container at the path declared in **odoo.conf**.
+
+  - All paths should be separated by a comma ","
+  - Once third-party modules are declared in "gitman," you’ll need to rebuild your image, keeping the same image name as initially created, using the command:
+
+      ```docker build . -t my-image-name```
+  
+  - Then restart the Odoo service or container with the command:
+    
+      ```docker compose restart```
+  
+  and once in your Odoo instance, refresh the application list in "developer" mode to see the new modules.
+
+If you modify your **gitman.yml** file before building with the "build" command, it will be sufficient to see the modules without needing to restart your containers.
+
+  - For simpler third-party modules, as well as the module you’re developing, we recommend placing them in the **addons** folder within your working directory.
+
+------------------------------------------------------------------------------------------------------------------------------------------------------
+
+### Technical Support
+
+- If you have any questions or issues with our development environment, you can contact us and submit your inquiry or support ticket by clicking on the link below.
+
+ - [Support Link](https://odoo.hdmsoft.com.ar/contactus)
+
+

rocketdoo-1.0/rocketdoo.egg-info/SOURCES.txt

@@ -0,0 +1,12 @@
+LICENSE
+README.md
+setup.py
+rocketdoo/__init__.py
+rocketdoo/config.py
+rocketdoo/rocketdoo.py
+rocketdoo.egg-info/PKG-INFO
+rocketdoo.egg-info/SOURCES.txt
+rocketdoo.egg-info/dependency_links.txt
+rocketdoo.egg-info/entry_points.txt
+rocketdoo.egg-info/requires.txt
+rocketdoo.egg-info/top_level.txt

rocketdoo-1.0/rocketdoo.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

rocketdoo-1.0/rocketdoo.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+rocketdoo = rocketdoo:main

rocketdoo-1.0/rocketdoo.egg-info/requires.txt

@@ -0,0 +1 @@
+copier

rocketdoo-1.0/rocketdoo.egg-info/top_level.txt

@@ -0,0 +1 @@
+rocketdoo

rocketdoo-1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

rocketdoo-1.0/setup.py

@@ -0,0 +1,26 @@
+from setuptools import setup, find_packages
+from pathlib import Path
+
+this_directory = Path(__file__).parent
+long_description = (this_directory / "README.md").read_text()
+
+setup(
+    name='rocketdoo',
+    version='1.0',
+    description='This library allows you to build an automated local development environment for Odoo EE and CE.',
+    long_description=long_description,
+    long_description_content_type='text/markdown',
+    author='Horacio Montaño and Elias Braceras',
+    author_email='horaciomontano@hdmsoft.com.ar',
+    url='https://github.com/HDM-soft/rocketdoo.git',
+    packages=find_packages(),
+    install_requires=[
+        'copier',  # Asegúrate de incluir copier en las dependencias
+        # Incluye aquí cualquier otra dependencia que tu proyecto necesite
+    ],
+    entry_points={
+        'console_scripts': [
+            'rocketdoo=rocketdoo:main',
+        ],
+    },
+)