My app failed to deploy in Autoscale deployments

[admin153]

See logs below:

2024-01-06T00:18:22Z info: Deployment: c1c60d7a-93c0-4328-9632-ccb6781de116
2024-01-06T00:18:22Z info: Build: 9d3a1406-2fb5-4223-89ff-c369b18a8554
2024-01-06T00:18:22Z info: Connecting to builder
2024-01-06T00:18:24Z info: Builder connected
2024-01-06T00:18:24Z info: Installing packages
2024-01-06T00:18:24Z info: Skipping Build as no Build command set
2024-01-06T00:18:24Z info: Pushing pid1 binary layer...
2024-01-06T00:18:26Z info: Created pid1 binary layer
2024-01-06T00:18:27Z info: Skipping Node layer creation
2024-01-06T00:18:27Z info: Pushing Repl layer...
2024-01-06T00:18:27Z info: Retrieved cached nix layer
2024-01-06T00:18:27Z info: Created hosting layer
2024-01-06T00:18:30Z info: Created Repl layer
2024-01-06T00:18:30Z info: Pushed image manifest
2024-01-06T00:18:31Z info: Pushed soci index manifest
2024-01-06T00:18:35Z info: Creating Autoscale service
2024-01-06T00:19:48Z error: The deployment failed to initialize due to a configuration or code error. Check the logs tab for more information. For additional support, please post on https://ask.replit.com/c/help/13 and a staff member will take a look.

[NateDhaliwal]

Hey, @admin153 !

Can you please provide a link to the repl? This way it is easier for staff and members of the community to help you!

Also see this guide on how to share your code:

How to share your code

To share your code with others, you can simply link to your repl or paste and format the code into your post! Linking to a repl The easiest way to share your code is by linking to your repl. You can find the link by clicking on your repl title, clicking on Cover page, and clicking the button to copy the URL. NOTE: only share repl join links or use the invite button with people you trust! Sharing short code samples Share a snippet of your code by wrapping it in backti…

[admin153]

@How to share your code

o share your code with others, you can simply link to your repl or paste and format the code into your post! Linking to a repl The easiest way to share your code is by linking to your repl. You can find the link by clicking on your repl title, clicking on eye Cover page, and clicking the link button to copy the URL. NOTE: only share repl join links or use the invite button with people you trust! Sharing short code samples Share a snippet of your code by wrapping it in backti…

https://replit.com/@admin153/WFM-VF-Slack-bot

[NateDhaliwal]

Hi @admin153 !
As your repl is a bot, please deploy it as a Reserved VM and not Autoscale as that is for websites.
Hope this helps!

[eaz]

ok, and what does one do for bots that should be run if anybody is connected (or has been recently) but not run if nobody is using it, so that no processor time is wasted by repl.it (much less billed to anybody)
you know, the behavior of running a bot behind the existing repl behavior up till now, without Always Online or any other bloat?

[eaz]

i specifically do not want to put this in a reserved VM–i specifically want it to be spun down if it is not being used
what i want is best-effort hosting, and if hosting it would require more resources than repl.it can afford to give without paying more than i already am, it should just be throttled

[NateDhaliwal]

Try putting your bot on a Flask/Express server, then use Autoscale. Autoscale turns on the server when there is an incoming request, and off if there isn’t to save resources.
Hope this helps!

[eaz]

hi, i already have a port being listened on, all of the usual works from back in the era when keepalive services were promoted, sans using a keepalive.
i literally just want the old behavior of best-effort hosting upon request that wont split the process or bill me for overages–i want it to just not use resources that would be billed to overage
as for not splitting the process i assume setting “maximum instances” to one does that?

[NateDhaliwal]

Could you elaborate more? I mentioned that Autoscale will only charge you when there is an incoming request, for every compute unit used. Reserved VMs are on 99.9% of the time, but is charged daily.

[eaz]

i actually have multiple projects that i’ve had rely on the same behavior from repl.it–the common thread is that i use python to listen on a port (often websocket, and then returning a fixed http response on the root so repl.it considers the repl “up”) and communicating with some number of clients over said websocket
the bot and some other projects connect externally to eg discord, but some literally are just central hub servers for whoever happens to be currently connected, if anybody is–when i connect and get “hang on, the repl is loading” from my interface i know that nobody else has it open or just disconnected.
im concerned that if i have a spike in traffic, whereas historically the repl would have simply not kept up (which is what i want to happen) i will now be billed for the extra traffic as it handles it

is this the kind of elaboration you meant, or did you need other elaboration?

[QwertyQwerty88]

@NateDhaliwal

Reserved VMs are on 99.9% of the time, but is charged daily.

Monthly*. Reserved VM deployments are charged monthly.

[eaz]

but charged per day it was running during that month, right?
that is, the bill is billed once per month but based on the days it was running?

[NateDhaliwal]

No, I believe it is for the whole month, for all the days and not just the days it was used.