Skip to content

Conversation

@manik0u
Copy link
Contributor

@manik0u manik0u commented Jan 16, 2026

Update of the Readme related to this issue : #85

Update of the Readme related to this issue : nextcloud#85

Signed-off-by: Manikou <91145906+manik0u@users.noreply.github.com>
Copy link
Contributor

@oleksandr-nc oleksandr-nc left a comment

Choose a reason for hiding this comment

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

Can we consider placing it after "Configuring Your Reverse Proxy" or in a new dedicated section.

Sorry for so late review.

Will you be fine if I open a PR replacing it based on your PR? Or I can edit this PR to not lost that idea comes from you.

### On the Nextcloud Web Interface - Daemon Register
Add the following configuration :
```
Daemon Configuraiton template : HaRP Proxy (HOST)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be "Configuration"

# AppAPI Configuration
ProxyPass /exapps/ http://<IP_host2_docker>:8780/exapps/
ProxyPassReverse /exapps/ http://<IP_host2_docker>:8780/exapps/
```
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add ProxyTimeout 1800 here?


##### On the Docker Host
##### Creation of Cert folder (if necessary)
`mkdir -p /some/path/{certs,}`
Copy link
Contributor

Choose a reason for hiding this comment

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

For which cases do we need the empty-name expansion?

-d ghcr.io/nextcloud/nextcloud-appapi-harp:release
```

> **Warning:** Do not forget to change the **HP_SHARED_KEY** value to a secure one!
Copy link
Contributor

Choose a reason for hiding this comment

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

A second "Warning: Do not forget to change HP_SHARED_KEY" that's redundant - it already exists immediately above. (line 74)


Finally, test the whole setup with “Test deploy” in the 3-dots menu of the deploy daemon.

### Additional tests from the network of your hosts (based on Almalinux - RHEL Distros))
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess second ) is a typo?

@oleksandr-nc
Copy link
Contributor

Hi @manik0u, thank you for this contribution!

I've incorporated your changes into #92 with the review feedback addressed. Your commit and authorship are preserved.

Closing this in favor of #92.

@manik0u manik0u deleted the patch-1 branch January 27, 2026 09:35
@manik0u
Copy link
Contributor Author

manik0u commented Jan 27, 2026

Hi @oleksandr-nc ,

Sorry for the delay in responding.
I've been very busy and haven't had time to consider your comments.
Thank you for your actions.

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.

2 participants