-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are There Additional Self-Hosting Instructions? #65
Comments
I'm in the same boat, it deployed okay but the image won't start. Here are my logs from fly.dev: Configuring firecracker Probably doing something wrong somewhere. |
Did one of you managed to make it work ? I have the same issues. |
I managed to make it work. Here's my fly.toml
|
This configuration got me up and running. Thanks a lot! One thing that really helped was using fly's github integration to launch and deploy the app. Fork the skybridge repo to your account, commit a change to fly.toml with your own configuration, then link your github to fly and launch from the web UI. No need to git clone or worry about dart_frog_cli version missmatches or anything like that, fly will just do everything so you don't need to copy anything to your local machine. Worked great, once I filled everything out correctly. Make your repo private if you do this though, so no one can snoop on your configuration file. (not that anyone would, but, you know, can't be too careful.) |
@Pikuboy OK, total noob here so I am likely making some sort of stupid mistake, but I copied your fly.toml wholesale (only changed the app name and baseurl to be my fly server) and my dockerfile looks identical to the OP's, but it continually times out when I try to deploy. There is this warning:
And then after about ten minutes the deployment times out with this error:
Any ideas? |
You need
You need to fill the Skybridge Secret line too in the fly.toml file with something line this SKYBRIDGE_SECRET='451865' this is just an example, use different numbers, I don’t know what it does but it fixed the same issue I had when I tried to deploy to fly.io. |
@Pikuboy sorry, should have said that I did fill that line in with random numbers. That didn't do anything, unfortunately. I assume that the app variable on the first line needs to match the app name in the URL, right? That's how I have my fly.toml file set up, anyway. |
I assume the same concerning the app name. Don’t know if it might cause your issue but did you also fill the SKYBRIDGE_AUTH_PASSWORD line? In my template SKYBRIDGE_REQUIRE_AUTH_PASSWORD is set to true. |
That worked! I set SKYBRIDGE_AUTH_PASSWORD to be identical to SKYBRIDGE_SECRET and it fired right up. Not sure if they need to match, but I figured it was more likely to work if they did. Thank you!!! |
Thanks for support here, was able to get up and running! Question quick, does anyone know how much this ~should cost per month on Fly.io? |
I’m not an expert on fly.io and I still don’t quite understand exactly how the pricing work but I have it running since mid-September (it has been like 2 months) and it didn’t cost me a penny. But I received for free 5$ when I sign up and as of today I have 3,53$ left of it. So maybe less than a dollar per month at some point. |
Oh cool! I am giving some friends access to server, so may need to ramp up. I investigated a bit and it seems like it would be ~$3/month based on config, but better to hear from someone on real world usage lol. |
Mine’s been up for a week and I have accumulated the exorbitant balance of…12¢. I’m running my server only for myself, so I’m guessing that a month’s use won’t even get to a dollar and may not even hit half that.
Chances are there’s some lower limit under which they won’t even bother invoicing for. It’s probably diminishing returns for them to try to collect any balance less than five bucks. I’ll report back when I get to the end of the billing cycle but I don’t anticipate this breaking the bank by any measure.
…On Nov 19, 2024 at 12:06 PM -0500, Cameron Banga ***@***.***>, wrote:
> > Thanks for support here, was able to get up and running!
> > Question quick, does anyone know how much this ~should cost per month on Fly.io?
> I’m not an expert on fly.io and I still don’t quite understand exactly how the pricing work but I have it running since mid-September (it has been like 2 months) and it didn’t cost me a penny. But I received for free 5$ when I sign up and as of today I have 3,53$ left of it. So maybe less than a dollar per month at some point.
Oh cool! I am giving some friends access to server, so may need to ramp up. I investigated a bit and it seems like it would be ~$3/month based on config, but better to hear from someone on real world usage lol.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Is anyone else experiencing rate limitting through this method? I still tend to only get about twenty posts loaded in my feed at a time and it doesn't seem to be able to pull more posts. Might make a separate issue for it. |
I have never looked at the bluesky API docs, but did notice in the logs that occasionally the calls being made do have limits, saw this in mine:
Likewise, HTTP Response times seem very long, and there was some wonkiness still when I set up the instance and connected to Ivory. My thought was to give a shot ramping up to a beefier machine on Fly.io, but it's been ~good enough so far personally. But if I still see issues, may bump to a 512MB instance. |
I just got this email:
|
Can confirm I also got the same message. Mine for 12 days was a whopping $0.33. |
Hey @videah, I decided to spin up an instance of Skybridge on Fly using your instructions in the readme. I updated the fly.toml and docker-compose.yml below, and while it does deploy to Fly I'm not able to get Skybridge to do anything. (Visiting the instance's URL just tries to load up a webpage that never loads.)
fly.toml
Dockerfile
Are there perhaps other dependencies or config changes I'd need to make to get a fresh instance running?
And of course, thank you so much for all the hard work!
The text was updated successfully, but these errors were encountered: