Issues

Of course, Brap is not a perfect service.

Here is a list of the issues that may brake your expectations, and solutions that may alleviate them until fixed:

FIXED: Hot-reloading is not yet supported for Node.js-based applications such as Angular, Ionic, React and the like.

To resolve, refresh your web browser manualy when your Javascript has completed recompiling.
Custom hosts are not yet supported. For client-side applications such as JavaScript, Angular and Ionic, custom host values will not work. In Angular for example, setting the host to myproxiedlocaldomain.com will not make your application accessible at that domain, even if you edit your hosts file /etc/hosts. That is because Brap uses reverse proxy to route traffic from public domains to your actual Linux Container:
```
ng serve --host myexamplelocaldomain.com
```
To resolve, you may opt not to use proxy at all, and then, whitelist the domains where you make your Front-End applications available:
```
brap-example-3000.brap.dev
brap-example-3001.brap.dev
brap-example-3002.brap.dev
```
Some packages will not run on our Pro Linux Containers. That is because our Linux Containers run headlessly, meaning, your screen is not connected to it? So don't even try installing oneko :D. There is no solution for this and is out of scope for what our Linux Containers are meant to be used.

To resolve, do not use the Pro Linux Containers of Brap. Instead, use a Virtual Machine (VM), but Brap does not offer VMs yet.

For other concerns, please contact us.

Keywords