insted of running a local backend in theory, you can edit
/src/env.tshttps://git.chapo.chat/hexbear-collective/hexbear-frontend/src/branch/main/src/env.ts
to point the api to a working backend.
Currently, that location is always trying to point to the same url as the site but you could use either the dev site or even the live site if you really wanted to. The API doesn't care.
pinging @vertexarray so she sees this too.
When i proposed it she claimed that she doesnt recommend it as a development workflow
In general, it's probably not the best but getting a working database and local backend is a lot to ask of someone who is only working on the frontend anyway.
We do have a dev site you can point to instead of the live site. that may be preferable so that you can test making posts and comments etc. Ask in the matrix room (linked in the sidebar) for the dev url.
Could you show me how should i modify
env.tsto make it connect with the dev site?simply change the three constants that are exported
host,port, andwsUrito point to the desired URLah, you may also need to edit
the
hostnamefunction....https://git.chapo.chat/hexbear-collective/hexbear-frontend/src/branch/main/src/utils.ts#L1093
Actualy, sorry
the API definition
https://git.chapo.chat/hexbear-collective/hexbear-frontend/src/branch/main/src/utils.ts#L1241
I dont know exactly how to do that, could you just send me how exactly the files should look?
Gotta run a local backend too, as well as the local database. For the backend, using docker will make it easier to get running but use more resources.
I dont know how to do that, wouldnt it be easier to have my frontend connect to the server?
I took a second to tool around with connecting my local frontend to the dev server, and it seems like it sort of works, but loading comments and making accounts didn't work. Can't recommend it as a development workflow.
Here's the guide to getting it running locally. If you run into problems getting it going don't hesitate to ask — it took a bit of fiddling for me.
Ok, so i followed the instructions, but when i run
cargo runon the backend i getFATAL: password authentication failed for user "lemmy"It looks like you can just do
./db-init.shin a terminal in theserverdirectoryFATAL: Peer authentication failed for user "postgres"Also there wasnt server directory, that file was in scripts
Hmm, I didn't encounter that on my end. I'm not on Linux so it might be an OS difference.
Which backend should i use?
https://git.chapo.chat/hexbear-collective/hexbear or
https://git.chapo.chat/hexbear-collective/lemmy-hexbear
https://git.chapo.chat/hexbear-collective/lemmy-hexbear is the rust backend, it's the one currently in production. Should use that. Also it has the frontend as a submodule.
I managed to execute
./db-init.shand now that i runcargo runi getcould not connect to server: Connection refusedIs the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?hmm, maybe try restarting postgres? If you could run
db-initusing its default config, it should at least be on the right port alreadyif by restarting you meant
sudo service postgresql restartthen it didnt worki figured how to fix that bug but now i have
Specified path is not a directory: "../ui/dist/documentation"I ran into that one. I think I just had to do a release build of the ui.
if you've pulled the submodules, you'll have the ui folder. do
yarn buildin thereSo, after i cloned frontend into ui and did
yarn buildthere, there are still those errors
Actually these problems might be because i cloned the repository provided in documentation you sent me and not the hexbear backend, i will try these steps with it and see if it works
