Oh very nice point! I will improve this behaviour.

Regarding theclick here to preview you're definitely right, will get that fixed.

I will check what really happened with the succesfully deployed app.

Your input is very much appreciated, thanks a lot :)

Hello Hamida,

So I have forked your repository to understand what really happened.

From what I can see, you have modified the build settings (which is awesome), and updated the dist folder and also specified an entry file. From the way you have used the app, I got one more feedback :) The entry file is supposed to be the entry file for a server file but I believe it's understood as the entry file for the app. If you specify this, it will enable server side functionality. If you don't enable and leave this empty, it will simply serve the site from the CDN (no server side functionality). But obviously you can't know this because it's written nowhere. Tomorrow I will add some documentation to the config page so that it's more understandable.

The entry file you have specified exports a function, and that function was supposed to be an async function. So I extended the deploy api and now it also handles sync functions.

Here is the a deploy that worked for me:mhuysmeutdyjaara13dlxpmmytkl4kp9-2...

If you re-deploy your site it should just work.

Again, a million thanks for your feedback and trying it out. It helped me a lot.

Hey Meghan, thanks a lot for the lovely feedback :)

So initially Stormkit is targeting indeed static websites and node applications as you pointed out. The reason to target only these is because I'd like to provide additional open-sourced APIs and components (in react and vue for instance) to ease common tasks such as logging, handling auth, forms and managing data.

Technically it's very easy to enable Go apps (or any other app lambda functions support) as well because the infrastructure is very extendible. I'll definitely keep in mind your request :)

Thanks a lot once again!

Very good point.

As far as I know, deploying an SPA app with Google App Engine is pretty straightforward. However, some of the things I've noticed:

1. As soon as you want to add server side rendering to your static websites things become more complicated - unless you'd like to use frameworks like gatsby. But even in this case if you have dynamic content like latest blog entries or latest products you can't use a framework like this.
2. You have to manage/setup your own CI/CD.
3. Handling different environments is more tricky, like setting up staging and production environments.

Finally, GAE is universal. You can host a lot of different applications while here the focus is only web applications. Right now, it's in alpha stage with minimal features. I am trying to gather as much feedback as possible and iterate over the software based on this input.

Hey Tuan Anh, sorry that's a UI bug. You should probably click to connect more repositories and select the repositories you'd like to connect :) Thanks for reporting tho, I fixed and deployed the new version. It should display an error message when you have no repositories connected now.