Income Sources :: Jobs :: 2022 :: HP :: Lens :: Repos :: poly-glass :: team-mo :: tooling :: silica-local-cloud
⪼ Made with 💜 by realpolyglot.com
- Income Sources :: Jobs :: 2022 :: HP :: Lens :: Repos :: poly-glass :: team-mo :: integrations :: silica-local-cloud
- Services not registering
Environment Setup, Unit Testing, Notes, and Tips Getting silica-local-cloud running takes docker and docker-compose. It is recommended that you not use snap or pip versions of these, as these will not function well (e.g. if using Ubuntu use apt to install them, not snap). For other directions on running silica-local-cloud on your dev-machine there are other instructions in these pages (I found the running it on Windows insightful as well as the README from silica-local-cloud project). In order to execute unit tests (npm test) in most projects, they will require you to run silica-local-cloud (./run.sh ), stop the container running the service you want to test (docker rm ) and then run the tests. Many of the 'unit' tests in Lens are really more system or integration testing that probably require many of the other Lens services to be running (a database for example or the GQL API server). To run tests in may projects look for the README file first. There could be a recipe that will provide instructions on how to make the unit tests to connect to silica-local-cloud (i.e. API, RabbitMQ message bus, database, ...). It generally involves copying some hidden template file to a location in the project and editing that file for your environment (your FQDN, your IP, ports....).