2 ms·
I have the same syndrome. But I feel seaweedfs should be easy enough to be picked up. If you have any questions, just let me know.
by chrislusf 5y ago
I have the same syndrome. But I feel seaweedfs should be easy enough to be picked up. If you have any questions, just let me know.
- Fornax96 5y agoHey, I was trying out Seaweed yesterday. I ran into an issue with HTTPS, it seems to be not very well supported at the moment. I managed to get it running mostly secure, but replication didn't work because the volumes were calling eachother with HTTP instead of HTTPS. The HTTP request is hardcoded here: https://github.com/chrislusf/seaweedfs/blob/43fd11278ef811856551904b531bcc91821d0c9f/weed/topology/store_replicate.go#L56 https://github.com/chrislusf/seaweedfs/blob/43fd11278ef81185... and probably in a lot of other places. I even tried setting the address of the volume to https in the startup script, but then it makes a request to http://https://volume1.example.com http://https://volume1.example.com and it still fails. I also noticed that the master API is still available over HTTP even when HTTPS is enabled. I can make an issue for these things if you want. These issues are currently the only showstopper for me. I need to have every endpoint on TLS with peer verification enabled. If you can get it fixed I will gladly continue testing seaweedfs and support you on Patreon :-)