Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Celest – Flutter Cloud Platform

celest.dev

Post reply on HN
Print view View original

21–30 of 50 posts

Re: Show HN: Celest – Flutter Cloud Platform

#22

Post by marcglasberg »

dillonnys wrote: post #19
e12e wrote: post #17

Looks interesting. What are your plans for the backend - will self-hosting be an option? Right now this looks fine for a hobby project, but massive lock-in/risk for production (what if you shut down, get bought up etc?).

Great points. My immediate plan for reducing lock-in is to provide the option to deploy into a cloud account you manage. This has the upside of making your deployed infrastructure independent of Celest and letting you use your cloud credits. Self-hosting is another option I'm considering, but I don't have a good sense yet of what that could look like. Any thoughts? Is spitting out a binary/Dockerfile sufficient to al…

Committing to open-source the code (and provide detailed instructions on how to run the code) in case the company shuts down is the most important. It could be part of the service contract. I've read all parts of the Celest code which are public, and I can attest it's very well-written and easy to understand.

Re: Show HN: Celest – Flutter Cloud Platform

#24

Post by marcglasberg »

dillonnys wrote: post #16
evanlance wrote: post #15

Excelent news! Excuseme but where can i manage my free celest-cloud? i could run celest deploy with success but now i dont know how to use it and keep with the testings :D

Glad to hear you ran a successful deploy! Currently we just have the CLI to manage your account, although I'm working on a web-based dashboard for better accessibility. The result of a deployment is just a URL, which is automatically placed in your generated client (see `celest/lib/client.dart`). To switch to this new environment, pass the production arg to your `celest.init` call like this: void main() { celest.init…

Just to clarify what Dillon said:

When you do `celest deploy` it sends your current code to the cloud. After that if your code contains: `celest.init(environment: CelestEnvironment.production);` it will use that code you just sent to the cloud. If your code contains `celest.init(environment: CelestEnvironment.local);` it will use the code you have in your local machine.

But in practice you develop locally, so you don't need to deploy all the time.

Also, you can call `celest.init` as many times as you like, while the app is running, to change from local to cloud and vice-versa, on the fly!

Re: Show HN: Celest – Flutter Cloud Platform

#25

Post by marcglasberg »

DerCommodore wrote: post #4

What is the difference to Serverpod? can you elaborate here so I get a better view?

I'd say the developer experience is completely different. With Celest you can almost pretend you are writing the frontend and backend code as one single codebase. And then you change a flag and the part of your code that needs to be in the cloud is moved to the cloud, seamless. I think you have to try it out to really grok how much easier it is.

Re: Show HN: Celest – Flutter Cloud Platform

#28

Post by dillonnys »

marcglasberg wrote: post #22
dillonnys wrote: post #19

Earlier quoted context omitted.

Great points. My immediate plan for reducing lock-in is to provide the option to deploy into a cloud account you manage. This has the upside of making your deployed infrastructure independent of Celest and letting you use your cloud credits. Self-hosting is another option I'm considering, but I don't have a good sense yet of what that could look like. Any thoughts? Is spitting out a binary/Dockerfile sufficient to al…

Committing to open-source the code (and provide detailed instructions on how to run the code) in case the company shuts down is the most important. It could be part of the service contract. I've read all parts of the Celest code which are public, and I can attest it's very well-written and easy to understand.

> It could be part of the service contract.

Agreed. I'll look into how we can add that.

Post reply on HN