anti_bbdax

PR submitted for docs/deployment/docker including adjustment to sidebars.js. Let me know what you think!

As noted in #ask-for-help I'll be starting to update some docs in the next week or so.

My plan:

• Additional deployment examples
  • docker compose
  • nix
• Reverse Proxy Setup
  • nginx
  • traefik
  • caddy (maybe)
• Initial configuration for use in an app stack
• Use of python-sdk with code examples

If there are any other areas you think need attending to, please let me know. I'll try to do separate pull requests for each bullet point so they are concise edits instead of a monolithic change.

That's great to hear. Within the next week or so I'll try to get some updates to the docs started.

There is also Nginx Proxy Manager that does a nice job as well.
https://nginxproxymanager.com/

I personally use traefik. Here's a blog post I did that's a bit more on the advanced side, but you can see how to setup traefik with DNS challenge to obtain TLS certs.

https://beardedtek.org/tailscale-powerdns-traefik-linode-dns/

And an alternative way:
https://beardedtek.org/traefik-tailscale-linode-dns/

I can definitely give a hand!

I was looking through the docs repo last night. It's very well laid out.

I have only 1 question before I get into it. Do you have any plans or intentions to switch licenses or close source Casdoor in the future?

Why what? Is the documentation not great?

• It doesn't explain the process or what it expects in clear terms
• It doesn't provide code examples
  Yes there is the swagger docs, but that is the bare minimum documentation.

If you want to encourage more use, you ask community members to help with documentation, collaboration, tutorials, code examples, etc to speed adoption.

If I can successfully get this all working, I plan to bring it to all my projects in the future.

If it keeps being a tangled web of devs pointing out the swagger docs and one word answers for complex issues and questions, then why the hell would I want to keep using it?

Just since I've joined this discord, this and similar questions have been answered by someone who seems to be burnt out, which is okay and common in the open source community. But if this software wants to thrive, let people help with documentation, assisting each other, and the community will take care of itself instead of someone being annoyed by people wanting to engage.

Authentication sucks in general. It's hard to do right, especially self hosted, and especially for those who don't do it 24x7 and need a good, quick, easy way to just make it work without having to pay someone else to handle it.

I know you can use Casdoor as a paid service, but that's all the more reason to make it easy.

I plan on tackling that in the next couple weeks. The documentation is not exactly great for how to accomplish it. I'm hoping to get through all of it and write up a tutorial or possibly do a pull request on the documentation, but I haven't looked that far forward yet.

I'm doing this myself. Feel free to take a look at my code.

https://GitHub.com/beardedtek/newsfeed

Hi y'all. I'm struggling with using /api/update-user.

I'm programatically doing this in python, but here is the equivalent curl that fails in the same way:

curl http://localhost:8000/api/update-user?id=newsfeed/beardedtek \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-H 'Bearer: my_ver_long_token' \
-d '{
"id": "string",
"owner": "newsfeed",
"displayName": "beardedtek",
"phone": "5555551234",
"address: [
           "My Place",
           "My Town"
          ]
}'

I'm getting back:

{
  "status": "error",
  "msg": "Unauthorized operation",
  "data": null,
  "data2": null
}