Content
View differences
Updated by Henriette Darge over 4 years ago
**Current situation**
* In order to test the Safari browser in BrowserStack we need to do multiple preparational steps because Safari acts a bit different there.
* These are the steps:
* set environment variable OPENPROJECT\_DISABLE\_DEV\_ASSET\_PROXY (alternatively in the FrontendHelper let this method: `self.assets_proxied?` always return false)
* In the file development.rb add this line add the bottom: `config.hosts << "bs-local.com"` "`[`bs-local.com`](http://bs-local.com/)`"`
* Instead of the normal asset build, do the following:
* cd frontend && num run build:watch
* After that: open the rails console (`rails c`) and run the following `OpenProject::Assets.rebuild_manifest!` (this command has to be rerun every time you want so see changes you made)
**Expected**
* The above steps should be implemented into the code and hidden behind a flag so that you only have to set the flag when you want to test something on Safari.
* In order to test the Safari browser in BrowserStack we need to do multiple preparational steps because Safari acts a bit different there.
* These are the steps:
* set environment variable OPENPROJECT\_DISABLE\_DEV\_ASSET\_PROXY (alternatively in the FrontendHelper let this method: `self.assets_proxied?` always return false)
* In the file development.rb add this line add the bottom: `config.hosts << "bs-local.com"`
* Instead of the normal asset build, do the following:
* cd frontend && num run build:watch
* After that: open the rails console (`rails c`) and run the following `OpenProject::Assets.rebuild_manifest!` (this command has to be rerun every time you want so see changes you made)
**Expected**
* The above steps should be implemented into the code and hidden behind a flag so that you only have to set the flag when you want to test something on Safari.