Wow ! Thanks ! It works now

Thanks, it works ! Added ncu (npm-check-updates) to the build script

Aaa, you rocks ! ctx was commented out at the top… But who is looking at the top, really ? For anyone needed this:

...
     chainWebpack (chain, { isServer, isClient }) {
        chain.module.rule('preprocessor')
          .test(/\.(js|vue)$/)
          .enforce('pre')
          .exclude
          .add((/[\\/]node_modules[\\/]/))
          .end()
          .use('webpack-preprocessor-loader')
          .loader('webpack-preprocessor-loader')
          .options({
            params: {
              capacitor: (ctx.modeName == 'capacitor')
            },
            directives: {
              capacitor: (ctx.modeName == 'capacitor')
            }
        })
      },
...

Connection target and binding one are different things. At docker you must bind server to 0.0.0.0 and connect client using node host address which is usually internal to docker network

I’ve used stock call:

if (this.$q.platform.is.capacitor) {
  return cordova.InAppBrowser.open(url, '_blank', params)

I’ve not needed onload events but needed to auto-close the window after user posts some data at URL. It was not trivial as one tab can’t close other one

@sheejavarghese6 Let me guess - you are trying to run it in emulator ? It will not work until you will not update the google play and webview inside emulator - it is stated at cordova site, google

Does code-push works for capacitor ?

the pure cordova runs even at 4.4 - https://cordova.apache.org/docs/en/latest/guide/platforms/android/index.html

hint: do not use emulator but real device with updated to latest webview.

Nginx can do auth for you for any location, see ngx_http_auth_request_module

…
someapilocation {
auth_request /auth;
…
}

location /auth {
proxy_pass http://myauthendpoint
}
…

At your endpoint you can just check the token that is coming in header

@Ilia Adding mas do not changing anything, I need arm64 build not x86:

…build log…
• packaging platform=mas arch=x64 electron=11.0.3 appOutDir=dist/electron/Packaged/mas
• downloading url=https://github.com/electron/electron/releases/download/v11.0.3/electron-v11.0.3-mas-x64.zip size=78 MB parts=8
• building target=macOS zip arch=x64 file=dist/electron/Packaged/app-mac.zip
• downloaded url=https://github.com/electron/electron/releases/download/v11.0.3/electron-v11.0.3-mas-x64.zip duration=11.973s
…

As you can see from build log zip and mas targets are using the same electron-v11.0.3-mas-x64.zip

You can redirect with some nginx logic the users from /latest/index.html -> /x.y.z/index.html

This way all lazy routes will still work for older versions and new users will get the latest one. Then just remove the whole /x.y.z directories using some usage stat from nginx logs - i.e. grep & remove at cron.

As redirect helper you can use generated scripts or njs

You can always delete the old files from using ‘find /some/path -ctime +3 -type f -exec rm -vf {};’ command.

Hi, I’m using electron-builder. But the --arch command line option is just ignored

Greetings,

Having users with slow and buggy connections so mostly they can’t even load the SPA bundle and browser stuck at white screen or so. Is there exists any ready solution that can load all files from server, restart download at error, display loading progress bar, etc ?