Custom container

[docjyJ]

Is it possible to add your own container?

For example, mount a json file my_container.json

[szaimen]

Hi, for what do you need this?

But yes, it should be possible to mount a custom folder say my_custom into the container inside /var/www/docker-aio/community-containers/ in the container and also provide a my_custom.json in the folder. then you can enable the container via --env AIO_COMMUNITY_CONTAINERS="my_custom".

[docjyJ]

{
    "aio_services_v1": [
        {
            "container_name": "nextcloud-aio-nocodb",
            "display_name": "NocoDB",
            "documentation": "https://github.com/nextcloud/all-in-one/tree/main/community-containers/nocodb",
            "image": "docjyj/aio-nocodb",
            "image_tag": "%AIO_CHANNEL%",
            "internal_port": "10028",
            "restart": "unless-stopped",
            "ports": [
                {
                    "ip_binding": "%APACHE_IP_BINDING%",
                    "port_number": "10028",
                    "protocol": "tcp"
                }
            ],
            "environment": [
                "NC_AUTH_JWT_SECRET=%NOCODB_JWT_SECRET%",
                "NC_PUBLIC_URL=https://table.%NC_DOMAIN%/",
                "NC_ADMIN_EMAIL=admin@noco.db",
                "NC_ADMIN_PASS=%NOCODB_USER_PASS%",
                "PORT=10028",
                "NC_DISABLE_TELE=true"
            ],
            "secrets": [
                "NOCODB_JWT_SECRET",
                "NOCODB_USER_PASS"
            ],
            "volumes": [
                {
                    "source": "nextcloud_aio_nocodb",
                    "destination": "/usr/app/data",
                    "writeable": true
                }
            ],
            "backup_volumes": [
                "nextcloud_aio_nocodb"
            ]
        }
    ]
}

Volume : <path/to.json>:/var/www/docker-aio/community-containers/my_nocodb/my_nocodb.json
Env: AIO_COMMUNITY_CONTAINERS=<other> my_nocodb
Repo: https://github.com/docjyJ/aio-nocodb

Publish and functional on my server!

Note: When Nextcloud Tables will be at the same level, I will stop keeping up to date because it will be useless

Do I make PR?

[szaimen]

Publish and functional on my server!

Nice!

Note: When Nextcloud Tables will be at the same level, I will stop keeping up to date because it will be useless

I see...

Do I make PR?

This is of course up to you but since it is already ready, I would say yes, go for it :)

I guess you could state this disclaimer in the readme though to transparently inform people directly. Then if the day should come, someone from the community can take over if they need it :)

[szaimen]

Btw, @docjyJ since you dont seem to change anything insjde the container, you could also use the nocodb/nocodb image directly. See e.g.

all-in-one/community-containers/vaultwarden/vaultwarden.json

Line 7 in cbe0a89

"image": "vaultwarden/server",

[szaimen]

Or am I missing something?

[docjyJ]

I guess you could state this disclaimer in the readme though to transparently inform people directly. Then if the day should come, someone from the community can take over if they need it :)

Everyone will want to change for an intricate tool directly in NextCloud. :)

Btw, @docjyJ since you dont seem to change anything insjde the container, you could also use the nocodb/nocodb image directly. See e.g.

I want to be informed of updates in case of braking change. But, I can change it in my PR.