Skip to content

Conversation

@kyteinsky
Copy link
Contributor

No description provided.

@kyteinsky kyteinsky marked this pull request as draft February 12, 2025 11:35
Signed-off-by: Anupam Kumar <[email protected]>
environment:
- NC_HARP_SHARED_KEY=${NC_HAPROXY_SHARED_KEY:-some_very_secure_password}
- NC_INSTANCE_URL=${NC_INSTANCE_URL:-http://nextcloud.local}
- HP_FRP_DISABLE_TLS=${HP_FRP_DISABLE_TLS:-true}
Copy link

@bigcat88 bigcat88 Feb 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do not needed, better to check without this flag set to True. by default we will use auto generated TLS

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can reuse the PROTOCOL env variable that is used to indicate if the setup uses TLS or not in general

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

those value is related to the communication type between HaRP and ExApp only.
we will describe this in the documentation when will work on it.

by default we will always recomend to not disable it.

- /var/run/docker.sock:/var/run/docker.sock
environment:
- NC_HARP_SHARED_KEY=${NC_HAPROXY_SHARED_KEY:-some_very_secure_password}
- NC_INSTANCE_URL=${NC_INSTANCE_URL:-http://nextcloud.local}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should call that something like NC_HARP_INSTANCE_URL, the rest of the setup is usually not pinned to a single nextcloud instance.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of interest: Is there a way to use one harp server for multiple nextcloud servers?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of interest: Is there a way to use one harp server for multiple nextcloud servers?

unfortunately, at the moment - definitely not

@@ -0,0 +1,8 @@
location / {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this need to go in a file jsut called nextcloud.local https://github.com/nginx-proxy/nginx-proxy/tree/main/docs#per-virtual_host or is it possible to have multiple?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah that didn't seem to work
we used this: https://github.com/nginx-proxy/nginx-proxy/tree/main/docs#overriding-location-blocks but the location / was also removed from the main config
maybe _location would allow to add just additional locations, will test

Signed-off-by: Anupam Kumar <[email protected]>
Signed-off-by: Anupam Kumar <[email protected]>
Comment on lines 1111 to 1112
container_name: nextcloud-appapi-harp
network_mode: ${HP_NETWORK_MODE:-master_default}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious about those parts, why do we need to set the network mode here actually?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One can work with different kinds of configurations like host or any other network, for testing.

@kyteinsky
Copy link
Contributor Author

container_name seems necessary for dns setting so the proxy _location addition can connect to it
these are the dns names when container does not have an explicit name:

                    "DNSNames": [
                        "master-appapi-harp-1",
                        "2b4545c5162e"
                    ]

@kyteinsky kyteinsky marked this pull request as ready for review March 3, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants