Pynecone export to html, css, and JS

[xopherw]

Is there a way for Pynecone to export the python codes into html/css/JS files so I can host the web app on github?

[Alek99]

Hello, in short yes or no depending on if your app is interactive or not.

Pynecone apps are not static by nature so if your app requires any state interaction you will need to host it on a server (at least the backend). This is because any python web app (not just our framework) needs to run some sort of server to handle the api requests and static website hosting such as s3 or GitHub can't run this.

If you want the js files we compile down to you can find this in the .web folder of your project. Once in this folder you can run next build && next export this should export a static version of your sites js/html/css in the out directory it creates within the .web directory.

You can then use the files in the out directory and follow any GitHub pages hosting tutorial for a nextjs app.

Our current tutorial details generally how to run this on a server see here. I'm currently in the process of making a better tutorial for hosting should have it out in the next couple days.

Let me know if this answers your question happy to elaborate if this doesn't make sense.

[FHU-yezi]

Maybe we can set the backend API address when we build the App, and deploy frontend with Nginx etc. use FastAPI to handle event callback and server side logic.

They can improve performance when we are facing lots of requests, and can reduce memory cost for a bit.

[Alek99]

Yes I believe you can do this by specifying the api_url in the config. So you can specify this in the config the pc run take .web code host it on s3 and then just run the backend on a server.

[FHU-yezi]

Yes I believe you can do this by specifying the api_url in the config. So you can specify this in the config the pc run take .web code host it on s3 and then just run the backend on a server.

The api_url arg is avaliable now? Awesome. But when we have frontend code already hosted somewhere else, we don't need to host static files with FastAPI.

So maybe a arg for pc run is needed? Called --no-static or something else.

[Alek99]

Right so when you have your frontend code hosted somewhere else you can do pc run --env prod --no-frontend and it should work if you specify the api_url on your frontend

[FHU-yezi]

If your Web App is totally static, means there are zero event callback, you can simply run pc run, and when your App is running, stop it, copy all the files in .web folder, and deploy them.

We are going to add a subcommand, maybe called pc export or something else, to build static assets.

[Alek99]

Yeah exact we can definitely add a pc export command. This could export all the contents for a static site

[picklelo]

Yes, there's a ticket for this already. We will add it out in an upcoming milestone.

[Alek99]

@xopherw The deployment process will be way easier once we have pc deploy done still working on this feature. But once we complete this you should be able to just type that and have a live app in a couple miniutea. In the mean time I'll work on creating a better self hosting tutorial and will update you when its ready