You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The services, and/or their configuration, required to run Hubs Community Edition were copied into the community-edition/services folder within this repository in order to ensure that a working Hubs Community Edition instance could be set up. However, it makes more sense for the services to be removed from here (any that don't already have a repository should have one created for them) and replaced with references to the full repositories (either by using git submodules, or a script that clones them as Hubs Compose does) since several of the current services are now outdated, others are likely to follow, and some needed services don't have their own repositories to track changes specific to them or facilitate non Community Edition setups.
For the most part, this is a straightforward enough task, however there are some discrepancies between what is present in community-edition/services and what was present in the repositories at the time the services were copied over (i.e. some stuff was added to the services in community-editon/services that didn't get added to the full repositories and some things were changed to make building the Docker images easier). I have gone through the community-edition/services and compared any that have full repositories to the state of the full repositories at the time they were copied over and noted the differences that were introduced.
The (Proposed) Plan
The following is what I think should be done with the services in community-edition/services and the discrepancies I have identified, along with other relevant notes:
certbotbot (transfer/create)
This should be transferred to a full repository (it doesn't have one, so one will need to be created).
PRs:
placeholder
coturn (transfer/create)
This is the configuration for creating Docker images and running coturn in a Community Edition instance.
It doesn't have it's own repository yet (although there is a fork of the coturn source code with some custom branches, one of which was merged into the upstream coturn), so it should be transferred to a full repository (probably named something like coturn-ce-config to prevent confusion).
There have been reports that it doesn't work at present; this could be because the last Mozilla Docker image used the May 24th 2022 release of coturn (4.5.2-r12), so it's possible the Dockerfile may need to be updated to reference the old coturn image.
PRs:
placeholder
dialog (remove/update)
This has netcat fixes that need to be ported over to the main repository (unless a better fix can be found), but then it should be removed.
Essentially, there was a dependency issue for the health check that prevented the Docker image from being built (netcat isn't found in the newer stuff), but the fix (removing netcat and the health check) was only added here and not to the full dialog repository.
This seems to be mostly the same as the full repository, except the Docker file was renamed and there's a changelog.sh script that was added to the service -- although changelog.sh only works in the full repository and needs fixes, e.g. the line 14 exit needs to be removed.
Something will need to be done with the full repository Docker file and the community-edition/services/dockerbuildall.sh convenience script so that they will work together (likely the Docker file in the full repository should be renamed to the standard Dockerfile, but this will require updates to our GitHub Actions as well).
Once the full repository has been updated, this should be removed.
PRs:
placeholder
nearspark (remove/update)
This seems to be mostly the same, except app.js in the full repository is guarded with a try/catch and doesn't have some commented code (we can probably leave this alone and go with the version in the full repository), and the package.json was renamed from package.turkey.json (we should probably use the full repository's package.json, but we may want to add the updated dependencies from package.turkey.json).
Once the full repository has been updated (if needed), this should be removed.
This should be transferred to a full repository (it doesn't have one, so one will need to be created, probably named something like pgbouncer-ce-config to prevent confusion).
PRs:
placeholder
photomnemonic (remove)
There are no differences between this and its full repository, so it should just be removed.
This should be transferred to a full repository (it doesn't have one, so one will need to be created, possibly with a name like postgres-ce-config), and possibly updated to use version 13.
This seems to be mostly the same as the full repository, except the Docker file was renamed and there's a changelog.sh script that was added to the service -- although changelog.sh only works in the full repository and needs fixes, e.g. the line 14 exit needs to be removed.
Something will need to be done with the full repository Docker file and the community-edition/services/dockerbuildall.sh convenience script so that they will work together (likely the Docker file in the full repository should be renamed to the standard Dockerfile, but this will require updates to our GitHub Actions as well).
Once the full repository has been updated, this should be removed.
PRs:
placeholder
speelycaptor (remove)
There are no differences between this and its full repository, so it should just be removed.
PRs:
placeholder
spoke (remove/update)
This seems to be mostly the same as the full repository, except the Docker file was renamed.
Something will need to be done with the full repository Docker file and the community-edition/services/dockerbuildall.sh convenience script so that they will work together (likely the Docker file in the full repository should be renamed to the standard Dockerfile, but this will require updates to our GitHub Actions as well).
Once the full repository has been updated, this should be removed.
PRs:
placeholder
Service Reintegration
Once all the services have been removed, they should be relinked from the full repositories (either by using git submodules, or a script that clones them as Hubs Compose does) and the community-edition/services/dockerbuildall.sh updated, if needed, to work with the relinked services. community-edition/services/readme.md will also need to be updated. UPDATE: the ## Building from Source section (introduced in #395) in the community-edition/readme.md will also need to be updated as well.
PRs:
placeholder
Historical notes
2026-05-12: It was originally planned that the non-customized 3rd-party postgrest, postgres, and haproxy services would have the official versions of their Docker images referenced directly in the community-edition/input-values.yaml file in this repository as overrides, rather than transferring the wrapping Dockerfiles to full repositories to build Hubs Foundation versions for them; however, it was decided at the 2026-04-21 Hubs Dev Meetup that it would be a better user experience to build Hubs Foundation Docker images of the non-customized 3rd-party services so that they can be updated at any time without requiring a release/update of the Community Edition deployment scripts.
Preamble
The services, and/or their configuration, required to run Hubs Community Edition were copied into the
community-edition/servicesfolder within this repository in order to ensure that a working Hubs Community Edition instance could be set up. However, it makes more sense for the services to be removed from here (any that don't already have a repository should have one created for them) and replaced with references to the full repositories (either by using git submodules, or a script that clones them as Hubs Compose does) since several of the current services are now outdated, others are likely to follow, and some needed services don't have their own repositories to track changes specific to them or facilitate non Community Edition setups.For the most part, this is a straightforward enough task, however there are some discrepancies between what is present in
community-edition/servicesand what was present in the repositories at the time the services were copied over (i.e. some stuff was added to the services incommunity-editon/servicesthat didn't get added to the full repositories and some things were changed to make building the Docker images easier). I have gone through thecommunity-edition/servicesand compared any that have full repositories to the state of the full repositories at the time they were copied over and noted the differences that were introduced.The (Proposed) Plan
The following is what I think should be done with the services in
community-edition/servicesand the discrepancies I have identified, along with other relevant notes:certbotbot (transfer/create)
coturn (transfer/create)
coturnin a Community Edition instance.coturnsource code with some custom branches, one of which was merged into the upstreamcoturn), so it should be transferred to a full repository (probably named something likecoturn-ce-configto prevent confusion).coturn(4.5.2-r12), so it's possible the Dockerfile may need to be updated to reference the oldcoturnimage.dialog (remove/update)
netcatfixes that need to be ported over to the main repository (unless a better fix can be found), but then it should be removed.scripts/docker/run.sh(lines 4-9) was commented out.Dockerfilewas replaced with the following (removing netcat):# run apt-get update > /dev/null && apt-get install -y jq curl dnsutils netcat > /dev/nullrun apt-get update > /dev/null && apt-get install -y jq curl dnsutils > /dev/nullhaproxy (transfer/create)
haproxy-ce-config).hubs (remove/update)
changelog.shscript that was added to the service -- althoughchangelog.shonly works in the full repository and needs fixes, e.g. the line 14 exit needs to be removed.community-edition/services/dockerbuildall.shconvenience script so that they will work together (likely the Docker file in the full repository should be renamed to the standardDockerfile, but this will require updates to our GitHub Actions as well).nearspark (remove/update)
app.jsin the full repository is guarded with a try/catch and doesn't have some commented code (we can probably leave this alone and go with the version in the full repository), and thepackage.jsonwas renamed frompackage.turkey.json(we should probably use the full repository'spackage.json, but we may want to add the updated dependencies frompackage.turkey.json).pgbouncer (transfer/create)
pgbouncer-ce-configto prevent confusion).photomnemonic (remove)
postgres (transfer/create)
postgres-ce-config), and possibly updated to use version 13.postgrest (transfer/create)
postgrest-ce-config).reticulum (remove/update)
changelog.shscript that was added to the service -- althoughchangelog.shonly works in the full repository and needs fixes, e.g. the line 14 exit needs to be removed.community-edition/services/dockerbuildall.shconvenience script so that they will work together (likely the Docker file in the full repository should be renamed to the standardDockerfile, but this will require updates to our GitHub Actions as well).speelycaptor (remove)
spoke (remove/update)
community-edition/services/dockerbuildall.shconvenience script so that they will work together (likely the Docker file in the full repository should be renamed to the standardDockerfile, but this will require updates to our GitHub Actions as well).Service Reintegration
community-edition/services/dockerbuildall.shupdated, if needed, to work with the relinked services.community-edition/services/readme.mdwill also need to be updated. UPDATE: the## Building from Sourcesection (introduced in #395) in thecommunity-edition/readme.mdwill also need to be updated as well.Historical notes
2026-05-12: It was originally planned that the non-customized 3rd-party postgrest, postgres, and haproxy services would have the official versions of their Docker images referenced directly in the
community-edition/input-values.yamlfile in this repository as overrides, rather than transferring the wrapping Dockerfiles to full repositories to build Hubs Foundation versions for them; however, it was decided at the 2026-04-21 Hubs Dev Meetup that it would be a better user experience to build Hubs Foundation Docker images of the non-customized 3rd-party services so that they can be updated at any time without requiring a release/update of the Community Edition deployment scripts.