mirror of
https://github.com/lldap/lldap.git
synced 2026-04-26 00:36:01 +03:00
[GH-ISSUE #306] Installation from source - cargo failed to load source for dependency yew_form #115
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#115
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EmTeeAge on GitHub (Sep 27, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/306
Hello,
I have tried installing lldap by building from source and ran into an issue when running the following command:
cargo build --release -p lldap -p migration-toolThe error is following:
First I though it had something with my local configuration of cargo or mistake on my side, but after examining Cargo.toml, it looks like yew_form is a dependency of lldap.
Unfortunately, it looks like the repo at https://github.com/sassman/yew_form is gone.
Based on the information in Cargo.toml, it should be removed "when there's a new release", however I have no idea which release and whether it is still supposed to be there.
After commenting out the references to yew_form, I managed to get further but ended up on a different error - this time regarding yew_form verions.
Could you provide me with some tips or help how to get rid of this?
Thank you very much
@EmTeeAge commented on GitHub (Sep 27, 2022):
According to crates.io, there's no package named yew_form in version 0.1.8, only 0.1.7.
I managed to get around the version error by editing Cargo.toml in the ./app folder and replacing yew_form = "0.1.8" with yew_form = "0.1.7"
After this modification, the build finished and I was able to move on.
@EmTeeAge commented on GitHub (Sep 28, 2022):
Well, in the end the installation failed eventually in the last step when running build.sh
@nitnelave commented on GitHub (Sep 28, 2022):
Do you have the latest code? I fixed that dependency a while ago, the repo
is now jfbilodeau/yew_form
On Wed, 28 Sept 2022, 09:07 EmTeeAge, @.***> wrote:
@EmTeeAge commented on GitHub (Sep 28, 2022):
Hi,
I used the latest source code from Releases, which is version v0.4.0. I haven't tried with the current code in the repo yet, I guess that could be the issue. Thanks.
@EmTeeAge commented on GitHub (Sep 29, 2022):
When building from the latest commit, I was able to compile the server, but know I'm unable to get the webUI up and running. I've tried playing around with different permissions, users and file paths, but I always seem to end up with this error.
The webUI on port 17170 loads with
No such file or directory (os error 2)@nitnelave commented on GitHub (Sep 30, 2022):
Repeating what was said on Discord for posterity:
LLDAP needs access to the frontend files created by running ./app/build.sh, the app/pkg directory, index.html, and static files. They need to be next to where you run the binary, in the app/ subdirectory from your working directory.
In your case, it sounds like you cloned the repository in/var/www/lldap, so calling cargo run from there should work (after generating the frontend build files)
@EmTeeAge commented on GitHub (Oct 2, 2022):
Thank you for the help!
It turned out to be issue with paths. I got a bit confused and was trying commands in the wrong paths.
I ended up with the following systemd configuration file, which now works correctly.
What also got me in the example systemd file (https://github.com/nitnelave/lldap/blob/main/example_configs/lldap.service) was this bit:
Why is there the \ and run is on the second line? In my case it works fine like this:
Thank you.
@nitnelave commented on GitHub (Oct 4, 2022):
I'm glad you got it working!
Just a note on the backslash: a line ending with a backslash means that the next line is considered to be the continuation of the current line. So
is the same as
It's just used to break up long lines. You'll see it in a bunch of places, including for instance Dockerfiles.