General comments related to cold install.

[raisch]

Hi.

First, thanks for SocialPredict. I'm quite excited to build my own projects using it as a base.

I have a few initial thoughts to share (below).

These are my observations when doing a cold install on a Macbook running MacOS Sequoia 15.6.1 with 16GB and 512GB disk of which 65+GB are free. I run the most recent version of Docker via Docker Desktop.

When I've fully evaluated the platform, I'll be sure to post bug reports.

And as I discover new things, I'll add them as comments on this post.

---

• Installation

  • The local install README states that database files will be stored under ./data/postgres. This is not the case; the data files are stored in a Docker volume named scripts_pgdata which, even if this was desired behavior, the name seems overly generic and so doesn't provide enough useful context.
  • Customization
    • changing image and container names in ./.env works for most setup. However lines ## 62-63 in ./scripts/dev/build_dev.sh overwrite the values defined in the env file with defaults, i.e. BACKEND_IMAGE_NAME="socialpredict-backend:latest" and FRONTEND_IMAGE_NAME="socialpredict-frontend:latest", which causes the Docker container creation to fail. Commenting those lines causes container creation to succeed.

• User Creation

  • on new user log in when the change password request appears, if the new password fails the internal complexity logic, the error message displayed to the user is Unexpected token 'N', "New passwo"... is not valid JSON which seems pretty odd to me.
    • A simple workaround is to provide the existing automatically generated password as the new password, which while not desired, passes the logic.
  • While setting the initial_account_balance in the users table appears to work, that value doesn't appear to surface properly in the UI, as the message: 'Error: Error: Failed to fetch user credit' appears in the left column of the UI directly below the 'SocialPredict' header.

---

Final Thoughts: In my opinion, the new password handling logic is really very brittle and doesn't communicate error conditions to the user well. I suggest it needs significant refactoring. (If I get the time, I'll update it and submit a PR, unless someone else beats me to it.)

Thanks again for SocialPredict & all best.

[pwdel]

Greetings @raisch thanks so much! Sorry for the delay, I have been dealing with sick family this weekend.

All of that sounds great. I would be happy to just add you as a contributor if that's easier for you...?

[raisch]

Thanks, that would be cool. I just posted a simple PR to support env vars defined in .env so they won't be overridden in ./scripts/dev/build_dev.sh (My Customization bullet above.) If that passes muster, I'll see if I can tackle a few more.

[raisch]

A few more hiccoughs:

• After setting a user's new password and the page is redirected to /login, the main pane displays 404 - Page Not Found.
• After initial password set and new user re-login, the top item in left menu shows an icon of two stacked cylinders followed by grey bullet with text = '500' which links to /profile - How is this menu item intended? After market creation and initial bet, it does not change. Ahh, after a little digging, this is the user's "credit".
• Using default value of economics.user.initialAccountBalance = 0 as defined in ./backend/setup/setup.yaml, when user creates a new market and bets 100 on YES, user balance is -111 (presumably 100 for bet and 1 for initialBetFee, and 10 for createMarketCost as also defined in ./backend/setup/setup.yaml) - Is this negative balance intended? It seems it might be since there is a maximumDebtAllowed of 500. Also, do the initialBetFee and createMarketCost contribute to the resulting awards or are they meant to be consumed by the system (as a cost of doing business, perhaps)?

Generally, I wonder if calling market stakes 'bets' is prudent as that implies that they are gambles rather than positions. Just a thought.