Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test ability to run SMD codebase locally #80

Open
anilnatha opened this issue Nov 7, 2023 · 6 comments
Open

Test ability to run SMD codebase locally #80

anilnatha opened this issue Nov 7, 2023 · 6 comments
Assignees
Labels
B14.1 B15.0 i&t.skip Skip I&T of this task/ticket task

Comments

@anilnatha
Copy link
Collaborator

We need to go through the process of setting up our local environment so that we can try running the SMD codebase locally.

Information related to set up local development system is located:

@anilnatha anilnatha added B14.1 task i&t.skip Skip I&T of this task/ticket sprint-backlog labels Nov 7, 2023
@anilnatha anilnatha self-assigned this Nov 7, 2023
@anilnatha
Copy link
Collaborator Author

After some trial and error, I've made progress in getting my local environment set up.

I'm now at the point where running the command make backend produces a docker error that I'm investigating

 ✔ Container vip-dev-env-proxy-proxy-1  Created                                                                                                                                                                                                                                                                                                               0.0s 
Error response from daemon: Ports are not available: exposing port TCP 127.0.0.1:443 -> 0.0.0.0:0: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory
ERROR ==> /Applications/Docker.app/Contents/Resources/bin/docker-compose,--project-name,vip-dev-env-proxy,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-0.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-1.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-2.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-3.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-4.yml,up,--detach,--remove-orphans,proxy failed with exit code 1

@anilnatha
Copy link
Collaborator Author

Thanks to this post, I was able to resolve the issue I was encountering with Docker Desktop.

@anilnatha
Copy link
Collaborator Author

Able to run codebase locally; however, encountered some issues that will need to be addressed as we proceed. Hoping the SMD/JPL Dev team will be able to provide insights regarding these issues

Problems

  1. NASA Child theme breaks WP installation forcing a rebuild.
  2. Plugin activation fails in some cases.
  3. Can't start frontend service because of the issues above.
  4. Don't currently have access to private hds package (@smd/hds)

@tloubrieu-jpl
Copy link
Member

tloubrieu-jpl commented Nov 14, 2023

@anilnatha is now analysing how to integrate our code to the SMD code base by copying their repository.

@tloubrieu-jpl
Copy link
Member

@anilnatha is making progress on that ticket and in parallel prepares questions for the SMD team.

@tloubrieu-jpl
Copy link
Member

@anilnatha is blocked because the SMD documentation is partly unavailable.

@anilnatha also prepared questions for the SMD team.

@anilnatha anilnatha transferred this issue from NASA-PDS/portal-wp-tasks Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B14.1 B15.0 i&t.skip Skip I&T of this task/ticket task
Projects
Status: ToDo
Development

No branches or pull requests

3 participants