Is there a page of documention for absolute beginners? (Like me!) I am having many very confusing issues getting started. I find not a single post or YouTiube video at all about my issues.
For example:
When I log in to my Dashboard, there is only one working link to “Register Package” with fields for “Package import path” and “Version”, but there are no explanations or instructions about what to enter into the fields, or how to do it. Anything at all that I enter results in an error! What is “semantic import versioning”? What is “Go module tooling”? Clicking the links takes me to an empty github page!
Also, caddy IS running in the background on my Rocky9 server, but ‘systemctl status’ tells me it is not! … and that it did not start with an error. But is IS running and it is serving my web pages! This makes no sense.
Please HELP! Please explain. (Forgive me if I am a stupid apache webmaster for 30 years now who has no clue what is going on here - but I obviously am)
~Thank you for any advice you can offer.
I admit we have not focused a lot of our time and energy on the website or for plugin authors. Sorry about that.
Are you authoring a plugin or just trying to set up Caddy? If you are only trying to set up Caddy, could you tell me what let you to go to “Register Package”? I don’t think anywhere in our docs points there (other than for plugin authors), but I should fix it if so.
That is strange though, you should see the following help text on the fields:
You must use semantic import versioning. Basically, this means if your module is at v2 or higher the import path must be suffixed with /vN (where N is the major version number).
Optional. Any version string recognized by Go module tooling is acceptable.
That’s also very strange… when I click the links, I get a populated GitHub page with content, but it does link to a new resource (evidently they moved from the GitHub wiki):
The Go wiki on GitHub has moved to go.dev (#61940).
The linked page has a full documentation of Go modules and when I look for “version”, I get relevant sections like “Version selection” and “Semantic import versioning”: Go Wiki: Go Modules - The Go Programming Language
(I’ll update the links on our website at least, since they changed the original-linked resource.)
Hello, Matt.
Thank you for your kind responses to my post. Between the time I joined the Caddy forum this afternoon until now, I have just run into more and more problems after problems in my effort to switch from Apache to Caddy. I did finally get a few pages of the thousands of them in my thirty-two year website portfolio that I had ambitons of transferring to a Caddy server. But, as I have truly spent two full days now making very little progress,I must abandon this idea. At the rate I’m going just trying to get my sites operating in Caddy, I figure it should take me about thirty more years to get switched over. On top of that I just began to realize how impossible it is to get cgi scripts, especially perl, working and integrating easily with databases in the Caddy environment, so I’ve decided to give this up and get back to work on my apache servers. I can see there is some good value in your project, but by this experience so far, there’s no way I can use Caddy in the very busy, high-pressure professional website production world I live in. Thanks again for your attention to my post. Good luck to you. ~RR
I don’t think anywhere in our docs points there (other than for plugin authors), but I should fix it if so.