Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 22 13:16
    nfsc-tommy starred Erudika/scoold
  • Jun 21 13:50
    albogdano closed #250
  • Jun 21 13:50

    albogdano on master

    fixed potential security issue,… (compare)

  • Jun 21 13:50
    albogdano reopened #250
  • Jun 21 12:21

    albogdano on master

    fixed secure cookie flag not se… (compare)

  • Jun 21 11:49

    albogdano on master

    fixed secure cookie flag not se… (compare)

  • Jun 21 11:38
    albogdano commented #250
  • Jun 21 10:54
    JamieSlome commented #250
  • Jun 20 20:44

    albogdano on master

    security.md (compare)

  • Jun 20 17:28
    albogdano closed #250
  • Jun 20 17:28
    albogdano commented #250
  • Jun 20 16:08
    oomb opened #250
  • Jun 17 08:31

    albogdano on master

    readme (compare)

  • Jun 16 19:28
    mathias7777 starred Erudika/scoold
  • Jun 16 19:26
    drwatsno starred Erudika/scoold
  • Jun 15 15:00
    AKN-Edo commented #53
  • Jun 15 15:00
    AKN-Edo commented #53
  • Jun 15 14:50
    albogdano labeled #53
Alex Bogdanovski
@albogdano
after restart you should see the Continue with Google button on /signin
jebbinBjss
@jebbinBjss

@albogdano I've finally been able to get things working, and I'm testing with some other users now. It looks like deleting / updating my user wasn't necessary, I'll maybe have to see if I can reconnect my user with the questions I had to get the points back!
It looks like something isn't handling the /para-scoold context in the url, maybe on the scoold side. I went through and removed that (Maybe I had things setup incorrectly before) and its all working now.

A couple extra questions. Is there a config option to disable to normal email and password login? I assume this is para.password_auth_enabled = true, but I just wanted to be sure that setting that to false wouldn't mean that people who aren't authenticated can ask / edit questions.
Second, we just want to make sure that anyone who isn't authenticated can't see anything. Is there anything else worth changing besides the para.is_default_space_public = false config setting?

Thanks again for all your help, its really appreciated
jebbinBjss
@jebbinBjss
Finally, one issue to report. Looking at the reports page for questions that have been reported, it doesn't give a link to the question that has actually been reported. That look likes a bug? You can't see what you are potentially deleting
Alex Bogdanovski
@albogdano
@jebbinBjss nice, I'm glad you got it working! para.password_auth_enabled = false will turn off logins with email and password, correct. for anonymous posting from unathenticated users there's another option para.anonymous_posts_enabled = true
para.is_default_space_public = false should be enough to make the website private
when used in addition to the approved domains option it won't allow anyone outside your org to login
jebbinBjss
@jebbinBjss
Great, thanks for confirming that
Nirfrea
@msadowskigraduate
Hello, we are having a bit of an issue introducing Scoold to our environment: we can't make @mention functionality to work. We are using para with MongoDB and Lucene implementation and Scoold PRO with LDAP integration. It seems like Scoold requests the user-search results from Para, yet the users are stored on Scoold-level as far as we could deduce. From logs we get the following information:Scoold para.log:[ERROR] com.erudika.para.client.ParaClient - 400 - Invalid query string syntax q= AND ("michal" OR name:"michal") in request GET http://localhost:8080/v1/profile/search/default?q=+AND+%28%22michal%22+OR+name%3A%22michal%22%29&limit=10&page=1&sort=timestamp&type=profile&desc=true; You reckon this is some misconfiguration on our side?
Alex Bogdanovski
@albogdano
@msadowskigraduate Scoold version?
Nirfrea
@msadowskigraduate
1.42.0
Alex Bogdanovski
@albogdano
@msadowskigraduate this was fixed a couple of versions back, please upgrade to 1.43.4
Nirfrea
@msadowskigraduate
Oh, cool! Cheers :)
Alex Bogdanovski
@albogdano
you're welcome!
jebbinBjss
@jebbinBjss

Hi @albogdano, we are trying to review user activity to see how our users like the platform. I've found the para access logs for the para server that contains requests, and the scoold logs that records high level things like user creation. Is there anything else that would be useful to review, or something that we can enable for scoold that will add information? I've also seen the metric logs, but we aren't concerned about timings at the moment.

Also, did you see my message above about the reports page missing a link to the reported question?

Alex Bogdanovski
@albogdano
@jebbinBjss Yes, I also got a message from Phil about the same - you should probably enable access logs in Scoold and then analyze those with a log analyzer like AWStats or GoAccess. To enable access logs in Scoold, start it with -Dserver.jetty.accesslog.enabled=true
Scoold does not keep any other telemetry data for usage statistics
jebbinBjss
@jebbinBjss
Ah, thanks. I didn't realise he had already sent you a message.
Alex Bogdanovski
@albogdano
@jebbinBjss sorry, I missed the reports message - I'll check that
jebbinBjss
@jebbinBjss
Thanks
Alex Bogdanovski
@albogdano
@jebbinBjss question reports do show the link to the actual post - you must have clicked on the report user link here:
image.png
To report a question you need to go to the question page and there's a Report link under the question body. Also, clicking "Delete" on the Reports page only deletes the report, not the reported question
jebbinBjss
@jebbinBjss
Ah I see that now. That could make take a small UI tweak? I think Phil and I assumed that the menu context was for the question.
Thanks!
Alex Bogdanovski
@albogdano
yes, I see how this might be confusing to some. thanks for the tip
vxhare
@vxhare
image.png
I configured the cloud server to upload photos to s3. The photo uploads to s3 and the permissions are set to public but on the site, the URL doesn't read s3 URL. it reads the default URL before I customized the domain.
Alex Bogdanovski
@albogdano
@vxhare by the way, Scoold Cloud automatically configures S3 for you. I updated Scoold Cloud, can you confirm that the issue is fixed?
se-alexnsa
@se-alexnsa
Hi there - in the email noftication, the bottom links "Scoold . Powered by Scoold" link to localhost:8000 for 'Scoold' and scoold.com for the other. I was thinking I have to access the html file to change localhost:8000, as I can't find where it might be defaulting to from looking at the documentation. Do you know where I can alter this link value?
Alex Bogdanovski
@albogdano
@se-alexnsa the URLs are controlled by para.host_url. you can turn off the branding on the website with para.show_branding = false and change the email footer with para.emails_footer_html = "<a href='url'>Text</a>"
vxhare
@vxhare
@albogdano now its serving from the server and not s3
Alex Bogdanovski
@albogdano
@vxhare yes, that's how it works - files uploaded to S3 from Scoold are aways served through the Scoold controllers not from S3 directly.
is the image loading?
vxhare
@vxhare
ahh

ok, yes!

thanks!!

Alex Bogdanovski
@albogdano
you're welcome!
I mean the image is on S3 and loaded from there but Scoold does that and you won't see the real S3 url
vxhare
@vxhare
@albogdano understood.
vxhare
@vxhare
image.png
How do you edit the google discription of the home page?
Alex Bogdanovski
@albogdano
@vxhare add para.meta_description = "new description"
and restart Scoold
also related: para.meta_keywords
nsortrakul
@nsortrakul
Hi, I want to migrate data from the existing production with a scoold version 1.30.2 to a newer version. Since the version 1.30.2 does not have backup/restore features, could you suggest the way to migrate all the data including users, tags, and question to the new version ?
Alex Bogdanovski
@albogdano
@nsortrakul you could just switch to the new version without a problem. that's not going to modify or delete any data. or you could just export the data from Para directly
Para also has a backup API at /v1/_export
se-alexnsa
@se-alexnsa
great thanks
also trying to troubleshoot the list of emails stored to para.admins
the list of emails were working when explicitly hard coded into the scoold application.conf file, and the admin page was accessible
However I've now been directed to store the list of emails as a secret in Parameter store AWS
but it doesnt show
can I check the value of para.admins by calling a certain api endpoint?
or is there a para-cli command I can use to check it
Alex Bogdanovski
@albogdano
@se-alexnsa no, the value for that option are loaded from the configuration file or from system properties with the same name. ENV variables also work but you need to modify the variable name to be para_admins="..."
there's no integration with AWS Parameter store. you have to supply the parameters to Scoold as system properties or ENV variables