compose-generator / compose-generator Goto Github PK

Is there an existing issue for this?

• I have searched the existing issues

Problem-related

No response

Suggestion

Add FastAPI under backend framework.

https://fastapi.tiangolo.com/

Alternative

No response

Additional context

No response

Instead of having templates for predefined stacks, a dynamic approach would be much more efficent.

We have several questions when generating a docker-compose

1. Is it a dev or production enviroment?

Include nginx reverse proxy: jwilder/nginx-proxy , include let's encry: jrcs/letsencrypt-nginx-proxy-companion

2. Do you want a frontend? Which one?

Angular / React / Vue -> does frontend exist? no -> run create-react-app / npx create-next-app / ng new

3. What Backend do you want to use?

Spring / Node / PHP / Rust -> does backend exist? no -> run sprinig initializer / ...

3. What DB you want to use?

Postgres / MariaDB / Mongo / H2 / ....

4. Do you want a DB Admin tool

Phpmyadmin, pgAdmin

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for networks: 'backend-database'
Unsupported config option for services: 'backend-node'

my docker-compose.yml file generated like this: docker-compose.yml file

Expected Behavior

running project by command docker-compose up

Steps To Reproduce

generated stack: react + node + postgres + adminer

Environment

- OS:Ubuntu 20.04
- Installation method:deb file
- npm:8.15.0

Docker version 20.10.18, build b40c2f6
docker-compose version 1.25.0, build unknown

Anything else?

why compose-generator doesn't startd without sudo?

Currently, I understand we can use 'custom' backends, etc. in the prompt by choosing custom services and defining the Docker image to pull, env vars, network exposure, etc.

However, I am encountering the issue that if you only are working with a custom service definition and no other templated service definitions the program hard-errors on "No templates selected." and aborts.

Is this by-design? Or is this a bug? (If this is a bug I'll re-file as a Bug type issue and follow your layout/template)

Is there an existing issue for this?

• I have searched the existing issues

Problem-related

Running the docker image on arm (M1) is not supported.

Suggestion

Add linux/arm64/v8 to the build-process.

Alternative

No response

Additional context

No response

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Following the "from scratch" guide, after installing the compose-generator from the repository listed in the documentation, I am following the setup process and setting up a single-container "custom" environment - I choose a custom frontend, and follow all the config steps, and leave all other options left alone, and get an error at the end about "no templates selected", and it aborts.

Expected Behavior

I would expect that the 'custom' compose file would still be generated rather than it erroring saying it can't do it because no templates are selected.

Detailed steps in next section.

Steps To Reproduce

1. Execute compose-generator g
2. Name = Test
3. Doesn't matter if prod-ready is selected or not (using N for now)
4. Custom Frontend
   • Don't build from source
   • Standard docker registry (docker.io)
   • Use hello-world for a test.
   • frontend-hello-world for service name
   • (same for container)
   • Do not add volumes
   • Do not add networks
   • Do not expose ports
   • No env vars
   • No env files
5. Do not select any backend services, database services, or admin services
6. Do not include Watchtower.

Error will happen similar to:

ERROR: 2023/02/15 19:16:48 No templates selected. Aborting ...

Environment

- OS: Ubuntu 20.04 (and 22.04)
- Installation method: APT package manager via specified repositories
- Compose Generator version: 1.9.0 built on 2022-07-02 21:44:48 UTC by github-actions

Anything else?

Original question RE: this is here #431