hosting your website

2026-01-05

once you're happy with the local preview of your website, it's time to upload the contents of /_site to the internet for the world to see.

this process varies slightly depending on which hosting service you use, so i won't go into great detail here. i will say that Neocities seems to be the one i hear about most commonly. personally, i've been trying out Nekoweb, and liking it so far.

one-click deploy

if you pay the minimum price for bimbo, you can access bimbo+[1] which has a "one-click deploy" feature. you can enable this by selecting your provider of choice from the set up deployment menu. bimbo currently supports Neocities and Nekoweb via API, but you can use any hosting service that supports SFTP (Secure File Transfer Protocol) by selecting the other option.

upon selecting one of these options, a window will pop up and ask for some information that will be saved in bimbo-secrets.yaml[2]. after adding this configuration, you should now see an option to deploy to your provider in the menu.

you can always edit bimbo-secrets.yaml later or delete it entirely to restore the set up deployment option if you want to use a different provider.

  1. feels rude to paywall like this, but i've also sunk a lot of hours into this project at this point and it would be nice to get some small return on the investment. i figure if you're doing enough work with bimbo that manual uploading becomes an inconvenience, you probably like the tool enough to make a one-time contribution ↩︎

  2. technically, you could put this stuff in bimbo.yaml as well, but bimbo-secrets.yaml is ideal for sensitive configuration that you don't want to include in version control[3] (like API keys) ↩︎

  3. version control is another can of worms entirely. i DO recommend it for your projects and should note that new projects will automatically include a .gitignore file that keeps /_site and bimbo-secrets.yaml from being included in git commits ↩︎

« previous post | home | next post »