Create a simple compose file for anyone who uses Opencloud personally and doesn't need a production ready instance.

[lolloARX]

This survey is for those who use Opencloud for personal use and think that configuring an .env file full of superfluous services (plus some compose files) is excessive and complicated to use Opencloud as a simple cloud and document editor.

[micbar]

@lolloARX What scope should that "simple compose file" have?

There have been many attempts to create one. But people were not happy with the bare minimum.

One could imagine "just opencloud". That is pretty simple.

https://docs.opencloud.eu/docs/next/admin/getting-started/container/docker#start-opencloud

docker run \
    --name opencloud \
    --rm \
    -d \
    -p 9200:9200 \
    -v $HOME/opencloud/opencloud-config:/etc/opencloud \
    -v $HOME/opencloud/opencloud-data:/var/lib/opencloud \
    -e OC_INSECURE=true \
    -e PROXY_HTTP_ADDR=0.0.0.0:9200 \
    -e OC_URL=https://localhost:9200 \
    opencloudeu/opencloud-rolling:latest

[lolloARX]

The advantages of a compose file are numerous:
1.A relatively simple syntax
2.Easy to start with a single command (instead of a long one that is more prone to errors)
3.Easily replicable
4.Easy to manage (for example, stopping all the containers inside that compose file with a single command)

(I would like to point out that these are all advantages that benefit users who have the skills to configure a .env file and some compose files to replace certain parameters that cannot be modified from the .env file.)

It is true that many people are not satisfied with having only the bare minimum, but it is impossible that all OpenCloud users are companies or users who appreciate such a feature-rich instance, often described as difficult to configure (as can be seen from various help requests from users whose instances do not start or who encounter configuration difficulties). It also cannot be said that OpenCloud is aimed only at experts, because on your own website it states: “OpenCloud is immediately understandable thanks to its intuitive operation even for new users.”

Therefore, I would suggest two different approaches:
1.A feature-rich approach for companies.
2.A simple approach with a compose file containing examples that are easy to apply and modify within a single compose file.

[micbar]

That is all well said.

Back to my question: Which features do you have in mind? Which reverse proxy?

[lolloARX]

Something like Caddy with its Caddy file, which is easy to configure, or Nginx Proxy Manager with its graphical interface, which, after trying it, I can confirm is really simple to use.

Obviously, I think they should all be presented exclusively as examples so that everyone can choose what they prefer.

This could also be useful for companies that perhaps manage certificates and reverse proxies centrally, rather than with a different configuration for each service.

[micbar]

Sorry to say: But are you just asking to get "everything"? I thought it should be simple...

[lolloARX]

If you ask me "which reverse proxy" I’m providing you with not one but two alternatives that are easy enough for a beginner, and I repeat that in my opinion they should only be added as examples so that everyone can choose what to use and whether to use it.