Develop Reference

Electron-builder uses wrong filename in https request when trying to fetch the latest release

I am building an application in electron and currently I'm trying to implement electron-builders autoUpdate. I have one private repository with my source code and one public repository where I want to release the updated artifacts of my app.
The process looks like the folliwing:
Install v1 of app on computer
Build v2 of app
Publish v2 of app on github
Open v1 of app on computer -> starts downloading newer version
My application is able to recognise that there is a new release published on github but when it tries to download it generates the wrong url. I get the following error message
error Cannot download "https://github.com/user/repo/releases/download/v2/application-1-universal-mac.zip", status 404:
To me the problem seems to be that in the request the wrong version number is being used. It uses the artifact name "application-1-universal-mac.zip" instead of "application-2-universal-mac.zip" which is uploaded.
In package.json I have tried to change:
"build": {
"artifactName": "appName.${ext}",
"executableName": "lol",
"buildVersion": "400",
"productName": "app",
}
which changes the name of the file but in the request it always uses the default
"node-app-${version}.${ext}"
Does anyone have a clue which variable electron-builder is looking at when generating file name in the request?

React JS App becomes blank white screen when deployed with AWS Amplify

I have a React JS app that works on local host, but when I deploy to AWS amplify displays as a blank white screen with no body. The browser tab shows the correct title and icon.
The page returns status code 403 and I believe there is a CORS issue? I have been unable to correct this in my code or on the Amplify console. Can someone point me towards what is causing my problem? I have successfully deployed a different React app with Amplify.

In my case I needed to change the homepage url in the package.json to match my Amplify URL. To do this add, or modify, the following line in your package.json:
"homepage": "{Amplify-URL}/#/"
The Amplify URL can be found in the Amplify console under App settings -> Domain Management -> URL.
Hopefully this helps!

In the build settings i.e. the amplify.yml file, you need to specify under artifacts the base directory which webpack or the build tool being used will generate.In my case this is the dist directory, because due to running yarn build command.
artifacts:
# IMPORTANT - Please verify your build output directory
baseDirectory: dist

Can I manually download Tauri buiding dependencies?

Due to some reasons, my host matchine can not get access to the Internet, the only way to build the app is to manually download all dependecies on another disk.
However, I was stuck in the wix package, which is downloaded from github. I've successfully downloaded it from my browser, but I don't know where to place it.
Is there any way to manually download all dependencies?
I was stuck here (on another disk):
info: Running Loopback command
Compiling app v0.1.0 (D:\frontend\src-tauri)
Compiling tauri v0.6.0
Finished release [optimized] target(s) in 19.28s
info: Verifying wix package
info: Downloading https://github.com/wixtoolset/wix3/releases/download/wix3112rtm/wix311-binaries.zip

On a windows machine, you can put the contents of https://github.com/wixtoolset/wix3/releases/download/wix3112rtm/wix311-binaries.zip in %LOCALAPPDATA%/tauri/WixTools.

Surge is not deploying my site

I used create-react-app to make a simple playlist creator with Spotify's API. I updated my redirectUri to the surge domain: http://jamming-1990.surge.sh/ and updated it on the dashboard of my app on Spotify's site as well.
I ran npm run build and followed the steps from the command surge, I get the output that it was created successfully but when I go to the domain, http://jamming-1990.surge.sh/ I get a 404.
Not sure what steps I missed, or why it's not deploying.

When inputting the path you must make sure to be in the build folder instead of the main root!

Problems with public directory when deploying Node.js app with Heroku

I've been working on an app which will feature a Timelinejs (open source js library) element on the client side. I copied the Timelinejs library into my public/javascripts/ directory of my app. Then I linked it in my html header. When I serve my app up locally everything works fine with the timeline. However, I noticed that when I deployed my app to Heroku it wasn't loading my timeline. Using chrome js console I discovered that it didn't find my files in the public/Javascripts/Timelinejs folder. Using the Heroku run bash command I discovered that none of my Timelinejs files were present in the file structure, although an empty Timelinejs directory was present. Is there any command or configuration I need to specify to get these files to my Heroku deployment?

Heroku has a readonly file system. The directory where you can write are ./tmp or ./log. You can't write inside the public folder.
That's because of how they manage their dynos and the way to scale them. If you want to store something, use the ./tmp or, recommended, a s3 bucket. (as I presume 'tmp' stands for 'temporary' :D)
More info here: https://devcenter.heroku.com/articles/read-only-filesystem