-
https://circleci.com/gh/Originate/EDX/49
Was working for 0.23.0.alpha.4 and started failing when upgraded to 0.23.0.alpha.5.
![screen shot 2017-09-19 at 6 38 02 pm](https://user-images.githubuse…
-
> When using dependencies that take a while to boot up
I want "exo run" to wait before it boots up services that depend on them
So that my services find fully running dependencies when they boot up …
kevgo updated
7 years ago
-
> When starting to work on a new Exosphere application
I want to be able to generate the application programmatically
So that I don't have to read documentation to determine how to set up the applic…
kevgo updated
7 years ago
-
> When developing a fleet of similar applications
I want to be able to use service templates from a remote location
So that I don't have to copy-and-paste templates into all my application code base…
kevgo updated
7 years ago
-
This was another bottleneck I faced.
How to make sure, after developing 4 different services they work well in production before integrating them in the front-end. For example, service d, consume a …
-
exo setup runs the setup command from each services.yml locally. However, here are a couple of scenarios where this is not desirable.
1. glide install, but my system is not pre-installed with go. I…
-
I tried to run the following command as per the docs:
`curl https://raw.githubusercontent.com/Originate/exosphere-sdk/master/bin/install_osx | sh`
and got the following error:
`sh: line 1: 404:: co…
-
If the `sends:` section is empty in the `service.yml` file, and that service tries to send a message, exosphere crashes. The error points to the line below:
https://github.com/Originate/exocom/blob…
-
The livescript send functionality supports a callback like this:
```
exoRelay = new ExoRelay exocom-host: host, exocom-port: port, role: role
exoRelay.send 'message.request {field1:..., field2:..…
-
This is an issue especially if you don't pipe `exo run` to a file.
It causes timesouts of services.
Recommendation: only dump parts of large messages