To be honest, the design of this site is so simple and somewhat bootstrap-era that I feel as if the $249 price tag is a joke.

I agree, this is the best solution, I'm sick of countless projects with key input fields where I have to go to Ctrl/CV every time.

Not to mention the ludicrously gaping security issue that this is. My guess is they want to push people to the plugins tho.

you need maybe https://github.com/Chanzhaoyu/chatgpt-web or https://github.com/Yidadaa/ChatGPT-Next-Web

For the example saved conversation, if your own service uses the openai API, you can change the baseurl to https://oai.hconeai.com which provides most of the functionality for conversation analysis

I am from China, the Chinese government has banned access to chatgpt related products and Baidu has launched the 文心一言 which is basically gpt-3.

Wait, do you mean it's on par with GPT-3, or it's literally GPT-3? If the latter, how did they get the model?

In fact, the development of the world is based on constant levels of abstraction, just think of assembly language and computer punch tape programming, those days are not long past.

> All you may need is HTML

All your blogs need is HTML.

It looks good! Look forward to more platforms, such as railway ,northflank

Thank you! Railway is almost ready! You can subscribe to updates here: https://github.com/Infisical/infisical/issues/271

Would you be able to open a GitHub issue for northflank? Thank you!

In fact, when you enter the fly.io console, you will feel that this is an unfinished construction site, especially when you start to deploy a new app, and the frame text icons in the options are simply truncated, which feels rough.

After I have experienced several fly.io render railway northflank platforms, I think the problem with fly.io is that the web console is not fully functional, too dependent on CLI and the response time of the application is unstable. The problem with render is that it is too slow to build, north is similar to railway, and the experience is good. But although the north console is very comprehensive, it is too complicated and dazzling. By contrast, the interface of railway is very simple and comprehensive, and UX is great. (found by wappalyzer analysis that it is based on nextjs,very nice)

I tried railway and northflank. Really like the UI northflank has; I think anyone familiar with Kubernetes should feel right at home. I also agree with the sentiment that railway ui is simpler.

I get up to 20secs of downtime when redeploying on railway... I was using the sample golang repo from fly : https://github.com/fly-apps/go-example

That's just unacceptible imo.

Hey there fyzix! Angelo here, Support Engineer from Railway. I was here procrastinating from work when I saw this comment.

The downtime you see is our proxy taking time to cutover- however, we have https://docs.railway.app/deploy/healthchecks that will only cutover once we have a 200 from your API. This way we can keep your old deploy live and serving requests if and only if it's live.

Theres more we can do to make it magical, but this should help in the meantime.

Thanks for the reply, Issue resolved:)

This could be done automatically by pinging the root and searching for a header set by railway's default page. If it doesn't exist then the service is live.

We used to do that by default, but it led to issues with load on our proxy. (Imagine n * m pings against your host for a shit-tonne (official measurement) of builds + deploys a day.)

We are hiring Network Engineers for exactly this reason :')

More context: The UI shows that the service is available but when I visit the live url, I get a 404.

What I think is happening is that the UI shows the status of the underlying container and there is some fault with the reverse proxy they are using to expose the container to the internet.

Fly.io doesn't have this issue but I am leery of all the complaints here.

>The problem with render is that it is too slow to build

This is only true for the free tier, and (hopefully) won't be true for much longer.

Yes, but I think the difference between free layer and paid users should be distinguished in terms of capacity and scalability. This crude entry experience may lead to a reduction in user conversion.