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
But to use it in the system installation script, it would be very useful to have an endpoint that can be used for curl.
By keeping it within the project's own repository, you would have control over how it should work.
Which installs blocky DNS proxy (which is very good, thanks for creating it).
Their script installs the latest version of blocky project. But with the configuration files from an old version, which makes blocky not work.
Since they are a project that tries to "facilitate" installations, it would be almost an endless battle, trying to manage all the projects, all the configurations when they are created.
When I did the installation using the script, because of this configuration incompatibility problem, I had the feeling that the blocky was not working.
Due to "willpower" in wanting to make blocky work, I worked to identify that the problem was actually the incompatibility of the initial configuration, and that it was "hardcoded", where it could be a curl that does the initial download.
Hi, could you create a config.yml in the docs that is a minimal configuration?
It would be great to have this for installation scripts.
The text was updated successfully, but these errors were encountered: